Regions and data residency
Vela deploys your indexes across 8 regions. You pick the region when you create the index, and it determines where the vectors are stored, backed up and queried.
A decision made when the index is created
Every index belongs to one region and one only. That choice fixes the physical location of the vectors, the metadata and the backups.
Put the index as close as possible to your application services to cut latency, or as close as possible to your data residency obligations. One account can hold indexes in several regions at once.
Three ways to place an index
The mode is declared at creation and stays changeable afterwards, with no reindexing.
Single-region index
The index lives in one region. It is the simplest configuration and the fastest to read from.
- p99 latency: 12 ms
- Capacity: 1 billion vectors
- Dimensions: up to 4096
- Backups in the same region
Multi-region replication
The same index is replicated across two or three regions. Queries are served by the closest replica.
- 2 to 3 regions per index
- Asynchronous write replication
- Automatic read failover
- Identical recall: 99.2 %
Strict residency
The index is locked to a geographic zone. No replica or backup may leave it.
- Documented GDPR scope
- Encryption at rest and in transit
- Exportable audit logs
- Replication confined to the zone
The 8 available regions
Every region hosts complete shards: an index is never split across two regions without explicit replication.
Europe and the Americas
Paris
eu-paris-1 — EU residency
Frankfurt
eu-frankfurt-1 — EU residency
London
eu-london-1 — UK residency
North Virginia
us-east-1 — US residency
Oregon
us-west-2 — US residency
São Paulo
sa-east-1 — Brazil residency
Asia-Pacific
Singapore
ap-southeast-1 — Singapore residency
Sydney
ap-southeast-2 — Australia residency
Replication options
Single region
Minimum latency, nothing leaves the zone
Double replication
Two regions, automatic failover
Triple replication
Three regions, reads from the nearest
What the region determines
An index's region commits its compliance scope, its backups and its observed latency.
Contact
contact@vela.dev
Documentation
docs.vela.dev
Languages
Multilingual search across 40 languages
What choosing a region commits
- Where the vectors and metadata are stored
- The latency measured from your application services
- Which regions this index may replicate to
- The GDPR compliance scope applied to the index
- Where backups and snapshots are held
- The retention zone for audit logs
Three points before you choose
Technical benchmarks measured on our reference indexes.
A k-NN query served from the closest region stays under 12 ms at the p99, metadata filters included.
An index never leaves its region: vectors, metadata and backups stay in the zone chosen at creation.
Multi-region replication keeps recall at 99.2 % and fails reads over without reindexing or downtime.
Ready to choose your region?
Create an index in the region of your choice and measure the latency from your own services.