LangSmith BYOC is generally available on AWS and in beta on Azure and Google Cloud. Agent traces and evaluations stay in the customer's cloud account, while LangChain retains a separate control plane for authentication, workspace configuration and billing metadata.
LangChain has expanded LangSmith Bring Your Own Cloud to the three major enterprise clouds. Its announcement says AWS is generally available, while Azure and Google Cloud are in beta. The meaningful distinction is architectural: LangChain operates the platform while defined categories of agent data remain inside the customer's cloud account.
Where agent data and control metadata live
Traces, evaluations, datasets, prompts and agent deployments stay in the customer's cloud account. LangChain manages the data plane for orchestration, scaling and platform updates. Its BYOC documentation says the control plane holds authentication, organisation and workspace configuration, billing metadata, hashed API keys and static UI assets.
This separation addresses one data locality concern without resolving every question about where platform information resides. Keeping agent traces inside a customer's account does not mean every record used to operate LangSmith remains there.
On Google Cloud, data planes can run in any region at launch. LangSmith manages them from its US control plane, so residency and control plane location remain separate questions. The architecture guide describes that separation, while the LangSmith documentation covers setup and operations.
The distinction matters when deployment requirements extend beyond the location of prompts and traces to authentication, workspace information or billing metadata. A customer hosted data plane addresses one part of that requirement; the separate control plane requires its own assessment.
What the rollout status establishes
AWS has reached general availability, while Azure and Google Cloud remain in beta. That establishes the current release stages, rather than comparative capability, production usage or operational maturity.
The chart encodes general availability as 2 and beta as 1. Those values are categorical labels, not measurements of service quality, customer adoption or relative readiness.
LangChain says BYOC is generally available on AWS and in beta on Azure and Google Cloud.
View data
| Cloud | Release stage, GA equals 2 and beta equals 1 |
|---|---|
| AWS | 2 |
| Azure | 1 |
| Google Cloud | 1 |
Managed operations leave a measurable question unanswered
The commercial proposition is a division of operational responsibility. LangChain manages updates, scaling and support, while customers still need to assess identity, network policy, region placement and the metadata handled by the control plane.
That arrangement could reduce the work involved in maintaining a self hosted platform. The article's evidence, however, provides no staffing counts, operating cost comparison or customer migration figures with which to quantify the benefit. More supported clouds establish wider deployment choice, not demonstrated operating savings.
There are two distinct deployment considerations. Where the main constraint is keeping traces, prompts and evaluations inside a customer's own cloud account, BYOC offers an architectural option. Where the requirement also covers the location and handling of control metadata, the separate control plane remains material.
Azure and Google Cloud could progress from beta to general availability, but that would establish a change in release status rather than demand. Migration from self hosted installations would be more informative about adoption, although migration alone could not establish the financial benefit of managed operations.
Scenarios over three years
The first observable milestone is whether Azure and Google Cloud move from beta to general availability. Evidence of customer migrations, operating responsibilities and staffing costs would be needed to judge whether the managed arrangement delivers meaningful economic benefits.
What settles it
Until that evidence appears, the defensible conclusion is narrower. LangSmith has expanded cloud coverage while retaining a distinction between customer hosted agent data and vendor managed control metadata. That boundary, rather than the number of supported clouds, remains the central question for deployments with strict data location requirements.