Enterprise deployment
How Langbot is hosted, and the dedicated and on-prem options on the Desk and Dedicated (Enterprise) plan.
Langbot is a hosted service. Free, Builder and Standard customers use the shared feed at api.langbot.ai and the hosted MCP server at mcp.langbot.ai. Desk and Dedicated (Enterprise) customers can choose where listening and the feed run, and what delay their seats carry.
Hosted (default)
- Langbot listens on its own hosted capacity and attaches every event that has a market on it.
- Feed, archive and MCP are multi-tenant with per-plan rate limits.
- Measured latency per source is public at /latency.
- Status: status.langbot.ai.
Managed listening
On Enterprise we listen to sources you specify, including dial-ins that need pre-registration, private webcasts you are entitled to, and over-the-air broadcasts in regions we do not already cover. Each managed source appears on your account's latency board with its own measured lead.
Dedicated capacity
A single-tenant feed gateway and archive on infrastructure reserved for your organization, in the region you choose. Same API, same SDKs, separate rate limits and a contractual SLA on availability and delivery latency.
On-prem deployment
For firms that cannot send data out of their environment, the listener, feed, archive and MCP server run inside your network. We deliver versioned container images and a reference deployment:
| component | runs | needs |
|---|---|---|
| Listener | an accelerated host, sized with you | audio egress to the sources you choose |
| Feed | any x86 host | Postgres with TimescaleDB, NATS JetStream |
| Market calendar | any x86 host | outbound HTTPS to venue metadata APIs |
| MCP server | any x86 host | network path from your agents |
Your SDKs point at your gateway:
LANGBOT_API_URL=https://feed.internal.exampleNEXT_PUBLIC_API_URL=https://feed.internal.exampleNEXT_PUBLIC_WS_URL=wss://feed.internal.exampleUpdates are pulled on your schedule. We provide upgrade notes, migrations and a support channel; you keep the keys, the audio and the archive.
Security and data handling
- API tokens are hashed at rest; the feed never sees exchange credentials.
- Audio is never written to disk. Transcripts from restricted sources expire after the source's retention window and are not redistributed; third parties receive phrase facts only.
- Webhook deliveries are signed with
X-Langbot-Signature. - Single sign-on and audit logs are available on Enterprise.
Talk to us
Email hello@langbot.ai with the sources you need and where the deployment has to live.