Skip to main content

Documentation Index

Fetch the complete documentation index at: https://langchain-5e9cc07a-preview-fjmorr-1778259990-38b7dcc.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

The Hybrid deployment model is deprecated. Do not use it for new deployments.For new deployments, use Self-hosted or Cloud.
The hybrid option requires an Enterprise plan.
The hybrid model splits LangSmith infrastructure between LangChain’s cloud and yours:
  • Control plane (LangSmith UI, APIs, and orchestration) runs in LangChain’s cloud, managed by LangChain.
  • Data plane (your and agent workloads) runs in your cloud, managed by you.
This combines the convenience of a managed interface with the flexibility of running workloads in your own environment.
Learn more about the control plane, data plane, and Agent Server architecture concepts.
ComponentResponsibilitiesWhere it runsWho manages it
  • UI for creating deployments and revisions
  • APIs for managing deployments
  • Observability data storage
LangChain’s cloudLangChain
  • Operator/listener to reconcile deployments
  • Agent Servers (agents/graphs)
  • Backing services (Postgres, Redis, etc.)
Your cloudYou
When running LangSmith in a hybrid model, you authenticate with a LangSmith API key.

​
Workflow

  1. Use the langgraph-cli or Studio to test your graph locally.
  2. Build a Docker image using the langgraph build command.
  3. Deploy your Agent Server from the control plane UI.
Supported Compute Platforms: Kubernetes.
For setup, refer to the Hybrid setup guide.

​
Architecture

Hybrid deployment: LangChain-hosted control plane (LangSmith UI/APIs) manages deployments. Your cloud runs a listener, Agent Server instances, and backing stores (Postgres/Redis) on Kubernetes.

​
Compute platforms

  • Kubernetes: Hybrid supports running the data plane on any Kubernetes cluster.
For setup in Kubernetes, refer to the Hybrid setup guide

​
Egress to LangSmith and the control plane

In the hybrid deployment model, your self-hosted data plane will send network requests to the control plane to poll for changes that need to be implemented in the data plane. Traces from data plane deployments also get sent to the LangSmith instance integrated with the control plane. This traffic to the control plane is encrypted, over HTTPS. The data plane authenticates with the control plane with a LangSmith API key. In order to enable this egress, you may need to update internal firewall rules or cloud resources (such as Security Groups) to allow certain IP addresses.
AWS/Azure PrivateLink or GCP Private Service Connect is currently not supported. This traffic will go over the internet.
Connect these docs to Claude, VSCode, and more via MCP for real-time answers.
Edit this page on GitHub or file an issue.