混合

混合模型在 LangChain 的云和您的云之间拆分 LangSmith 基础设施：

• 控制平面（LangSmith UI、API 和编排）在 LangChain 的云中运行，由 LangChain 管理。
• 数据平面（您的智能体服务器和智能体工作负载）在您的云中运行，由您管理。

这结合了托管界面的便利性和在您自己环境中运行工作负载的灵活性。 在混合模型中运行 LangSmith 时，您使用 LangSmith API 密钥进行身份验证。

​

工作流程

1. 使用 langgraph-cli 或 Studio 在本地测试您的图。
2. 使用 langgraph build 命令构建 Docker 镜像。
3. 从控制平面 UI 部署您的智能体服务器。

​

Architecture

​

Compute Platforms

• Kubernetes: Hybrid supports running the data plane on any Kubernetes cluster.

​

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.

​

Listeners

In the hybrid option, one or more “listener” applications can run depending on how your LangSmith workspaces and Kubernetes clusters are organized.

​

Kubernetes cluster organization

• One or more listeners can run in a Kubernetes cluster.
• A listener can deploy into one or more namespaces in that cluster.
• Cluster owners are responsible for planning listener layout and Agent Server deployments.

​

LangSmith workspace organization

• A workspace can be associated with one or more listeners.
• A workspace can only deploy to Kubernetes clusters where all of its listeners are deployed.

​

Use Cases

Here are some common listener configurations (not strict requirements):

​

Each LangSmith workspace → separate Kubernetes cluster

• Cluster alpha runs workspace A
• Cluster beta runs workspace B

​

Separate clusters, with shared “dev” cluster

• Cluster alpha runs workspace A
• Cluster beta runs workspace B
• Cluster dev runs workspaces A and B
• Both workspaces have two listeners; cluster dev has two listener deployments

​

One cluster, one namespace per workspace

• Cluster alpha, namespace 1 runs workspace A
• Cluster alpha, namespace 2 runs workspace B

​

One cluster, single namespace for multiple workspaces

• Cluster alpha runs workspace A
• Cluster alpha runs workspace B

---