Skip to main content
Hybrid is a platform setup for LangSmith Deployment, which deploys and runs agents in production. In a hybrid platform setup, you self-host Agent Servers in your own infrastructure and send their traces to LangSmith, where LangSmith can be either a self-hosted instance or LangSmith Cloud. This setup gives you control over where your agent workloads run while letting you choose the LangSmith platform option that best fits your observability and compliance requirements.

​
Components

ComponentWhere it runsWho manages it

for LangSmith Deployment		Your infrastructureYou
LangSmith
(tracing, evaluation, prompts)		Self-hosted in your infrastructure, or LangSmith SaaSYou (self-hosted) or LangSmith (SaaS)
Hybrid is a platform setup for LangSmith Deployment (agent serving). To set up LangSmith for observability, evaluation, and prompt engineering only, see Set up LangSmith.

​
Workflow

  1. Build and test your agent locally.
  2. Deploy your agent to an Agent Server running in your infrastructure.
  3. Send the agent’s traces to LangSmith (self-hosted or SaaS) for observability and evaluation.

​
Self-host your Agent Servers

Deploy standalone Agent Servers using Docker, Docker Compose, or Kubernetes. See the standalone server guide for prerequisites, environment variables, and platform-specific instructions.

​
Choose where traces are sent

Agent Servers send traces to LangSmith based on the LANGSMITH_ENDPOINT environment variable:
  • LangSmith SaaS: Omit LANGSMITH_ENDPOINT to use the default (GCP US), or set it to the endpoint for your region:
    Region
    GCP US
    GCP EU
    GCP APAC
    AWS US
  • Self-hosted LangSmith: Set LANGSMITH_ENDPOINT to the hostname of your self-hosted LangSmith instance.
In both cases, authenticate with a LangSmith API key issued by the LangSmith instance you are tracing to.
Connect these docs to Claude, VSCode, and more via MCP for real-time answers.
Edit this page on GitHub or file an issue.