Regions & data residency

“Region” means two different things in Sencai, worth keeping separate: where your own workloads actually run (a setting you control per instance), and where Sencai’s own platform stores your account data (a company-level policy, not a per-organization setting today).

The region your instance runs in

Every cloud instance is created in a specific provider region - you pick it in step 2 of the New Instance wizard, and it’s shown on the instance’s detail page afterward. This is the only region setting that actually determines where a given workload’s compute, memory, and disk physically sit. Choose the region closest to your users, or the one required by your own data-handling policy for that workload.

Region choice is per instance, not organization-wide - different instances in the same organization can run in different regions and even different providers.

Tracking your own multi-region footprint

Infrastructure → Regions (/gravity/infrastructure/regions) is a reference screen for keeping track of which provider regions your organization uses - a place to record which region is your primary for a given provider, which one you’d fail over to, and a live latency reading between Sencai and each region’s public endpoint.

Note

This screen is a tracking and reference tool, not a deployment control. Adding a region here, marking it primary, or setting a replication target doesn’t provision, move, or replicate anything by itself - it’s bookkeeping your team maintains, and Sencai doesn’t act on it automatically. Latency readings (“Ping”) are measured checks; everything else on this screen is metadata you enter.

Use it to keep a shared, visible record of your organization’s intended multi-region posture - useful for planning and for showing your own disaster-recovery documentation where your regions are - rather than as a switch that makes multi-region failover happen.

Adding a region record

Add Region asks for:

• Region identifier - the provider’s own region code, for example us-east-1 or eu-west-1. This is free text, not validated against what your connected accounts actually have access to.
• Cloud provider - AWS, Google Cloud, Azure, or Hetzner.
• Display name (optional) - a human-readable label, for example “US East (N. Virginia)”.
• Primary - marks this as your primary region for that provider. Only one region per provider can be primary at a time; marking a new one demotes the previous one automatically.

Each entry also has a Status (Active, Degraded, Maintenance, or Offline) you set yourself, and a replication target field for noting which other region you’d fail over to - again, a note for your team, not a live replication link Sencai manages.

Who can manage this

Any Member, Admin, or Owner can add a region record, edit it, or trigger a latency ping; Admin or Owner is required to delete one. Viewer and Auditor can view the list but not change it.

Where Sencai’s own platform data lives

Separately from where your workloads run, Sencai the company operates under EU law and is designed to keep platform data - your account, organization, and audit records - within European jurisdictions. This is a company-level policy, not a per-organization setting you choose in the app; there’s no region picker for your own account data today.

Your workloads themselves are unaffected by this either way - they run wherever you choose when you provision or import them, including on non-EU providers or regions if that’s what you pick.

What’s next

• Provision & manage instances - where you pick the region a workload actually runs in
• Connect a cloud provider
• Privacy - how Sencai handles your organization’s data more broadly