Data residency
This page is for procurement and security reviews: where Updawg keeps your data, and what crosses a border. It says what is true today, and marks what is planned.
Regions
Section titled “Regions”Every organization’s data lives in one region, chosen when the organization is created and not changed afterwards.
| Region | Location | Status |
|---|---|---|
eu |
Google Cloud, Frankfurt (europe-west3) |
Live. Every organization today. |
us |
Google Cloud, Iowa (us-central1) |
Live. |
You choose the region when you create an organization. It is on the
organization (region in the API) and on each of your memberships in
GET /v1/me, with the API address to use for it (api_url). You sign in once,
at the EU; the portal then talks to each organization’s own region.
What lives in your organization’s region
Section titled “What lives in your organization’s region”Everything about your fleet:
- hosts, their inventories, pending updates and exposures;
- proposals, policies, approvals, rollouts, jobs and their logs;
- the audit log;
- notification channels, API tokens, enrolment tokens, single sign-on and SCIM configuration;
- your organization’s job-signing keys, held in that region’s Cloud KMS;
- usage records used for billing.
Each region has its own database, its own servers and its own keys. A region’s
API refuses requests for an organization in another region with
421 wrong-region and the address to use instead. It does not forward them, so
your organization’s requests and data are never handled by the other region.
What is shared across regions
Section titled “What is shared across regions”A small directory, in the EU, holds what is needed to sign you in and to find your organizations:
- your account: email address, name, and the sign-in identities you linked;
- sessions;
- each organization’s name, slug, region and plan, who belongs to it and with which role.
It holds nothing about any fleet. Public data, such as security advisories and distribution release dates, is fetched by each region on its own.
The directory is the EU region’s database. A US organization’s region keeps its own copy of who is in it and with which role, pushed from the directory when it changes; that copy is the names and email addresses of that organization’s members, and nothing about anybody else.
What leaves the region
Section titled “What leaves the region”- Email. Notifications, digests and sign-in links are sent through Updawg’s mail relay in Germany, whichever region the organization is in. A notification carries what it is about: host names, package names, advisory IDs.
- Payments. Stripe processes billing for every customer. It receives your billing contact, the plan and the number of active hosts per day, never fleet data.
- Support. Mail you send to help@updawg.net becomes a ticket in our helpdesk (Atlassian).
- Monitoring. Operational metrics (counts and latencies, no tenant content) from every region go to one monitoring project.
Moving an organization
Section titled “Moving an organization”Not offered through the API. If you need an organization in another region, talk to us: it is an export and import that we run, not a setting.