Skip to main content
The Cloud hosting option is a fully managed model where LangChain hosts and operates all LangSmith infrastructure and services:
If you’re ready to deploy your app to LangSmith Cloud (AWS or GCP), follow the Cloud deployment quickstart or the full setup guide. This page explains the Cloud managed architecture for reference.
Cloud deployment: LangChain hosts and manages all components including the UI, APIs, and your Agent Servers.

​
Cloud architecture and scalability

This section is only relevant for cloud-managed LangSmith at https://smith.langchain.com, https://eu.smith.langchain.com, https://apac.smith.langchain.com, and https://aws.smith.langchain.com.For information on the Self-hosted LangSmith solution, refer to the Self-hosted documentation.
LangSmith is hosted on Google Cloud Platform (GCP) for the US, EU, and APAC SaaS regions and on Amazon Web Services (AWS) for the AWS-hosted US SaaS region. The platform is designed to be highly scalable. Many customers run production workloads on LangSmith for LLM application observability, evaluation, and agent deployment. The US-based LangSmith service (default GCP region) is hosted in the us-central1 (Iowa) region of GCP.
The EU-based LangSmith service is available and hosted in the europe-west4 (Netherlands) region of GCP. If you are interested in an Enterprise plan in this region, contact our sales team.
As of April 2026, LangSmith SaaS is available on AWS in us-east-2 (Ohio).
As of May 2026, LangSmith SaaS is available in APAC on GCP in australia-southeast1 (Sydney).

​
Regional storage

The resources and services in this table are stored in the location corresponding to the URL where sign-up occurred (GCP US, GCP EU, GCP APAC, or AWS US). Cloud-managed LangSmith uses Supabase for authentication/authorization and ClickHouse Cloud for the data warehouse. See the Regions FAQ for more information.

​
Region-independent storage

Data listed here is stored exclusively in the US:
  • Payment and billing information with Stripe and Metronome

​
GCP services

The following applies to the US, EU, and APAC SaaS regions on GCP. LangSmith is composed of the following services, all hosted on Google Kubernetes Engine (GKE):
  • LangSmith Frontend: serves the LangSmith UI.
  • LangSmith Backend: serves the LangSmith API.
  • LangSmith Platform Backend: handles authentication and other high-volume tasks. (Internal service)
  • LangSmith Playground: handles forwarding requests to various LLM providers for the Playground feature.
  • LangSmith Queue: handles processing of asynchronous tasks. (Internal service)
LangSmith uses the following GCP storage services:
  • Google Cloud Storage (GCS) for runs inputs and outputs.
  • Google Cloud SQL PostgreSQL for transactional workloads.
  • Google Cloud Memorystore for Redis for queuing and caching.
  • Clickhouse Cloud on GCP for trace ingestion and analytics. Our services connect to Clickhouse Cloud, which is hosted in the same GCP region, via a private endpoint.
Some additional GCP services we use include:
  • Google Cloud Load Balancer for routing traffic to the LangSmith services.
  • Google Cloud CDN for caching static assets.
  • Google Cloud Armor for security and rate limits. For more information on rate limits we enforce, please refer to Rate limits.

​
AWS services

The following applies to the AWS US SaaS region in us-east-2 (Ohio). The same logical LangSmith components run on Amazon EKS instead of GKE. LangSmith is composed of the following services, all hosted on Amazon EKS:
  • LangSmith Frontend: serves the LangSmith UI.
  • LangSmith Backend: serves the LangSmith API.
  • LangSmith Platform Backend: handles authentication and other high-volume tasks. (Internal service)
  • LangSmith Playground: handles forwarding requests to various LLM providers for the Playground feature.
  • LangSmith Queue: handles processing of asynchronous tasks. (Internal service)
LangSmith uses the following AWS storage and data services:
  • Amazon S3 for runs inputs and outputs.
  • Amazon RDS for PostgreSQL for transactional workloads.
  • Amazon ElastiCache for Redis for queuing and caching.
  • ClickHouse Cloud over AWS PrivateLink in us-east-2 for trace ingestion and analytics, consistent with the regional storage table above.
Some additional AWS services we use include:
  • Elastic Load Balancing (Network Load Balancers) and Istio ingress for routing traffic to the LangSmith services. Documented API rate limits are enforced at the Istio ingress gateway. For details, see Rate limits.
  • Amazon CloudFront for caching static assets (including the web UI hostname aws.smith.langchain.com).
  • AWS WAF on CloudFront for managed rule groups at the edge (for example, AWS Managed Rules common protections and Bot Control).
Light mode overviewDark mode overview

​
Allowlisting IP addresses

​
Egress from LangChain SaaS

All traffic leaving LangSmith services will be routed through a NAT gateway. All traffic will appear to originate from the following IP addresses: It may be helpful to allowlist these IP addresses if connecting to your own AzureOpenAI service or other endpoints that may be required by the Playground or Online Evaluation.
Traffic from agents deployed on LangSmith Deployment egresses through a separate set of NAT IPs. For that list, refer to Allowlist IP addresses in the Cloud platform features reference.

​
Ingress into LangChain SaaS

The LangChain endpoints map to the following static IP addresses for traffic that terminates on our GCP load balancers (US/EU/APAC) or, for AWS US, on the Network Load Balancer in us-east-2 (API and gateway hostnames): You may need to allowlist these to enable traffic from your private network to LangSmith SaaS endpoints (api.smith.langchain.com, smith.langchain.com, beacon.langchain.com, eu.api.smith.langchain.com, eu.smith.langchain.com, eu.beacon.langchain.com, apac.api.smith.langchain.com, apac.smith.langchain.com, apac.beacon.langchain.com, aws.api.smith.langchain.com, aws.smith.langchain.com).

​
Private connectivity (Enterprise)