Regions
Your data stays where the law says it must.
Many governments and regulators require certain data to stay inside their borders. Ahura OS is built so a partition lives in one region, and everything that belongs to it stays there.
Regional endpoints
One live region today, with the others on the way. Each region is a complete, separate deployment.
Americas
- Live
N. Virginia
United States
Default region. US sector rules such as HIPAA and state privacy laws.
api.ahuraos.app
- Coming soon
Oregon
United States
US West residency and latency, second US region for resilience.
us-west.api.ahuraos.app (planned)
- Coming soon
Montréal
Canada
Canadian public-sector and some provincial rules favouring in-country data.
ca.api.ahuraos.app (planned)
- Coming soon
São Paulo
Brazil
LGPD and Brazilian financial-sector expectations.
br.api.ahuraos.app (planned)
Europe
- Coming soon
Ireland
Ireland (EU)
GDPR: keeps EU personal data inside the EU.
eu.api.ahuraos.app (planned)
- Coming soon
Frankfurt
Germany (EU)
GDPR plus strict German public-sector and banking expectations.
de.api.ahuraos.app (planned)
- Coming soon
London
United Kingdom
UK GDPR and public-sector requirements for UK-held data.
uk.api.ahuraos.app (planned)
- Coming soon
Zürich
Switzerland
Swiss data protection law and banking secrecy expectations.
ch.api.ahuraos.app (planned)
Asia Pacific
- Coming soon
Sydney
Australia
Australian government and regulated sectors that require data to stay onshore.
au.api.ahuraos.app (planned)
- Coming soon
Tokyo
Japan
APPI rules on cross-border transfer of personal data.
jp.api.ahuraos.app (planned)
- Coming soon
Singapore
Singapore
PDPA transfer obligations and regional hub for Southeast Asia.
sg.api.ahuraos.app (planned)
- Coming soon
Mumbai
India
DPDP Act and sector localisation rules, notably in payments.
in.api.ahuraos.app (planned)
Middle East and Africa
- Coming soon
UAE
United Arab Emirates
UAE data protection law and government cloud policies.
ae.api.ahuraos.app (planned)
- Coming soon
Cape Town
South Africa
POPIA conditions on transfers outside South Africa.
za.api.ahuraos.app (planned)
Regions and addresses marked coming soon are planned and may change. Need a region that is not listed? Locations are chosen by customer demand and legal requirements.
Data sovereignty
Why where your data lives matters.
Rules differ by country, but the pattern is the same: personal, financial and government data is often required, or strongly expected, to stay in-country.
- Australia
- Government agencies and many regulated bodies are expected to hold sensitive data onshore, and the Privacy Act makes organisations accountable for personal information sent overseas.
- European Union
- GDPR restricts moving personal data outside the EU unless strict safeguards exist. After the Schrems II ruling, many EU organisations simply keep data in the EU.
- United Kingdom and Switzerland
- UK GDPR and the Swiss data protection act follow similar transfer rules, and public bodies and banks often require local hosting.
- Canada
- Privacy law makes organisations accountable for data they transfer, and some public bodies and provinces prefer or require it to stay in Canada.
- India
- The DPDP Act allows the government to restrict transfers to some countries, and regulators have required certain payments data to be stored in India.
- Singapore, Japan, Brazil, South Africa
- Each applies conditions to sending personal data abroad, such as comparable protection or consent, which is far simpler to meet by keeping data local.
- United States
- No single residency law, but sector rules such as HIPAA, state privacy laws and federal procurement requirements shape where and how data is held.
A general summary, not legal advice. Requirements vary by sector and change over time. Check what applies to you.
How Ahura keeps it local
Residency built into the platform.
A home region per partition
You choose where a partition lives when you create it. Its memory, files, records, graph and workflow history are stored there.
Backups and archives stay put
Frozen partitions and archives are kept in the same region as the live data, not copied somewhere cheaper.
Keys stay in region
Agent identity keys are created and used in the region of the partition they belong to.
No silent replication
Data does not move between regions unless you explicitly set that up.
Same API everywhere
Every region speaks the same MCP interface, so moving an agent to a new region means changing one address.