LangSmith BYOC on AWS is generally available as a managed data plane in the customer account

What we checked

• Is there a LangChain/LangSmith product page or AWS Marketplace/source URL confirming BYOC terms, architecture, and availability? confirmed. Yes. LangChain's 12 August 2026 blog and the BYOC documentation confirm general availability on AWS, the control-plane and data-plane split, Enterprise-only access, and the supported-region list. The opened AWS Marketplace listing is a different product: a customer-operated Helm chart, not the managed BYOC data plane. [1][2][9]
• Has this exact LangSmith BYOC-on-AWS announcement already been covered? unresolved. LangChain covered the launch itself in the 12 August 2026 blog and in current product docs. Searches of TechCrunch, VentureBeat, InfoQ, The Register, The New Stack, and SD Times did not return original reporting of this general-availability announcement. Missing search hits are not proof that no independent story exists. [1]
• Do agent traces and runtime data stay entirely inside the customer's AWS boundary, delivering complete data sovereignty? partly confirmed. Traces, prompts, datasets, experiments, agent deployments, workspace secrets, and related application data are stored in the customer data plane and, during normal operation, are documented as not transiting LangChain infrastructure. Users, roles, SSO configuration, billing metadata, hashed API keys, and the UI bundle remain on LangChain's control plane in us-east-2, so this is data-plane residency rather than a fully isolated LangSmith. [2][3][4]
• Is the live AWS Marketplace LangSmith listing the BYOC managed offering? refuted. The Marketplace page is LangSmith Agent Engineering Platform (Self-Hosted), delivered as a Helm chart for Amazon EKS at version 0.13.14, with a $150,000 annual platform license and a $150,000 minimum annual usage commitment. LangChain's 16 July 2025 Marketplace post describes that Helm path, not LangChain-operated BYOC. [9][10]

What we found

• LangChain's 12 August 2026 blog and the BYOC docs both state that BYOC is generally available on AWS for Enterprise customers after sales enablement. Docs list sixteen AWS regions, including ca-central-1 in Canada; the blog says fifteen regions in the US, EU, and APAC and does not mention Canada. Additional cloud providers are planned for the second half of 2026, and the control plane always runs in us-east-2 even when the data plane is elsewhere. [1][2]
• The control plane in LangChain's cloud holds authentication, organization configuration, billing metadata, API keys, and the UI bundle. The data plane in the customer account holds traces, prompts, datasets, experiments, agent deployments, workspace secrets, and other application data. Sensitive requests go from the browser or SDK to the data plane; plane-to-plane traffic uses AWS PrivateLink, the EKS API is private, and worker nodes have no public IPs. [3][1][4]
• Customers apply LangChain's langsmith-byoc-role Terraform module, merged into langchain-ai/terraform in May 2026; LangChain then provisions the data plane in about 60 to 90 minutes and operates upgrades, scaling, patching, backups, and monitoring. The IAM role is documented as unable to call s3:GetObject on traces, rds-db:connect, or elasticache:Connect, with break-glass data access requiring customer approval. There is no BYOC uptime SLA, and docs disagree on whether LangSmith upgrades run daily or weekly. [5][3][6][7][4][8]
• The live AWS Marketplace listing is not BYOC. It is LangSmith Agent Engineering Platform (Self-Hosted), a Helm chart for Amazon EKS at version 0.13.14, with a $150,000 annual platform license and a $150,000 minimum annual usage commitment. LangChain's 16 July 2025 Marketplace announcement describes that customer-operated Helm path; BYOC is billed as AWS infrastructure in the customer account plus a separate LangChain Enterprise invoice. [9][10][4][11]
• LangChain estimates a default SmithDB data plane at $3,015 to $3,770 per month in the customer account and says planes created on or after 21 October 2026 use SmithDB only, with ClickHouse support ending in LangSmith v0.19. Customer-managed encryption keys, custom DNS, install into an existing EKS cluster, and trace migration are not available. Docs now list Engine as supported on BYOC using the customer's model providers, while the August blog still called Engine planned; Managed Deep Agents and the LLM auth proxy remain planned. [12][2][4][1][13]

What it means

Treat BYOC as hybrid managed LangSmith, not full-stack isolation and not the Marketplace Helm product. If traces, prompts, datasets, and agent runtimes must stay in a designated AWS account during normal operation, the opened docs support that design. If every control surface must also stay in-region with no vendor reconcilers, use self-hosted: identity, SSO, billing metadata, and API keys remain in us-east-2, and LangChain continuously manages the cluster over PrivateLink. Review the Terraform role, break-glass process, and customer-owned CloudTrail and EKS audit logs. Budget AWS spend on the order of a few thousand dollars per month per data plane plus a custom Enterprise contract, and do not assume an uptime SLA, customer-managed keys, a custom domain, or a lift-and-shift of existing traces.

Still open

• Will AWS Marketplace publish a distinct BYOC SKU, or only billing integration alongside the self-hosted Helm listing?
• Which LangSmith upgrade cadence is current: daily, as the operations page states, or weekly, as the FAQ states?
• When will customer-managed encryption keys and non-AWS clouds ship, given CMK is not available today and other clouds are only planned for the second half of 2026?
• What contractual availability terms, if any, Enterprise sales will offer despite the FAQ stating there is no BYOC uptime SLA?