LangSmith BYOC Expands to AWS, Azure, Google Cloud

LangChain pushed LangSmith's Bring Your Own Cloud option past AWS, where it's been generally available, into Azure and Google Cloud, both now in beta. The pitch is straightforward: traces, evals, datasets, prompts, and agent deployments stay inside a customer's own cloud account, on whichever of the three providers that customer already runs on, while LangChain handles the orchestration, scaling, and updates that keep the system running.

That split matters because of how LangSmith BYOC is architected. The setup separates a control plane, managed by LangChain, from a data plane, managed by the customer, and the boundary between them determines what LangChain can see versus what never leaves a company's own infrastructure. For organizations juggling multiple teams, regions, or compliance regimes, that architecture decides whether a single deployment can serve everyone or whether separate business units need entirely separate setups.

The expansion also reflects a tradeoff LangChain has been navigating since BYOC launched on AWS: how to give companies the data residency guarantees of self-hosting without saddling them with the operational burden that used to come with it.