Residency
Residency pins where a namespace stores and processes its records, Files and analytics, set per Startup or per Tenant.
Residency pins the region where a namespace stores and processes its records, Files and analytics copy. A Startup sets it for itself, and a Tenant can set its own.
Contract
residency is a Setting with the value us or eu. It is set before a namespace writes its first record and locks once that record exists.
| Rule | Detail |
|---|---|
| Default | Inherited from the Studio, nearest holder first |
| What stays in region | The owner database, Files, the analytics copy, backups and every step that reads them |
| Tenants | A Tenant takes its own region at provisioning, whatever its Startup's region |
| Model calls | Routed to models served inside the region |
| Visitors without Consent | Counted by a daily-rotating hash; no cookie is set and no IP address is stored |
| Region on record | Every Action records the region it ran in |
Residency is read by the Privacy and Compliance Systems, which answer a Customer's data-location questions from these records.
Verbs
| Verb | Object | Event |
|---|---|---|
| Setting.update | Setting | Setting.updated |
Interfaces
Example
shiftboard.app, scheduling Software for clinics, runs in us. When a clinic in the EU signs up, its Tenant is provisioned in eu, and that clinic's records never leave the EU.