Skip to main content

Private connectivity (Enterprise)

Enterprise only. Private connectivity is available exclusively for Enterprise customers. Contact your account representative or sales@langchain.dev to enable this feature.
Enterprise customers can connect to LangSmith without exposing traffic to the public internet using AWS PrivateLink, GCP Private Service Connect (PSC), or Azure Private Link. Customers on AWS can connect to LangSmith via AWS PrivateLink, providing private connectivity from any VPC. Cross-region connectivity is supported natively.

Endpoint service name

Setup

1. Request access: Contact your account representative or sales@langchain.dev with your AWS account ID. LangChain will add your account to the endpoint service’s allowed principals list. 2. Create an Interface VPC Endpoint in your AWS account. Attach a security group that allows TCP 443 inbound from your VPC CIDR (or from the instances that need to reach LangSmith):
3. Wait for acceptance. LangChain will accept the connection. The endpoint status will change from pendingAcceptance to available. Allow a few minutes after acceptance for the change to fully propagate before testing connectivity.

Configure DNS

Configure DNS so that aws.api.smith.langchain.com resolves to your VPC endpoint’s private DNS name within your VPC. You can use any private DNS solution: Route 53 Private Hosted Zones, a corporate DNS resolver, or any DNS server reachable from your VPC. First, get your endpoint’s DNS name:
Then, create a CNAME record for aws.api.smith.langchain.com pointing to that DNS name. Here’s an example using Route 53:

Verify connectivity

From an EC2 instance or container in your VPC:

GCP Private Service Connect

Enterprise customers on GCP can connect to LangSmith via Private Service Connect (PSC), providing private connectivity without exposing traffic to the public internet.

Service attachment URIs

Use the following service attachment URIs to create a PSC endpoint in your VPC:

PSC domains

After setup, use the following domains to connect to LangSmith over your PSC connection:

Setup

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 PSC endpoint

Create a forwarding rule in your VPC targeting the service attachment:

Configure DNS

Create a private DNS zone in your VPC and add an A record pointing to the PSC endpoint IP:

Verify connectivity

From a VM in your VPC:
Customers on Azure can connect to the LangSmith Azure SaaS API through Azure Private Link. A private endpoint in your virtual network (VNet) connects to the LangSmith Private Link service.

Request access

Contact your account representative or sales@langchain.dev with your Azure subscription ID and desired endpoint region. LangChain adds your subscription to the Private Link service auto-approval list. LangChain also provides the service resource ID. Wait for LangChain to confirm that subscription access is enabled before creating your private endpoint. New connections from an allowlisted subscription are approved automatically. Connections from other subscriptions require manual approval.

Create a private endpoint

Use an existing subnet in your VNet. Set the endpoint location to the subnet’s region. Replace the placeholders with your Azure resource details and the service resource ID provided by LangChain. The following Terraform example uses the AzureRM provider:
Terraform
Apply the configuration and wait until the connection status is Approved before testing connectivity. If the connection remains Pending, send the private endpoint ID to LangChain to confirm subscription access and resolve the pending request.

Configure DNS

Configure private DNS so that azure.api.smith.langchain.com resolves to your private endpoint’s IP address inside your VNet. Add the following resources to the same Terraform configuration:
Terraform
If you use custom DNS servers, configure them to resolve azure.api.smith.langchain.com to the private endpoint IP. Linking an Azure private DNS zone alone does not configure your custom resolver. This example configures private access to the API hostname only. For private access to the LangSmith UI or other services, contact LangChain for additional hostnames.

Verify connectivity

From a VM or container in your VNet, confirm that DNS returns the private endpoint IP and HTTPS succeeds:
Keep using https://azure.api.smith.langchain.com as your LangSmith API endpoint. API keys and workspace permissions still apply.