BYOC on GCP is in beta. Network details can change between releases. The values on this page are the current defaults.
Address ranges
All subnets come from thevpc_cidr you choose, a range from /16 to /18. All have Private Google Access on.
A
/18 VPC has no room for the pod range, so its pods use 192.168.0.0/18, and the VPC must not overlap that range. Use a /17 or /16 to keep every range inside your VPC.
GKE services take no range from the VPC. GKE assigns them its Google-managed range, 34.118.224.0/20, which stays inside the cluster and is not exported over VPC peering. Older data planes keep 192.168.0.0/18 for pods and 192.168.64.0/18 for services.
The VPC is one regional VPC with custom subnets. Cloud NAT uses one static external IP address, which you can allowlist to accept traffic from the data plane. Cloud NAT logging is set to errors only.
Connect your network
The data plane endpoint is internal by default: an internal passthrough load balancer in the GKE subnet, with global access, so clients in any region of a connected network can reach it. You choose public or internal when you create the data plane. To reach an internal endpoint:- Connect your network to the data plane VPC, for example with VPC peering or Cloud VPN. Peering exchanges subnet routes, including the GKE pod range, so choose a
vpc_cidrthat does not overlap your networks. With a/18VPC, your networks must not overlap192.168.0.0/18either. - Make the hostname resolve from your network. The address record is in a private zone that only the data plane VPC can see, so the private address is never published.
MTU
The VPC uses the GCP default MTU, 1460 bytes. If you connect the VPC to a network with a smaller MTU, such as a hub VPC or an interconnect at 1440 bytes, setmtu_bytes when you create the data plane. LangSmith accepts 1300 to 8896.
Private Service Connect
- LangChain publishes a service attachment in
us-central1. LangSmith automatically adds your project to its accept list during data plane provisioning. No manual project allowlisting is required. - The data plane creates the endpoint: an internal address in the control plane endpoint subnet, and a forwarding rule to the service attachment. Data planes in other regions reach the endpoint through global access.
- A private DNS zone for
us-central1.p.api.smith.langchain.com, visible only in the data plane VPC, points at the endpoint. - Private Service Connect carries traffic from the data plane to the control plane only. The control plane reaches the cluster through the GKE DNS-based endpoint.
Private Google Access
The data plane reaches Google APIs overprivate.googleapis.com, so that traffic stays on Google’s network and does not depend on the VPC’s default route. LangSmith creates the following in the data plane VPC:
- Routes:
199.36.153.8/30(private.googleapis.com) and34.126.0.0/18(direct connectivity for some Google APIs), both with the default internet gateway as next hop. Their names start withlangsmith-. - Private DNS zones:
googleapis.com,pkg.dev, andgcr.ioresolve toprivate.googleapis.com. Arep.googleapis.comzone keeps regional endpoints, such asaiplatform.us-central1.rep.googleapis.com, on their public addresses. The zones are visible only in the data plane VPC.
DNS and ingress
- Hostname:
<first 8 characters of the data plane ID>.gcp.langchain-byoc.com. LangChain owns the parent zone. - Public zone: A public Cloud DNS zone for the hostname in your project, which LangChain delegates from the parent zone.
- Public endpoint: An external passthrough load balancer. The hostname resolves on the internet.
- Internal endpoint (default): An internal passthrough load balancer in the GKE subnet, with global access. The address record is in a private zone, visible only in the data plane VPC, so the private address is never published. The public zone stays for the delegation and the certificate challenges.
- TLS: A Let’s Encrypt certificate. HTTP redirects to HTTPS.
- Gateway hardening: The gateway normalizes paths before routing, rejects request bodies over 100 MiB, limits requests per gateway pod, and denies
TRACE,TRACK, andCONNECT. - Control plane paths: Paths such as sign-in are forwarded to the control plane over Private Service Connect.
Container images
LangSmith and its add-ons pull their images over Private Google Access from LangChain’s Artifact Registry repository,us-docker.pkg.dev/langchain-artifacts/langsmith-byoc. The add-ons are cert-manager, trust-manager, External Secrets, Istio, and KEDA. No images come from Docker Hub, Quay, or GitHub Container Registry.
Outbound traffic
The following traffic needs no internet access:- Control plane: Private Service Connect.
- Google APIs and images: Private Google Access.
- Cloud SQL and Memorystore: Private IP and Private Service Connect.
If your network inspects TLS, exclude these destinations from inspection. Workloads in the data plane do not trust your inspection CA.
See also
Connect these docs to your agent of choice via MCP for real-time answers.

