Why BYOC

BYOC is for organizations that want the data ownership and network isolation of self-hosting, without spending engineering time building and operating the full LangSmith platform themselves. The data plane stays in your AWS account, and LangChain manages the LangSmith infrastructure.

​

What BYOC provides

• Faster time to value: You provision an AWS account and the required roles, and LangChain handles the rest of the provisioning flow.
• Customer-owned data: Databases, object storage, and compute run in infrastructure that you own.
• Private networking: The data plane runs inside your AWS account and can connect privately to your systems without exposing them publicly.
• SaaS-aligned architecture: The data plane is provisioned using a tried and tested architecture.
• Monitoring out of the box: LangChain has visibility into data plane health and metrics, and can proactively identify, investigate, and remediate issues.
• Less platform maintenance: Your engineering team spends more time driving value with LangSmith and less time managing LangSmith infrastructure, upgrades, scaling, and operational drift.
• Automatic upgrades: You receive automatic upgrades to a recent version of LangSmith.
• Lower barrier to multi-environment and multi-region rollout: Run multiple LangSmith data planes across environments, accounts, or regions without rebuilding the architecture from scratch each time.

​

Compare BYOC and self-hosted

The table below compares the two deployment models:

​

Move from self-hosted to BYOC

You can move to BYOC from an existing self-hosted deployment. Traces are not migrated today, but users, roles, datasets, experiments, prompts, annotation queue configuration, automation rules, and dashboards can be copied over. To plan a migration, contact the LangChain sales team.

​

See also

• BYOC overview
• BYOC architecture
• Self-hosted LangSmith

---