Private Networking

Private Link for AWS and Private Service Connect for GCP is now available in Chroma Cloud.

Today, we’re introducing Private Networking support for Chroma Cloud on AWS and GCP.

With Private Networking, your Chroma Cloud traffic stays on cloud-provider private networks end-to-end, improving security posture and reducing latency.

Private Networking lets Chroma Cloud behave like a first-party service inside your VPC, without changing your application code.

Private Networking lowers your cloud costs as traffic stays within the AWS or GCP network.

When Private Networking is enabled, a private endpoint is provisioned in your VPC and registers an internal DNS record inside your VPC. That DNS entry maps api.trychroma.com directly to Chroma Cloud over the provider’s private network. From your application’s point of view, nothing changes, same hostname, same config.

Traffic no longer traverses the public internet, it flows privately from your VPC to ours.

• Private, VPC-to-VPC connectivity to Chroma Cloud
• No public IP exposure for production traffic
• Lower and more predictable latency
• No ingress or egress network fees

Get Started

Private Networking is available today to Enterprise Plan customers for AWS and GCP. Support is configured per-tenant, our team will work with you to set up the endpoint and DNS routing correctly for your environment.

If you’re interested in enabling it for your deployment, or want to understand whether it’s a good fit for your architecture, reach out to us, and we’ll help you get set up. support@trychroma.com