Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

Story

LangSmith BYOC launches on AWS, Azure, and Google Cloud

AI summary

LangChain announced that LangSmith Bring Your Own Cloud (BYOC) is generally available on AWS and in beta on Azure and Google Cloud. BYOC places the data plane, including traces, prompts, datasets, experiments, agent deployments, and workspace secrets, in the customer's cloud account, while LangChain manages scaling, orchestration, schema updates, and runtime dependencies. The open-source migration tool can move workspace resources from self-hosted LangSmith, while trace migration is currently available only on AWS.

In-depth insight

The launch gives enterprise agent teams more deployment choices across AWS, Azure, and Google Cloud while retaining customer ownership of sensitive telemetry data, according to LangChain Blog.

LangSmith Bring Your Own Cloud (BYOC) now runs on AWS (GA), Azure (Beta), and Google Cloud (Beta). Your traces, evals, datasets, prompts, and agent deployments stay in your own cloud account, on the cloud you choose, and LangChain manages the data plane for you, from orchestration and scaling to platform updates.

How BYOC splits LangSmith

By splitting the control plane and data plane in two, BYOC provides greater flexibily to decide where agents run and where telemetry lives, without taking on the work of running LangSmith. LangChain runs the control plane, which holds auth, org and workspace config, billing metadata, hashed API keys, and static UI assets. You own the data plane, which holds everything sensitive, from traces, prompts, and datasets to experiments, agent deployments, and workspace secrets.

‍

An organization can hold several data planes, each in its specific account and region, and each data plane holds its workspaces. This lets you split data planes by region, environment, or business unit.

For example, a platform team might run production and staging data planes in separate AWS accounts, while a business unit that standardized on Azure runs its own, separate BYOC deployment on Azure. Each team's traces land in the account that team owns.

#LangSmith#LangChain#AWS#Azure#Google Cloud#Terraform

Original · 4 min readRead the original
Group chat

No comments yet. Start the conversation.