---
type: "post"
id: "langsmith-byoc-is-now-available-on-aws-azure-8b699c"
slug: "langsmith-byoc-is-now-available-on-aws-azure-8b699c"
title: "LangSmith BYOC is now available on AWS, Azure, and Google Cloud"
description: "LangChain says LangSmith Bring Your Own Cloud (BYOC) is generally available on AWS and in beta on Azure and Google Cloud."
retrieval_nugget: "LangChain says LangSmith Bring Your Own Cloud (BYOC) is generally available on AWS and in beta on Azure and Google Cloud. It keeps the LangSmith data plane in a customer-owned cloud account while LangChain operates it, offering teams a middle ground between a managed service and maintaining self-hosted infrastructure."
published_at: "2026-11-03"
updated_at: "2026-11-03"
record_date: "2026-11-03"
date_kind: "published_at"
topics: ["google"]
entities: ["LangChain","LangSmith","AWS","Azure","Google Cloud","Managed Deep Agents","Istio","KEDA"]
related_patterns: ["agent-security-moves-to-runtime-boundaries"]
novelty_label: "new_fact"
what_changed: "LangSmith BYOC expands beyond its prior AWS availability: it is now offered on Azure and Google Cloud as well, with AWS GA and the new cloud options in beta."
prior_refs: []
source_url: "https://www.langchain.com/blog/langsmith-byoc-aws-gc-azure"
source_urls: ["https://www.langchain.com/blog/langsmith-byoc-aws-gc-azure"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:langsmith-byoc-is-now-available-on-aws-azure-8b699c"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/langsmith-byoc-is-now-available-on-aws-azure-8b699c/","markdown":"https://newruntime.com/posts/langsmith-byoc-is-now-available-on-aws-azure-8b699c.md","json":"https://newruntime.com/posts/langsmith-byoc-is-now-available-on-aws-azure-8b699c.json"}
markdown_url: "https://newruntime.com/posts/langsmith-byoc-is-now-available-on-aws-azure-8b699c.md"
---

# LangSmith BYOC is now available on AWS, Azure, and Google Cloud

## Retrieval answer

LangChain says LangSmith Bring Your Own Cloud (BYOC) is generally available on AWS and in beta on Azure and Google Cloud. It keeps the LangSmith data plane in a customer-owned cloud account while LangChain operates it, offering teams a middle ground between a managed service and maintaining self-hosted infrastructure.

## Summary

LangChain says LangSmith Bring Your Own Cloud (BYOC) is generally available on AWS and in beta on Azure and Google Cloud. It keeps the LangSmith data plane in a customer-owned cloud account while LangChain operates it, offering teams a middle ground between a managed service and maintaining self-hosted infrastructure.

## What happened

LangChain announced that LangSmith BYOC runs on AWS (GA), Azure (Beta), and Google Cloud (Beta). The product splits the service into a control plane operated by LangChain and data planes owned by the customer. LangChain’s control plane holds authentication, organization and workspace configuration, billing metadata, hashed API keys, and static UI assets. The customer’s data plane holds sensitive operational material: traces, prompts, datasets, experiments, agent deployments, and workspace secrets.

An organization can have multiple data planes, each in a specified cloud account and region, with workspaces inside each plane. LangChain’s examples include separating production and staging across AWS accounts, or running a separate deployment for a business unit that has standardized on Azure. The company says the arrangement lets teams decide where agents run and where telemetry resides without taking on the work of running LangSmith themselves.

The cloud implementations use each provider’s network, identity, and security building blocks. Azure deploys into a dedicated virtual network with a private AKS API endpoint; LangChain deploys Istio and KEDA with Helm for ingress routing and event-driven scaling, and sends system telemetry to Azure Monitor. Support for LangSmith Sandboxes on Azure is described as coming soon. Google Cloud data planes can run in any region at launch, but are managed from LangSmith’s US control plane; resources use namespace-scoped names to avoid collisions with existing infrastructure. AWS deployments run inside an existing VPC, with the database in customer-selected subnets and the option to attach customer security groups to application roles. The company says all three clouds also run Managed Deep Agents endpoints.

