Regions

turbopuffer supports multiple regions, choose the one closest to your backend. The default is gcp/us-central-1.

In addition to these public clusters, we run dedicated clusters in various other regions for single-tenancy customers. We can spin up dedicated clusters in hours upon request, email us. We will continue to expand public regions with demand.

import turbopuffer as tpuf
# Choose region from turbopuffer.com/docs/regions, api.turbopuffer.com is default
# note: turbopuffer-python v0.1.16 or later is required
tpuf.api_base_url = "https://gcp-us-east4.turbopuffer.com"

To move data between regions, use the export and upsert APIs with a client for each region.

Cross-Cloud Latency

Since response times for vector search are typically above 10ms, the contribution of cross-cloud latency is generally acceptable. Traffic within a cloud provider's region is lower latency (< 1ms) than cross-cloud traffic (1-10ms), even if the providers are geographically close. For larger customers, cross-cloud interconnects can be set up to reduce network latency.

Cross-Cloud Egress Fees

A common misconception is that as long as your vendor is in the same Cloud as you (e.g. AWS ↔️ AWS), you will be charged lower networking fees. This is generally not the case, as most providers' API endpoints point to public IPs that route through the public internet, unless you've set up a private connect (see below; you'll know if you have). Any traffic leaving your VPC incurs $0.05-0.09/GB Internet egress fees (AWS / GCP/ Azure).

Egress networking fees are charged to you on your bill by your provider. For larger customers, we will work with you to set up AWS Private Link, GCP Private Service Connect, Azure Private Link or an interconnect to reduce networking fees to $0.01/GB. Unless you're transferring tens of billions of vectors per month, this is unlikely to have a large effect on your bill (1B vectors = 6TB would be $600 of egress, not a significant issue).