Regions
Choose a project’s region
Section titled “Choose a project’s region”When you create a project, the new-project form lists the regions you can choose. GET /regions returns the same list.
A project’s region decides where its dedicated database is created, with that database’s backups and read replicas. A project on the shared database keeps its data in the United States, whichever region you chose. Your account, your organization’s billing and settings, and the audit log are kept in the United States.
Data residency
Section titled “Data residency”Data residency keeps an organization’s project data in one region: the United States or the European Union. It is arranged as part of an Enterprise contract; contact us if you need it.
With data residency:
- Every project in the organization runs in the organization’s region. The new-project form shows the region and doesn’t offer others.
- Project databases, their backups, and stored files stay in that region. A project whose data must stay in the European Union is served from its own database there, never from the shared database.
- Your account, billing, project settings and audit logs stay in the United States.
- Verament requests are not bound to the region.
The region is chosen once, before the organization’s first project. After that it can’t be changed in place: databases and files can’t move between regions.
From the API, with a console access token, GET /orgs/{orgId}/data-region returns the organization’s region and whether it is locked.