创建

登录 ReadmeX

或

了解我们如何处理你的信息: 隐私政策

ReadmeX

陪你读懂 AI 动态

今天,想先了解什么?

选一份动态总结,或直接聊聊你的问题。

社区和关注动态总结只属于你自己。

资讯

LangSmith BYOC登陆三大云平台

AI 总结

LangChain宣布LangSmith Bring Your Own Cloud(BYOC)在AWS正式可用,并在Azure和Google Cloud进入测试阶段。BYOC将追踪数据、提示词、数据集、实验、智能体部署和工作区密钥等数据面内容留在客户自己的云账户中,由LangChain负责扩缩容、编排、模式更新及运行时依赖。开源迁移工具可从自托管LangSmith迁移工作区资源,但追踪数据迁移目前仅支持AWS。

深度见解

据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

原文约 4 分钟读完阅读原文
群聊

还没有评论,来说说你的看法。