Multi-Geo Data Residency for Self-Hosted LangSmith

Question

For a self-hosted LangSmith customer with data residency requirements across multiple geos, can they have a single organization and separate data by geo at the workspace level? Or do they need one organization per geo?

Answer

Customers with multi-geo data residency requirements need multiple separate LangSmith instances, each with its own organization. The recommended approach is one instance and one org per geographic region.

It is not currently possible to separate data by geographic region at the workspace level within a single organization. Workspaces within an org all share the same underlying infrastructure and data storage, so they cannot guarantee data residency isolation.

Recommended Setup

Key Takeaways

Each geo requires its own dedicated self-hosted LangSmith instance. Workspace-level separation within a single org does not provide data residency guarantees. Users in different regions will need to access their respective regional instance. Each instance is managed independently with its own org, users, and configuration.