Data residency — bRRAIn Docs

Where your data lives — region options, sovereign-cloud options, and how to change.

Data residency

You choose where your data lives. This page lists the available regions and explains how the choice works.

How residency works

At organization creation you pick a data residency region. From that moment forward:

  • Your Vault, your graph, your files, your audit log, your backups — all stay in that region.
  • All compute that touches your data runs in that region.
  • All replication (for high-availability tiers) stays within the same region or in geographically proximate regions per your contract.

Region choice is a one-time decision. Changing region requires a vault migration (a coordinated process with our support team), not a self-service control.

Standard regions

Standard hosted regions (available on all paid tiers):

| Region | Location | Plan availability | |---|---|---| | us-east-1 | Virginia, USA | All tiers | | us-east-2 | Ohio, USA | All tiers | | us-west-2 | Oregon, USA | Team and above | | ca-central-1 | Quebec, Canada | Business and above | | eu-frankfurt-1 | Frankfurt, Germany | Team and above | | eu-ireland-1 | Dublin, Ireland | Team and above | | eu-paris-1 | Paris, France | Business and above | | uk-london-1 | London, United Kingdom | Business and above | | ap-tokyo-1 | Tokyo, Japan | Team and above | | ap-singapore-1 | Singapore | Team and above | | ap-sydney-1 | Sydney, Australia | Business and above | | sa-saopaulo-1 | São Paulo, Brazil | Business and above | | me-bahrain-1 | Manama, Bahrain | Enterprise |

Additional regions may be available; the live list is at brrain.io/regions.

Sovereign-cloud regions

Sovereign-Cloud customers can pin to:

  • A specific country (subject to availability).
  • A specific data center.
  • An on-premises deployment in your facility.
  • A hybrid of cloud and on-premises.

Available sovereign-cloud regions cover most G20 countries and many additional jurisdictions on request. We work with you on a per-engagement basis to confirm availability and configure infrastructure.

What "stays in region" means

For your chosen region:

  • Storage — primary storage for Vault, files, backups.
  • Compute — your brain pod and all marketplace extension processes.
  • Inference — Handler responses are computed in-region.
  • Audit log — recorded and retained in-region.
  • Backups — encrypted backups are stored in-region by default. Cross-region backup is available as opt-in for disaster-recovery purposes; you choose where.

For all regions, management traffic (provisioning, billing, support tooling) flows through bRRAIn's central infrastructure. This is a thin metadata channel; it does not include your data records.

Data sovereignty controls

Beyond region, sovereignty-bound customers may need:

  • Encryption keys held outside our infrastructure. Available via BYOK (see Encryption) and HSM-backed sovereign-cloud setups.
  • No bRRAIn engineer access without authorization. Standard posture; documented in Zero-trust model.
  • Customer-controlled audit logs. Audit log can be exported continuously to your SIEM.
  • No subprocessor data flow. Sovereign-cloud setups can be configured to remove all subprocessor dependencies (no third-party object storage, no third-party email, no third-party payment processing — these revert to your nominated providers or to manual processes).

Cross-region considerations

If your organization spans regions:

  • You can have one organization per region (each with its own residency).
  • Cross-organization data sharing via federation respects each side's residency — federated data is read in real time, not copied across regions.
  • bR2bR (bRRAIn-to-bRRAIn) cross-organization queries cross region only if both sides authorize.

Changing residency

Region migration is a coordinated process:

  1. You request migration via support.
  2. We schedule a migration window.
  3. We provision a target pod in the new region.
  4. We replicate Vault and storage to the new region.
  5. We freeze writes briefly for cutover.
  6. We flip your subdomain DNS to the new pod.
  7. We retire the old region.

End-to-end typically 24–72 hours depending on Vault size. Vault remains read-only briefly during cutover; writes pause for minutes to a couple of hours.

Where to next