BYOC is only available for customers on the Enterprise plan.
Get started
To deploy LangSmith BYOC, contact our sales team. After the LangChain team enables BYOC for your organization, follow the onboarding guide for AWS, GCP, or Azure to create your first data plane.Regions and cloud providers
BYOC is generally available (GA) on AWS. BYOC on GCP and Azure is available in beta.AWS
You can deploy LangSmith BYOC in any of the following AWS regions:
The AWS control plane runs in
us-east-2, at aws.smith.langchain.com, regardless of where you place your AWS data planes. If you provision a data plane outside the US, your sensitive application data stays in that region while control plane metadata remains in the US:
GCP
BYOC on GCP can run in any GCP region. If the region you need is not enabled yet, contact the LangChain team to add it. The GCP control plane runs inus-central1, on the LangSmith US region at smith.langchain.com. The same split of control plane metadata and data plane application data applies. For setup, see BYOC onboarding on GCP. For what LangSmith deploys in your project, see BYOC architecture on GCP.
Azure
BYOC on Azure can run in any Azure region. If the region you need is not enabled yet, contact the LangChain team to add it. The Azure control plane runs incentralus, at azure.smith.langchain.com. The same split of control plane metadata and data plane application data applies. For setup, see BYOC onboarding on Azure. For what LangSmith deploys in your subscription, see BYOC architecture on Azure.
Available features
The following features are supported on AWS. For GCP and Azure beta feature availability, confirm your requirements with the LangChain team before deployment:- Observability: Tracing, projects, dashboards, and alerts.
- Evaluation: Datasets, experiments, evaluators, and annotation queues.
- Insights: Automatic analysis of traces to surface usage patterns, common agent behaviors, and failure modes.
- LangSmith Chat: Analyze traces, threads, prompts, and evaluations from inside your workspace.
- Prompt engineering: Prompts and prompt commits.
- LangSmith Agent Server: The LangSmith Agent Server control plane runs inside your data plane’s cluster, so both the agent management layer and your agents run in your private network.
- Sandboxes: Usage through the CLI and SDK is identical to Cloud, except that you point at your data plane’s endpoint.
- LLM Gateway: Call models across providers with one LangSmith API key, with spend, rate limit, and data protection policies enforced centrally.
- LLM auth proxy: Enforce your own authentication flows for model invocations so provider credentials are never exposed to end users.
- LangSmith MCP: Connect MCP-compatible clients to LangSmith to query data.
- Fleet: Build and run no-code agents from templates, connectors, and channels.
- SmithDB: The purpose-built observability backend for trace data, persisting to S3 on AWS, Cloud Storage on GCP, or Blob Storage on Azure in your cloud environment. Data planes created on or after October 21, 2026 run SmithDB only. ClickHouse is deprecated, and support ends in LangSmith v0.19.
- Engine: Automatic detection, diagnosis, and resolution of recurring issues found in production traces. On BYOC, Engine runs its models on your own model providers, and you configure your GitHub App and Slack app in the LangSmith UI. See Engine on BYOC.
- Managed Deep Agents: Build and run deep agents with connectors, channels, and schedules.
Use Managed Deep Agents CLI and SDK v0.10 or later for BYOC. To get started, follow the Managed Deep Agents quickstart.
Prerequisites
Before LangChain can provision a data plane on AWS, you need the following:- A LangSmith organization on AWS: Create one at aws.smith.langchain.com, then send your organization ID to the LangChain team to enable BYOC.
- An AWS account: LangChain recommends a fresh account dedicated to LangSmith BYOC, but it is not required.
- A supported region: Pick one of the AWS regions listed above.
- An IAM role and external ID: LangChain provides the external ID. Copy it using the button next to the Data Planes header in Settings > Data Planes, then apply the
langsmith-byoc-roleTerraform module with this value to create the role LangChain assumes to provision and manage your data plane. You must use this module.
Connect these docs to your agent of choice via MCP for real-time answers.

