The sovereignty maturity model
Where is your website, from 0 to 5?
A sovereign website is a website you own and can move. Owning is the easy part; moving is where it fails. Sovereignty is not yes or no: it is how far you can move, on your terms.
One part in the middle is enough
Once there is a piece of proprietary technology in the middle of a site, it does not matter how small it is: you cannot move the site. Nobody else can move it for you either. You cannot even pay someone to move it, because they would have to rebuild that part first. A paid plugin, a platform's form handler, a hosting company's special function, an agency's private framework: any one of them is enough.
And lock-in hides in more than one place: where the domain is registered, the technology underneath, and the platform it runs on. A site that is portable in its code but registered in someone else's name is not sovereign. Nor is one in your name that only runs on one company's servers.
The one-minute self-check
Answer the five questions in order. Stop at your first no: that is your level. If you answer yes to all five, your site is at level 5.
-
Can you export your words and images?
- Yes: go on to question 2.
- No: your site is at level 0, rented.
-
Can you take the whole site with you, design and functions included, not only the words?
- Yes: go on to question 3.
- No: your site is at level 1, exportable.
-
Does it depend on nothing you do not control: no paid plugin, theme or agency component that holds it where it is?
- Yes: go on to question 4.
- No: your site is at level 2, a part you do not control.
-
Could any host that serves plain files run it without changes, and is its domain registered in your own name, at a registrar you chose?
Both parts must be yes.
- Yes: go on to question 5.
- No: your site is at level 3, open, on one host.
-
Is it deployed today on more than one host?
- Yes: your site is at level 5, sovereign and proven.
- No: your site is at level 4, portable.
Nothing you answer here is sent anywhere: this page has no form, no script and no tracking. The self-check is a guide to the model, not a certificate.
The six levels
-
Level 0, rented
A hosted builder decides everything, and little leaves but some content. Most website platforms sit here by their own terms of service.
What it would take to move up
Get your words and images out in formats you can read without the tool that made them. Where a platform does not export at all, your own public pages are still yours to read: an agent can start from them. See moving your site.
-
Level 1, exportable
You can export your words and images; the design and the functions stay behind.
What it would take to move up
Hold the whole site, design included, as files in a repository in your name, built on open software rather than on the platform. In practice that means rebuilding the site from its exported content, which is what the five designs are for.
-
Level 2, self-hosted, with a part you do not control
The software is open, but one paid plugin, theme or agency component holds the site where it is.
What it would take to move up
Replace that one part with open, commodity parts, so that anyone could rebuild or move the site without its supplier. However small the part, the site is held until it is gone.
-
Level 3, open, on one host
Open code in your repository, but tied to one host's special features. A corporate site built on one cloud provider's proprietary services sits here at best, however well it is engineered.
What it would take to move up
Remove the dependence on that host's special features, so that the site is plain files any static host can serve without changes. And register the domain in your own name, at a registrar you chose: see owning your domain.
-
Level 4, portable
Plain files and open tools; any static host can serve it; your domain at your registrar. The website cell is here today, and so is this site.
What it would take to move up
Deploy the same commit, regularly, on more than one host, ideally one of them in Europe and one your own machine, so that moving is a thing that already happened, not a promise.
-
Level 5, sovereign and proven
Portable, and proven by being deployed on many hosts, one of them in Europe and one your own machine.
What it takes to stay here
Keep deploying everywhere, so that every host keeps working. The pipeline that deploys one commit to many hosts is the next step for our own sites, and does not exist yet.
Source: What is a sovereign website and Designing sovereignwebsite.ai. The advice on moving up is drawn from the definition of each level.
Seven principles
The model follows from seven principles any site can be tested against, whoever built it. A sovereign website could be made by hand. A website is sovereign when:
- You own it. The site, its content and its history are in a repository in your name, and the domain is registered to you, at a registrar you chose.
- You can move it. It runs on any commodity host that can serve files, without changes.
- Nothing in the middle is proprietary. Every part it needs to build and run is open and commodity; if one part is not, the site is not sovereign, however small that part is.
- Its content and schema are open. Words, data and their structure are in open formats you can read without the tool that made them.
- Anyone can change it. You, any developer, or your own AI, without asking the company that built it.
- What works on it is bounded. Agents and tools that change it work inside a behaviour policy that says what they may touch.
- It is proven, not claimed. It is deployed, regularly, on more than one host, so that moving is a thing that already happened, not a promise.
The principles live at sovereignwebsite.org, with the open pattern.
What this does not claim
- The principles and the model are a proposal, written to be argued with and improved.
- Where a platform sits on the model is read from its own published terms; a given site may do better or worse.
- The every-host pipeline does not exist yet; only GitHub Pages is in use today.