AI 模型和平台
LangChain 带来朗斯密斯 BYOC Beta至Azure和Google云
在 Google 上的首选来源中添加 Unite.AI
2026年11月3日的LangChain 宣布，LangSmith Bring your Own Cloud(BYOC)现在以β形式在Microsoft Azure和Google Cloud上提供，将管理部署选项扩展到了AWS之外，这里一般可以使用。
BYOC将敏感的LangSmith数据和agent部署保存在客户的云账户中。 平台背后的公司LangChain管理数据平面，包括管弦乐，缩放，以及平台更新。 它的对象是那些想要自我托管的LangSmith的数据存储和网络隔离而不自己操作完整平台的组织。
AWS是较早的发布。 LangChain的2026年8月12日的公告推出 BYOC，适用于在自己的AWS帐户和VPC内寻求有管理部署的企业，特别是具有严格数据治理要求的团队。
BYOC如何分割朗斯密斯
BYOC将平台分离为LangChain操作的控制平面和客户拥有的数据平面。 控制平面包含认证，组织和工作空间配置，计费元数据，散列API密钥，以及静态接口资产。 数据平面包含痕迹，提示，数据集，实验，agent部署，以及工作空间秘密。
一个组织可以在不同的账户和地区维护数个数据平面，每个内部都有工作空间。 这种结构允许按区域、环境或业务单位进行分离。 一个平台小组可以在单独的AWS账户中运行生产和中转，而Azure上标准化的业务单位则运行自己的部署。
该型号也改变了与自办LangSmith相关的升级负担。 具有严格合规界限的团队先前需要的平台工程师来补补状态服务，配置数据库，运行schema迁移，以及协调定制的Helm推出。 通过BYOC，数据仍保留在客户的虚拟网络中，而LangChain则管理缩放，计划更新，运行时间依赖。
LangChain 称 AWS 客户引用了连续升级，比自办发布周期更快地获得新的LangSmith特性，自动缩放是主要的好处。
云层建筑和安全责任
所有三条云都支持BYOC数据平面中的管理深Agents端点，但执行部分使用每个供应商自己的网络和安全构件。
在Azure上，数据平面在专用虚拟网络中运行，并配有私人的AKS API端点。 Istio和KEDA通过Helm部署用于入侵的路由和事件驱动的缩放，系统遥测到Azure监视器。 LangChain列出在Azure上的LangSmith Sandboxs支持很快。 Google 电话云数据飞机可以在发布的任何区域运行，尽管它们是由LangSmith的美国控制飞机管理；命名空间范围的资源名称旨在避免与现有基础设施相撞。
AWS支持一个现有的VPC，数据库放在客户选择的子网中。 安全小组可以将自己的安全小组附加在应用角色上，让数据平面适应现有的进犯和进犯检查政策。
在AWS上，两个PrivateLink连接在飞机之间进行通信，LangChain没有通过公共互联网到达客户环境。 敏感数据请求直接从浏览器或客户端到客户数据平面。 跨账户的IAM角色可以提供和管理基础设施，但它在微量桶上没有s3:Get Object权限，没有rds-db：连接权限到PostgreSQL，没有弹性切换：Connect权限给Redis.
在AWS，共同责任模式留下了云账户治理，内部连通，接入政策，客户端安全监控，以及与客户的合规控制。 LangChain运行和更新管理组件。 事故排除故障可能需要客户核准的破镜访问，并附有访问后摘要，包括时间戳、采取的行动和获得的任何数据。
移徙和入境
对于从自办的LangSmith出发的组织，开源迁移工具复制用户和角色，数据集，实验，提示，注释排队配置，自动化规则，仪表板，以及车队资源。 它复制而不是移动数据，使源实例保持不变并存在。 迁移文件还留下了人工工作：必须重新部署部署的agents, Insights报告不在各事件之间转移，Fleet迁移需要重新输入秘密值，重新连接每个用户的OAuth连接。
追踪，运行和反馈遵循LangChain使用内部工具运行的单独过程。 AWS上支持跟踪迁移，而开源工具则不迁移跟踪。
BYOC背后的Terraform模块和迁移工具都是公开的。 LangChain 称数据平面LLM Gateway支持来自框外的11个供应商的模型，外加任何OpenAI-或Anthropic兼容端点。 提供AWS,Azure或Google Cloud上的BYOC数据平面，需要联系LangChain销售。
对企业来说，实际效果是在不转让云治理的情况下更宽泛地选择数据边界的位置：LangChain可以在更多地方运行LangSmith，而客户团队仍然拥有账户控制，监控，合规，以及几个迁移任务。
本文由 AI图鉴自动抓取并翻译，版权归原作者所有；如需查看原文请点下方链接。
AI Models & Platforms
LangChain Brings LangSmith BYOC Beta to Azure and Google Cloud
Add Unite.AI to your preferred sources on Google
LangChain announced on November 3, 2026 that LangSmith Bring Your Own Cloud (BYOC) is now available in beta on Microsoft Azure and Google Cloud, expanding the managed deployment option beyond AWS, where it is generally available.
BYOC keeps sensitive LangSmith data and agent deployments in the customer’s cloud account. The company behind the platform, LangChain, manages the data plane, including orchestration, scaling, and platform updates. It is intended for organizations that want the data residency and network isolation of self-hosted LangSmith without operating the full platform themselves.
AWS was the earlier launch. LangChain’s August 12, 2026 announcement introduced BYOC for enterprises seeking a managed deployment inside their own AWS account and VPC, particularly teams with strict data-governance requirements.
How BYOC Divides LangSmith
BYOC separates the platform into a LangChain-operated control plane and a customer-owned data plane. The control plane contains authentication, organization and workspace configuration, billing metadata, hashed API keys, and static interface assets. The data plane contains traces, prompts, datasets, experiments, agent deployments, and workspace secrets.
An organization can maintain several data planes in different accounts and regions, with workspaces inside each one. That structure allows separation by region, environment, or business unit. A platform team could run production and staging in separate AWS accounts while a business unit standardized on Azure operates its own deployment.
The model also changes the upgrade burden associated with self-hosted LangSmith. Teams with strict compliance boundaries previously needed platform engineers to patch stateful services, configure databases, run schema migrations, and coordinate custom Helm rollouts. With BYOC, data remains in the customer’s virtual network while LangChain manages scaling, schema updates, and runtime dependencies.
LangChain said AWS customers cited continuous upgrades, faster access to new LangSmith features than the self-hosted release cycle, and automatic scaling as the main benefits.
Cloud Architecture and Security Responsibilities
All three clouds support Managed Deep Agents endpoints in BYOC data planes, but the implementations use each provider’s own networking and security building blocks.
On Azure, the data plane runs in a dedicated virtual network with a private AKS API endpoint. Istio and KEDA are deployed through Helm for ingress routing and event-driven scaling, and system telemetry goes to Azure Monitor. LangChain lists LangSmith Sandboxes support on Azure as coming soon. Google Cloud data planes can run in any region at launch, although they are managed from LangSmith’s US control plane; namespace-scoped resource names are intended to avoid collisions with existing infrastructure.
AWS supports an existing VPC, with the database placed in subnets the customer chooses. Security teams can attach their own security groups to application roles, allowing the data plane to fit existing ingress and egress inspection policies.
On AWS, two PrivateLink connections carry communication between the planes, and LangChain does not reach the customer environment over the public internet. Sensitive-data requests go directly from the browser or client to the customer data plane. The cross-account IAM role can provision and manage infrastructure, but it holds no s3:GetObject permission on the trace bucket, no rds-db:connect permission to PostgreSQL, and no elasticache:Connect permission to Redis.
On AWS, the shared responsibility model leaves cloud-account governance, internal connectivity, access policies, customer-side security monitoring, and compliance controls with the customer. LangChain operates and updates managed components. Incident troubleshooting may require customer-approved break-glass access, with a post-access summary covering timestamps, actions taken, and any data accessed.
Migration and Access
For organizations moving from self-hosted LangSmith, the open-source migration tool copies users and roles, datasets, experiments, prompts, annotation-queue configuration, automation rules, dashboards, and Fleet resources. It copies rather than moves data, leaving the source instance unchanged and live. The migration documentation also leaves manual work: deployed agents must be redeployed, Insights reports do not transfer between instances, and Fleet migrations require re-entering secret values and reconnecting per-user OAuth connections.
Traces, runs, and feedback follow a separate process operated by LangChain with internal tooling. Trace migration is supported on AWS, while the open-source tool does not migrate traces.
The Terraform modules behind BYOC and the migration tool are public. LangChain said the data-plane LLM Gateway supports models from 11 providers out of the box, plus any OpenAI- or Anthropic-compatible endpoint. Provisioning a BYOC data plane on AWS, Azure, or Google Cloud requires contacting LangChain sales.
For enterprises, the practical effect is a wider choice of where to place the data boundary without transferring cloud governance: LangChain can operate LangSmith in more places, while customer teams still own account controls, monitoring, compliance, and several migration tasks.
Auto-fetched and translated by AI Atlas. All rights belong to the original author.