Langdock’s security page lists four ways to run its AI platform. The first, multi-tenant SaaS, reads “Hosted via Microsoft Azure on servers inside the EU.” The page marks single-tenant SaaS “Enterprise (from 2,000+ seats)”. “Bring your own cloud” and on-premise hosting both carry “Enterprise (from 5,000+ seats)”.
Read as a ladder, the page ties deployment choice to contract size. On this reading, the closer a buyer wants the platform to its own infrastructure, the more seats it has to buy.
What each rung’s wording suggests
In the usual sense of the terms, multi-tenant means many customers share one deployment, and single-tenant means one customer has a deployment of its own. For single-tenant SaaS, the page reads “Dedicated deployment managed by Langdock.”
“Bring your own cloud” reads “Dedicated deployment in your own cloud.” The top rung reads “Hosting on custom Kubernetes setups via Helm charts.” Kubernetes is software that runs containerised applications across a cluster of servers. Helm charts are packaged installation recipes for it. “Your own cloud” and “custom Kubernetes setups” point towards infrastructure the customer picks. Who operates it day to day is a question for the contract.
One option sits beside the ladder. “Bring your own API keys” reads “Use your own model provider keys for supported LLMs”, meaning large language models.
Certificates and model choice
The page also lists ISO 27001 and SOC 2 Type II. ISO 27001 appears as “Certified to the global standard for information management.” SOC 2 Type II appears as “Independently audited to ensure secure, reliable data handling.”
A buyer looking at the top two rungs should ask which controls each certificate covers once the software runs on infrastructure the buyer chose. The answer belongs in the contract.
On this reading, the API-key option keeps two questions apart for a buyer. Which model provider to use is one. Where the software around it runs is the other.
Adoption figures
The security page reads “Trusted by over 15,000 companies globally”. Langdock’s customer story on Merck, dated 1 December 2025, quotes Walid Mehanna, Chief Data & AI Officer. Its figures need a careful read. The title gives “33,000 monthly active Langdock users”, while the text reads “Merck saw its user base exceed 33,000, with 14,000+ monthly active users.”
A buyer citing the Merck case should say which of the two counts it means. The story does not name a deployment option, so it says nothing about which rung Merck runs on.
The rung a smaller firm can reach
The trade-off sits at the bottom of the ladder. A firm buying a few hundred seats is below both thresholds. Single-tenant, own-cloud and on-premise hosting all start above its size, as the page lists them.
For some firms the multi-tenant option will be enough. For a firm whose policy names a specific jurisdiction for AI processing, “servers inside the EU” is the line to hold against that policy.
Two vendor questions follow from the page. Which deployment is available at the firm’s own seat count, and who runs it day to day? For anything closer to the firm’s own infrastructure, the number to plan around is 5,000.