Explanation
Regions and availability
How Sovrain spreads organizations across regional servers, why an organization's data lives in its region, and what that design means when a server restarts.
When you create an organization, you choose a data region, and Sovrain tells you it cannot be moved later. This page explains what a region is in Sovrain, what lives in it, and what the design means for availability, including what it does not offer.
One server per region
A Sovrain deployment is a small set of servers, one per region. Each organization lives on exactly one of them: its database file and its password manager attachments are stored on the server of the region chosen at registration, and that server alone answers requests for the organization.
One of the servers also plays the part of the landing server. It serves the public pages at sovrain.net,
including the registration form, and it keeps the list of organization addresses that are taken, together with the
region each one belongs to. It does not store the data of organizations in other regions. When Jane registers
Acme, the landing server reserves acme, points acme.sovrain.net at the server of the region she chose, and asks
that server to create the organization. From then on, people’s browsers and applications talk to Acme’s regional
server directly.
Why the data lives where you put it
Choosing a region is choosing where the organization’s live data is stored: its file sits on that region’s server, and Sovrain does not move it to another region. The hosted service also keeps encrypted daily backups of each server’s data outside that server, and outgoing email goes through an external mail provider.
The same property explains why the region cannot be changed. Moving an organization would mean moving its file to another server and repointing its address, while every session, token and pending change is in flight. Sovrain does not offer that, so the region is worth choosing with care at registration.
The region does not appear in the organization’s address. acme.sovrain.net is the same whichever region holds
Acme, so applications never need to know which region they are talking to.
What a restart means
Each region is served by one server and nothing stands in for it. When that server restarts, for an upgrade or after a failure, the organizations of that region are unavailable until it is back. People cannot sign in, and applications cannot complete sign-ins or refresh tokens through Sovrain during that time. A planned restart lets running requests finish first and is usually a short interruption; an unplanned failure lasts as long as it takes to bring the server back.
Some things carry on regardless. People who are already signed in to an application keep working there, because
the application’s own session does not depend on Sovrain once it has started. Organizations in other regions are
not affected at all. And if the landing server is down, organizations in other regions keep working, because their
addresses point at their own regional servers; only the pages at sovrain.net stop: registering new organizations
and finding your organization from the main sign-in page. An address freed while the landing server is down stays
reserved.
A few things held only in memory start fresh after a restart, most visibly the counters behind most rate limits.
What this design does not offer
Sovrain does not provide high availability. There is no second server in a region waiting to take over, no automatic failover, and no uptime commitment. This is the honest consequence of the simple design: one server and one file per organization are easy to reason about, to back up and to keep in one place, but they make each server a single point of failure for its region.
For most organizations, a short interruption at sign-in is an inconvenience rather than an emergency, as long as applications keep their own sessions. If your applications cannot tolerate even that, plan around it: let them keep sessions long enough to ride out a restart, and keep your own exports of the organization (see Back up your organization).
Related pages
- Organizations and their addresses
- Sessions and sign-out
- Add a region, for operators who run Sovrain themselves
- Server configuration