Build team AI agents connected to approved knowledge sources and tools, with workspace access controls.
Best for: Build team AI agents connected to approved knowledge sources and tools, with workspace access controls.
AI Agents & Workflows
Back to discovery
🧩
PaidInformation reviewed 2026-10-15
Langdock
About this listing
Product and access model reviewed from current official sources; workflow and example are editorial suggestions, not a hands-on test.
Official sourceA team AI workspace for model-agnostic chat, custom agents, connected knowledge, workflows, and plan-dependent governance.
Best suited to
Langdock suits organizations choosing how employees access models and shared business sources.
Meet Langdock
Langdock suits organizations choosing how employees access models and shared business sources. Its base subscription covers chat and agents, with workflow, governance and API arrangements handled separately. Begin with a read-only task and a small approved source collection. Centralized access can organize a rollout, but the team still needs to define permissions, evidence checks and responsibility for any external action.
A practical workflow
- Define a team use case and permitted sources.
- Create an agent with clear instructions and scope.
- Evaluate known questions and missing evidence.
- Review permissions before enabling actions or wider access.
Illustrative input
This example describes a task, not a tested output. Adjust the source material and settings to your own situation.
Summarize this approved internal guide and list unanswered questions, without sending messages or changing connected records.
Result check: Verify source support and ensure the agent respected the allowed data and action boundary.
Access and alternatives
Langdock uses a paid base subscription after a time-limited no-card trial. Workflow runs, governance packages and API model use have separate billing or eligibility rules. Some workflow model usage is billed separately from chat. Confirm seats, fair-use boundaries, retention and any time-limited add-on promotion in the current proposal.
Choose another workflow when its emphasis fits better: Dust for another team-agent approach; Onyx for a different knowledge-and-assistant workspace.
What you can do
Multi-model team chat
Custom AI agents
Connected knowledge sources
Workflow automation
Agent governance controls
Where it helps
- A shared workspace can organize model access
- Agents support repeatable team tasks
- Governance can make review responsibilities explicit
What to consider
- Separate products use different billing units
- Connected knowledge and actions require permission checks
Pricing & free access
Official pricingPaid
Langdock uses a paid base subscription after a time-limited no-card trial. Workflow runs, governance packages and API model use have separate billing or eligibility rules. Some workflow model usage is billed separately from chat. Confirm seats, fair-use boundaries, retention and any time-limited add-on promotion in the current proposal.
Plan information can change. Prices and conditions are set by the provider. Information checked 2026-10-15.
Source for access detailsWeekly AI tool changes in AI Agents & Workflows
One email a week with pricing and feature changes in this category. No per-tool price alerts.
By subscribing you agree to receive this email from Genius Forges and to us storing your address to send it. We may ask you to confirm by email. Every email has an unsubscribe link. See our privacy policy.
Questions about Langdock
Who is Langdock useful for?
Langdock suits organizations choosing how employees access models and shared business sources. Its base subscription covers chat and agents, with workflow, governance and API arrangements handled separately. Begin with a read-only task and a small approved source collection. Centralized access can organize a rollout, but the team still needs to define permissions, evidence checks and responsibility for any external action.
Does Langdock have continuing free access?
Langdock uses a paid base subscription after a time-limited no-card trial. Workflow runs, governance packages and API model use have separate billing or eligibility rules. Some workflow model usage is billed separately from chat. Confirm seats, fair-use boundaries, retention and any time-limited add-on promotion in the current proposal.
How should I start a small evaluation?
Define a team use case and permitted sources. Create an agent with clear instructions and scope.
What should I check in the result?
Verify source support and ensure the agent respected the allowed data and action boundary.
When should I choose a different workflow?
Dust for another team-agent approach; Onyx for a different knowledge-and-assistant workspace.
Did this help you complete your task?
Tell us what needs improving. No account or private output required.
Report incorrect information or a broken linkReview evidence
Documentation-based review · 2026-10-15
Reviewed from the linked official documentation. The workflow and example are editorial suggestions; no account-level product test or measured performance comparison was performed.
Other tools to consider
Explore all toolsOnyx, formerly Danswer, connects company knowledge sources to search, chat and agents.
Best for: Team knowledge search and connected AI chat
Productivity & Automation
Open-source local guardrail that checks AI coding agent tool calls, secret reads, MCP use and package installs before they run.
Best for: HOL Guard is for developers who let agents such as Claude Code, Codex or Cursor run commands on their machine.
Coding & DevelopmentAI Agents & Workflows