LangChain frames BYOC as a way to retain the data-location boundary of self-hosted LangSmith while shifting infrastructure operations to the vendor. It says it handles scaling, schema updates, and runtime dependencies, and describes AWS customers benefiting from continuous upgrades, access to new features soon after they ship on LangSmith Cloud, and automatic scaling. Those are vendor-reported benefits; the announcement provides no quantified performance or cost comparisons.

For migration, LangChain provides an open-source tool that reads from a live self-hosted instance without taking it offline. It transfers users and roles, datasets, experiments, prompts, annotation queue configuration, automation rules, dashboards, and Fleet resources. Traces, runs, and feedback are migrated separately by LangChain using internal tooling; trace migration is available on AWS today. BYOC is provisioned by contacting sales. The company also says its Terraform modules and migration tool are public, and that the data-plane LLM Gateway supports 11 providers out of the box plus OpenAI- or Anthropic-compatible endpoints.

## What the archive adds

This is a new LangSmith deployment announcement, but it extends the archive’s recent coverage of cloud placement and vendor-managed infrastructure. [Vercel’s BYOC on AWS](https://newruntime.com/posts/bring-your-own-cloud-on-aws-is-now-bf9422/) moved function execution into the customer’s cloud without transferring operation of the whole platform. LangSmith’s announcement similarly separates customer-controlled data placement from vendor-operated infrastructure, now across three clouds, with only AWS generally available.

## Trend signal

This supports the shift toward agent platforms that preserve customer control over sensitive execution data while vendors operate the surrounding system. It is adjacent to, rather than direct evidence for, [agent security moves to runtime boundaries](https://newruntime.com/patterns/agent-security-moves-to-runtime-boundaries/): BYOC describes where data and workloads run, but does not establish that runtime permissions or enforcement are stronger.

## Why now

LangChain says it launched BYOC on AWS in August and that customer demand prompted it to bring the option to Azure and Google Cloud. The announcement therefore presents the two beta cloud deployments as an expansion of an existing AWS offering, not a simultaneous launch of three GA services.

## Why it matters

For teams building agents under data residency or network constraints, the choice is not simply between a vendor-hosted service and operating every component themselves. BYOC is intended to retain traces, prompts, deployments, and secrets in the team’s account while reducing the work of patching stateful services, managing databases, scheduling maintenance windows, and applying upgrades.

That boundary can make observability and evaluation infrastructure easier to adopt in organizations that cannot send telemetry to a shared SaaS data plane. Multiple planes also allow teams to separate environments or business units. But the split requires a careful review: LangChain still operates the control plane and manages the data plane, while the customer remains responsible for its cloud account and network context. Teams should confirm what crosses that boundary, how identities and access are governed, and whether the regional behavior matches their requirements—particularly since Google Cloud data planes are managed from a US control plane at launch.

## Limits and uncertainty

The announcement is a vendor description, not an independent security assessment or customer study. It does not quantify deployment cost, operational savings, availability, latency, or migration duration. It also does not fully specify the shared-responsibility model in the supplied material. Azure and Google Cloud are beta, Azure Sandboxes are not yet available, and trace migration is stated to be available on AWS only. The source does not establish when those gaps will close or whether all clouds have feature parity.

## Skill to build now

Before choosing a hosted agent-observability platform, draw a data-flow and ownership map for one real deployment: list traces, prompts, datasets, secrets, agent workloads, credentials, and control metadata, then mark the cloud account, region, and operator for each. Use it to test whether a BYOC architecture satisfies your residency and network requirements, and identify what a migration plan must preserve.

## Reader takeaway

LangSmith BYOC offers customer-account data placement with vendor-operated infrastructure, but availability differs by cloud: AWS is GA; Azure and Google Cloud remain beta. The practical decision is whether the split between customer data plane and LangChain control plane fits your security, operations, and migration requirements—not simply whether the product says “your cloud.”

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Google](https://newruntime.com/topics/google.md): Explore the google topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Sources](https://newruntime.com/sources/): See the original sources this archive cites.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)