Sovereign Agentic Website
Where hosted sovereign websites live, until their owners take them home.
This domain serves the hosted version of the Sovereign Agentic Website (SAW). Each hosted site gets its own address, name.sovereignwebsite.site, and keeps it until its owner points their own domain at it.
It is kept apart from the brand on purpose, as GitHub keeps github.io apart from github.com. The offer lives at sovereignwebsite.ai. The open pattern, which anyone can use without paying us, lives at sovereignwebsite.org.
What this domain is for
A sovereign agentic website is built by agents and owned by the person it is for. It is a repository the owner controls, holding the site as plain files, its content and its schema, the instructions for the agents and the behaviour policy that limits them, with checks and a deploy that run on any host.
Anyone can run that pattern themselves. We also offer it hosted: the factory sets up the repository and the site, the agents build it, and it is served here at its own address. This domain is only the address. The site itself is always in its owner's repository.
Sovereign, here, means owning your site and being able to move it. It is not a legal or certification claim.
How a hosted site gets here
Everything is done by CI pipelines, under an Agent Behaviour Policy that lists what each agent and each pipeline may do. Anything not listed is refused.
- A request is a folder committed to a control repository. The request holds the site's details and the GitHub account of its owner.
- The plan runs on the pull request. Checks run read-only, with no secrets, and show what would be created before anything is.
- The apply runs on merge. The pipeline creates the site's repository, seeds the site, sets its DNS record and address, enforces HTTPS, and invites the owner's GitHub account to the repository.
- The owner accepts the invitation. That step stays with them. Then the hand-over is one sentence: point your Claude at this repository, and start editing.
- Ownership moves to the owner. Every site is expected to move into its owner's ownership within three months, sooner if they ask. For now that is a soft requirement, which may become a rule.
The repository is the owner's, and it can move anywhere. The site is static files with their history, so it serves from GitHub Pages for free or from any web host. Nothing of the site lives only with us.
This pipeline follows the AgentiCCells site factory, which already works this way: one of its requests went from a commit to a live, secure site with its owner's access in 55 seconds. On sovereignwebsite.site, hosted-site requests are the next stage of the SovereignWebsite factory. Read one commit, one site, one owner.
Sites
There are no hosted sites here yet. The hosted service under the Sovereign Agentic Website name is only now being set up. When there are hosted sites, they will be listed here.
Moving your site away
Leaving should be easy, because the site was always yours. When you move, you take:
- The repository, with its history. Every change ever made is a commit you keep.
- The files. Static files that any web host can serve.
- The schema. The structure of the site and its content are files in your repository, in open formats, not an export in a format someone else chose.
- The address. Point your own domain at the site, and the name.sovereignwebsite.site address is no longer needed.
Hold your domain at your own registrar
A website you own includes its name, and the registrar is where the name is really held. We compared sixteen registrars from their own pages and, for a small business in Europe, put forward OVHcloud, Hostinger and INWX, each with its catch. Watch the renewal price, which is often far above the first year's. Read your own registrar.
Owning the files means you can move. It does not move them for you.
Read more
- Sovereign Agentic Website: the name, and why sovereign and agentic.
- Sovereignty you can move: why where your data is hosted is not sovereignty.
- No lock-in: why being able to leave is the difference that matters most.
- The website cell: the repository, the designs and the hand-over.
- One commit, one site, one owner: how a commit becomes a site with its owner.
- Your own registrar: where to hold your domain.
Articles by Dinis Cruz.