Skip to main content
Once your data plane is active, all API traffic for its workspaces goes to the data plane endpoint rather than to the LangSmith Cloud backend. This page explains how to route requests to the right service. The LangSmith UI routes to the correct data plane based on the workspace you have selected. Chrome and Edge users may need to allow local network access first. The rest of this page applies to your own client code and direct API calls.

Organizations, data planes, and workspaces

A BYOC deployment adds one level to the standard LangSmith resource hierarchy: the data plane, which sits between the organization and the workspace.
  • Organization: The top level. Users, roles, billing, SSO configuration, and API keys belong to the organization and live in the control plane.
  • Data plane: Belongs to an organization and represents physical separation of data. An organization can have several data planes, each in its own AWS account and region.
  • Workspace: Belongs to exactly one data plane, which you select when you create the workspace. Traces, datasets, experiments, and other agent data live in a workspace.
Nesting diagram of a BYOC deployment. An organization contains two data planes, each labeled as physical separation. The first is in us-east-1 and the second is in eu-west-1. Each data plane holds one workspace per team, and every workspace is labeled as logical separation within its data plane. Use data planes for physical separation of data, and workspaces for logical separation within a data plane. Common ways to divide data planes are:
  • Per region, such as us-east-1 and us-west-2, to keep sensitive agent data in a specific region.
  • Per environment and region, such as prod us-east-1 and dev us-east-1, to hold production and development data in separate AWS accounts.
  • Per business unit, when each unit owns its own AWS account.
Below the data plane, workspace isolation works the same as on Cloud or self-hosted. For more information, see Administration overview and Workload isolation.

Find your data plane endpoint

Each data plane has a base URL. Navigate to Settings > Data Planes to see each of your data planes, its state, and its API URL.
Data planes are provisioned with a private endpoint by default, so you need private connectivity to reach the base URL, such as Tailscale, AWS PrivateLink, or VPC peering.

Allow local network access in Chrome and Edge

When you open a workspace on a private data plane, the LangSmith UI sends requests from the LangSmith site to the data plane’s private address. Chrome and Edge treat these as local network requests and ask each user to allow them. If a user blocks or ignores the prompt, the UI cannot reach the data plane and shows a network access error, even when the user is on your private network. To allow access for one user:
  1. Open the LangSmith UI, such as https://aws.smith.langchain.com.
  2. Click the icon to the left of the address bar.
  3. If Local network access is in the list, set it to Allow. Otherwise, click Site settings in Chrome or Permissions for this site in Edge, and set Local network access to Allow.
  4. Reload the page.
To allow access for every user in your organization, push a managed browser policy. Chrome and Edge use the same policy names:
  • LocalNetworkAllowedForUrls: The current policy, in recent Chrome versions and in Edge 146 and later.
  • LocalNetworkAccessAllowedForUrls: The earlier policy, for older browser versions.
If your fleet runs a mix of versions, set both:
Each policy lists the site that makes the requests, which is the LangSmith UI URL, not the data plane URL. It therefore also covers data planes you add later. To confirm that the policy applies, open chrome://policy or edge://policy.
This setting does not replace private connectivity. Users still need a network path to the data plane, such as a VPN.

Trace to a data plane

Before running the examples, create an agent and configure agent addressing. To send traces to a workspace that lives in your data plane, point the LangSmith SDK at the data plane endpoint and authenticate with an API key scoped to a workspace in that data plane:
Create LANGSMITH_API_KEY from a workspace inside the target data plane. Traces are tenant-scoped, so an API key from a workspace on a different data plane, including a Cloud workspace, is rejected.
For a complete, runnable example, follow the Observability quickstart and substitute the environment variables above.

Route API requests

The base URL routes to different services depending on the path prefix: The LangSmith API also accepts an /api prefix, so https://<data_plane_host>/api/v1/sessions reaches the same endpoint. The SDK uses the bare data plane host, as shown in Trace to a data plane.

Trace to multiple endpoints

Use these patterns to trace to both Cloud and a data plane, or to multiple data planes.

Dual write to two endpoints

Set LANGSMITH_RUNS_ENDPOINTS to write to multiple endpoints. These replica settings use each agent environment’s tracer_session_name as project_name:

Choose the destination in agent logic

To decide where to trace at runtime, create a client per endpoint and select between them. Set LANGSMITH_CLOUD_PROJECT and LANGSMITH_BYOC_PROJECT to the corresponding agent environments’ tracer_session_name values:

See also