Short answer
What is Langdock and which companies should evaluate it?
Langdock is an enterprise AI platform with multi-provider chat, agents, Knowledge Bases, workflows and documented APIs. It is particularly relevant when teams want broad AI access and technical teams want to extend the same environment through interfaces. It should not be reduced to a simple chat tool.
Facts from vendor documentation. Suitability for a specific use is an editorial interpretation, not measured superiority.
Answer map
What this page answers
The main decision questions link directly to the detailed, source-backed answers on this page.
Evaluation criteria
4 criteria to evaluate separately
Model access
Compare more than model count: evaluate approvals, availability, regions and the practical ability to switch between model providers.
Company knowledge
Evaluate which internal sources can be connected, how source permissions are preserved and whether answers can be traced back to evidence.
Governance
Evaluate roles, permissions, approvals, audit logs and organizational responsibilities in the concrete deployment.
Hosting and data region
Do not treat storage region, processing region, model region and possible third-country transfers as the same commitment.
At a glance
How do the documented offers differ?
| Criterion | Langdock |
|---|---|
| Company focus | Langdock: platform for company-wide AI use. [09] Product breadth alone does not prove better fit or faster adoption. |
| Model access | Langdock: model choice across the supported catalogue. [10] Model availability, limits and hosting region must be checked for the specific workspace. |
| Company knowledge | Langdock: Knowledge Bases with API access. [11] Search retrieves relevant passages rather than automatically sending every document to a model. toolindex has not benchmarked answer quality. |
| Integrations | Langdock: integrations and open interfaces. [14] An interface does not establish the exact connector, write permissions or implementation effort. |
| Governance | Langdock: workspace control and agent governance. [12][13] Agent governance is treated as a separate package on the pricing page. Scope and future cost should be checked separately. |
| Administration | Langdock: SSO, SCIM and SAML documented. [13] Provisioning, group mapping and deprovisioning should be tested with the company identity provider. |
| Agents and workflows | Langdock: agents and multi-step workflows. [16][17][13] Workflow execution and model usage are separate cost drivers. An agent feature is not proof that a business process will succeed. |
| Hosting and data region | Langdock: EU application hosting; model region depends on configuration. [12] This does not mean every model is hosted in the EU. Dedicated and on-premise options have separate conditions. |
| Model training | Langdock: no training on customer data according to the vendor. [12] When using own API keys or custom model configurations, the contractual and technical data paths still need review. |
| Pricing structure | Langdock: user licence plus optional packages and usage. [13] The public price selector depends on factors such as user count and billing. toolindex does not state a supposedly comparable euro entry price without a fixed configuration. |
| API and development | Langdock: publicly documented multi-provider API. [15] Supported models, regions and rate limits depend on endpoint and workspace. |
Vendor claims, not measurements from a product test. Limitations are shown in each cell. The sections below explain the decision context.
Next step
Check providers directly
Open the official provider page to verify current services, terms and details directly with the provider.
Provider profile · Decision context
When should a company evaluate Langdock?
Langdock is an enterprise platform whose documentation covers chat, agents, integrations, workflows, knowledge repositories and APIs. [09]
Interpretation and limitation: Product breadth alone does not prove better fit or faster adoption.
Source checked: · Not hands-on tested
Langdock is a relevant option for organisations that want a shared AI interface with documented developer interfaces. The public API structure can make technical pre-assessment easier for integration-heavy use cases. [09]
Provider profile · Decision context
Which model choices does Langdock offer?
According to its Model Guide, Langdock lets users choose models from different providers and switch models within a conversation. [10]
Interpretation and limitation: Model availability, limits and hosting region must be checked for the specific workspace.
Source checked: · Not hands-on tested
Langdock documents model choice across providers. Availability, Auto Routing, regions and any use of company API keys should be recorded separately. [10]
Provider profile · Decision context
How does Langdock connect company knowledge?
Langdock documents Knowledge Bases for searching document collections and using them in chat, agents, workflows and through the Knowledge Folder API. [11]
Interpretation and limitation: Search retrieves relevant passages rather than automatically sending every document to a model. toolindex has not benchmarked answer quality.
Source checked: · Not hands-on tested
Langdock describes integrations plus REST, MCP and A2A as ways to connect internal systems and tools. [14]
Interpretation and limitation: An interface does not establish the exact connector, write permissions or implementation effort.
Source checked: · Not hands-on tested
Knowledge Bases can be used in chat, agents and workflows, and the Knowledge Folder API provides another integration path. A pilot should test document updates, deletion and permission changes. [11][14]
Provider profile · Decision context
Which governance and administration does Langdock document?
Langdock documents workspace permissions and offers separate agent governance for reviewing and approving agents. [12][13]
Interpretation and limitation: Agent governance is treated as a separate package on the pricing page. Scope and future cost should be checked separately.
Source checked: · Not hands-on tested
Langdock lists SSO, SCIM and SAML in its Business offer. [13]
Interpretation and limitation: Provisioning, group mapping and deprovisioning should be tested with the company identity provider.
Source checked: · Not hands-on tested
Langdock documents workspace permissions, agent governance, SSO, SCIM and SAML. Concrete packaging and permission behaviour should be tested with the company identity structure. [12][13]
Provider profile · Decision context
How should Langdock agents, workflows and APIs be assessed?
Langdock documents agents and workflows that combine agents, integrations and logic into multi-step processes. [16][17][13]
Interpretation and limitation: Workflow execution and model usage are separate cost drivers. An agent feature is not proof that a business process will succeed.
Source checked: · Not hands-on tested
Langdock documents provider-compatible completion endpoints for OpenAI, Anthropic, Google and Mistral models under one Langdock API key. [15]
Interpretation and limitation: Supported models, regions and rate limits depend on endpoint and workspace.
Source checked: · Not hands-on tested
Interactive assistance, automated workflows and programmatic access are separate use cases. The documented feature set does not by itself prove production reliability or cost efficiency. [16][17][13][15]
Provider profile · Decision context
What should companies review about Langdock hosting, privacy and security?
Langdock states EU hosting for the application and most configurable models, with optional dedicated, own-cloud and on-premise deployment models. [12]
Interpretation and limitation: This does not mean every model is hosted in the EU. Dedicated and on-premise options have separate conditions.
Source checked: · Not hands-on tested
Langdock states that customer data is not used to train or improve AI models. [12]
Interpretation and limitation: When using own API keys or custom model configurations, the contractual and technical data paths still need review.
Source checked: · Not hands-on tested
Langdock documents ISO 27001:2022 and SOC 2 Type II in its Trust Center together with technical and organizational controls such as encryption, restricted production access and disaster-recovery procedures. Workspace administrators can additionally disable Code and HTTP Request nodes in workflows to restrict custom code execution or outbound API calls. [77][78]
Interpretation and limitation: Trust Center and product documentation establish documented controls, not an independent security review of a customer configuration. Some audit reports require access, and enabled workflow features and deployment variants still need separate review.
Source checked: · Not hands-on tested
Langdock documents EU hosting for the application and most configurable models, with other deployment options. Model region, contracts, connected tools and the actual data flow still need separate review. [12][77][78]
Provider profile · Decision context
How should Langdock pricing be compared?
Langdock separates Chat and Agents licences from workflow, governance and API components. Enterprise pricing is custom. [13]
Interpretation and limitation: The public price selector depends on factors such as user count and billing. toolindex does not state a supposedly comparable euro entry price without a fixed configuration.
Source checked: · Not hands-on tested
A fair comparison should include user licences, workflow usage, governance components and API usage where relevant. Enterprise pricing should be assessed from a concrete quote. [13]
Provider profile · Decision context
What should a Langdock pilot prove?
Use the same tasks, documents and permission cases as the alternatives. Record output quality, correction effort, administration and total usage cost.
- Use the same real tasks and source documents across all candidates.
- Test at least two user roles with different permissions.
- Record time to a usable result, corrections, failures and operational effort.
- Capture licence, usage, implementation and administration cost separately.
Evidence
Sources and research limits
11 sources used on this page. Checked means that a public source was read. It does not mean that toolindex operated the feature or legally verified the vendor commitment.
- 09Langdock: Introduction to Langdock
· Vendor source
Reviewed area: Chat, Agents, API, Integrations, Workflows, Library, Skills
- 10Langdock: Model Guide
· Vendor source
Reviewed area: Model selection; auto routing; provider families
- 11Langdock: Knowledge bases
· Vendor source
Reviewed area: Search, document retrieval and Knowledge Folder API
- 12Langdock: Privacy & Security
· Vendor source
Reviewed area: EU application/most models; no training; permissions; deployment
- 13Langdock: Pricing
· Vendor source
Reviewed area: Chat & Agents; Workflows; Governance; API; adjustable selector
- 14Langdock: Enterprise
· Vendor source
Reviewed area: Interoperability; REST, MCP, A2A; custom infrastructure
- 15Langdock: Completion API Overview
· Vendor source
Reviewed area: Provider-compatible endpoints; supported regions; rate limits
- 16Langdock: Introduction to Agents
· Vendor source
Reviewed area: Agents for tasks; sharing and configuration
- 17Langdock: Introduction to Workflows
· Vendor source
Reviewed area: Agents, integrations and logic in multi-step automations
- 77Langdock: Langdock Trust Center
· Vendor source
Reviewed area: ISO 27001:2022; SOC 2 Type II; encryption; restricted production access; disaster recovery; EU subprocessors and data processing
- 78Langdock: Security Controls
· Vendor source
Reviewed area: Workspace administrators can disable Code and HTTP Request nodes to restrict custom code execution and outbound API access