How it works
From an interview to your own first change.
A team of agents interviews you, builds the site, shows you five designs, and hands it over. From then on you change it by talking to your own AI, inside a behaviour policy that keeps the site yours while agents work on it. And you can move it whenever you like.
Six steps
-
An interview
Most people do not know what they want from a website until someone asks them the right questions. So the first step is an interview by an AI, about five things: what the site is for and who should read it; the sections you want; the photos, videos and documents you have; three websites you like and why; and what to avoid, and what must stay private. It ends with a one-page brief, in your words, that you can read and correct.
-
Your material, in any way that suits
A zip of photos, documents and videos; an email; links to what is already public, such as a profile, a portfolio or an existing site; or the files handed over during the interview itself, so the AI that interviewed you can start building.
-
A team of agents builds it
Even the smallest site is a team, not one prompt: a conductor who takes the brief and hands out the work, a researcher who reads what you gave and what is public, with sources, a designer, a developer who builds and releases the site with its checks, and a security reviewer. Each has a written job description and a behaviour policy, and each signs its work.
-
Five designs to choose from
People find it hard to describe a design, and easy to point at one. The five designs are inspired by the sites you said you like: not copies, but the qualities you named, in five different readings. You pick one; the chosen one goes live and the others are kept.
-
Hand-over
The site is handed over to you, in a repository you control, with everything it needs to be changed safely. See what you receive.
-
The milestone: your first change
Everything aims at one moment: you change your own site by talking to your AI. A sentence, a photo, a CV, and the site is different, checked and live. So the hand-over is not the end; the last step is your first change, made with you, and confirmed live.
The interview as the first step is a design that is still being built. Source: Start with an interview and Partners sell, we build.
What you receive
-
A repository in your name
The site's files, its content and its schema, with every change since the first.
-
A live site on its address
On a hosted site, its own address on sovereignwebsite.site until you point your own domain at it.
-
Five designs
The chosen one live, and the others kept.
-
Instructions for your AI
A CLAUDE.md file written for you, so your AI knows what the site is, how to change words and photos, the checks, and what not to touch.
-
A behaviour policy and checks
A policy for any agent that works on the site, and checks that run before anything goes live.
-
Ownership
The repository moves into your ownership within three months, sooner if you ask. This is a soft requirement for now.
Source: The sovereign website, The website cell and No lock-in.
Next: a website with a team inside
The sites handed over today carry a CLAUDE.md and a behaviour policy for one agent, your own. The next step, not yet built, is to hand over the team itself: six or seven agents already set up and coordinated in your site's repository, each with a brief and a behaviour policy.
Conductor
The one you talk to, in plain words. It turns a request into a plan, hands out the work, reports back, and asks before anything goes live.
Designer
Every new page in the style you chose.
Writer
The words, in your voice, from what you say and send.
Developer
Builds the change, keeps the checks green, and publishes once you approve.
Reviewer
Checks prices, claims, consent, privacy and secrets before you see anything.
Translator
Keeps every page in each of the site's languages.
Keeper
The weekly care: broken links, speed, accessibility, a certificate, the domain's renewal date.
Because the team lives in your repository, it is yours as the site is: move the site and the team moves with it. It runs on your own AI account, at its cost and within its limits, and wakes when there is a request or a weekly check.
Source: A website with a team inside. The roles are a proposal.
Changing it by talking, with guard rails
You change the site with your own AI, not through our platform. Because it is your AI, the site can do whatever it can connect to: a new page, a rewritten section, a CV read and turned into an updated experience section, a feed from another system.
An AI that edits your site can also publish something private, embed a script from somewhere unsafe, or break a page. So every site ships with guard rails:
- A behaviour policy that says what any agent working on the site may and may not do.
- Every change is a commit, and anything can be undone.
- Checks and a leak scan run before anything goes live.
- A security agent reviews what each change exposes.
Where an owner wants a person watching over it, that is a service a partner can sell.
Source: The website cell and Static against the platforms.
Moving it
The site is files, built once and served as they are. There is no server code running, no database, no plugin to patch, and no login page on the site itself to attack. There are no cookies unless you add them, and no tracking by us. So any host that can serve files can serve it, without changes: GitHub Pages for free, or any web host, in any region, or your own computer.
Being able to move is the claim; having moved is the proof. Our sites deploy today to GitHub Pages only. A pipeline that deploys the same commit to many hosts, one of them in Europe and one your own machine, is the next step and does not exist yet. When it does, this site will be its first proof.
Source: What is a sovereign website and Static against the platforms. See where your own site stands on the maturity model.
Already have a site, or a domain?
Moving from a platform
Your existing site is the material. Moving from Wix, Squarespace or WordPress.
Your name, in your name
A website you own includes its address. Owning your domain.