If you’re ready to deploy your app to Cloud, follow the Cloud deployment quickstart or the full setup guide. This page explains the Cloud managed architecture for reference.
The Cloud option is a fully managed model where LangChain hosts and operates all LangSmith infrastructure and services:
Fully managed infrastructure: LangChain handles all infrastructure, updates, scaling, and maintenance.
Deploy from GitHub: Connect your repositories and deploy with a few clicks.
Automated CI/CD: Build process is handled automatically by the platform.
LangSmith is deployed on Google Cloud Platform (GCP) for the US and EU 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 deployed in the us-central1 (Iowa) region of GCP.
The EU-based LangSmith service is now available (as of mid-July 2024) and is deployed 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).
The resources and services in this table are stored in the location corresponding to the URL where sign-up occurred (US (GCP), EU (GCP), or US (AWS)). Cloud-managed LangSmith uses Supabase for authentication/authorization and ClickHouse Cloud for the data warehouse.
The following applies to the US and EU SaaS regions on GCP.LangSmith is composed of the following services, all deployed 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.
The following applies to the US (AWS) 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 deployed 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).
All traffic leaving LangSmith services will be routed through a NAT gateway. All traffic will appear to originate from the following IP addresses:
US (GCP)
EU (GCP)
US (AWS)
34.59.65.97
34.13.192.67
18.188.147.158
34.67.51.221
34.147.105.64
18.219.86.202
34.46.212.37
34.90.22.166
3.21.57.192
34.132.150.88
34.147.36.213
35.188.222.201
34.32.137.113
34.58.194.127
34.91.238.184
34.59.97.173
35.204.101.241
104.198.162.55
35.204.48.32
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.
The LangChain endpoints map to the following static IP addresses for traffic that terminates on our GCP load balancers (US/EU) or, for US (AWS), on the Network Load Balancer in us-east-2 (API and gateway hostnames):
US (GCP)
EU (GCP)
US (AWS)
34.8.121.39
34.95.92.214
3.129.27.169
34.107.251.234
34.13.73.122
13.58.107.119
16.59.151.49
16.59.98.147
3.134.146.243
3.150.87.246
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, aws.api.smith.langchain.com, aws.smith.langchain.com).
Enterprise only. Private Service Connect is available exclusively for Enterprise customers. Contact your account representative or sales@langchain.dev to enable this feature.
Enterprise customers on GCP can connect to LangSmith via Private Service Connect (PSC), providing private connectivity without exposing traffic to the public internet.
Request access: Contact your account representative or sales@langchain.dev with your GCP project ID. LangChain will add your project to the service attachment’s allowed consumer list.After access is granted, create a PSC endpoint and configure DNS using either the gcloud CLI or Terraform.
Create a private DNS zone in your VPC and add an A record pointing to the PSC endpoint IP:
# Create a private DNS zonegcloud dns managed-zones create langsmith-psc \ --dns-name="<REGION>.p.api.smith.langchain.com." \ --visibility=private \ --networks=<YOUR_VPC_NETWORK># Add an A record pointing to the PSC endpoint IPgcloud dns record-sets create "<REGION>.p.api.smith.langchain.com." \ --zone=langsmith-psc \ --type=A \ --rrdatas=<PSC_ENDPOINT_IP>
LangSmith enforces rate limits on API endpoints to ensure service stability and fair usage. The following table shows the rate limits for different endpoints in both US and EU regions. Note that:
Rate limits are expressed as count / interval where count is the number of requests allowed within the interval (in seconds). For example, 2000 / 10 means 2000 requests per 10 seconds.
When no HTTP method is specified in the endpoint column, the rate limit applies to all HTTP methods for that endpoint.
When a specific method is listed (e.g., POST, GET), the rate limit applies only to that method.
