What you own when we hand it over.
Five things, each with an account and a name on it, and one test that decides whether the sentence is true.
| What | Where it lives | Whose it is |
|---|---|---|
| The source code | A git repository, with every change and the reason for it | Yours on payment. The repository is transferred with its full history, not a zip of the final files. |
| The domain | A registrar, in your name | Yours. One you already have stays where it is and the login is yours; one we register for you is moved into your name at handover, and the registrar's own window decides the day it completes. |
| The hosting | A host account of your own | Yours to run or move. The site is files and a small worker, and no deploy of it needs our account. |
| The content | In the repository, and in the store the site reads | Yours, and exportable. Text and images come out in a shape another system can read. |
| The accounts | Analytics, mail and payments | Yours, in your name and on your card. We are a user while we work, and we are removed at handover. |
The test. On a machine that has never seen us: clone it, install it, deploy it, and the site answers. If the install reaches a private package, a path on our machines, a bucket we own or a key only we hold, then the sentence at the top of this page is false, and it is our defect rather than your problem.
What we keep, and the licence you get
We keep the reader that crawled your site, the panel that publishes it, and the estate's own components. You get a perpetual, royalty-free, non-exclusive licence to use them inside your site, and no right to resell them. The open-source libraries the site is built on keep their own licences, and no one can hand over a right they do not hold.
The day it happens
Payment first, then the keys, in one sitting: the repository is transferred, the domain is moved or re-pointed, the credentials are issued, and the licence text is a file in the tree.
If you stop paying
Cancel, and the site keeps serving the last build it was given. Only publishing stops. Nothing else goes dark: not the domain, not the host account, not the content.
Editing without a developer is something a static site can have, and any developer can add it to this repository. The monthly exists so that you do not have to: it is the watching, the restores and the work, never the hosting and never the licence.
What is warranted, and what is not
Warranted, in these words:
- It renders as audited on the day it is handed over.
- A clean clone installs and deploys on a machine that has never seen us.
- Every page we captured answers at its address.
- The licence text travels in the repository.
Not warranted, said before you ask:
- Edits made after handover.
- Rights to content you supplied.
- Anything added afterwards, including a plugin.
- A score, because nobody can promise one.
How to leave
The six questions a careful buyer asks, each answered in one sentence:
- Whose name is the domain in, and can I log in today? Yours, at your registrar, and the login is in your hands from handover.
- Where does the code live, and who owns that account? A repository you own, which we work in and hand over with its history.
- If I take this to another developer on Monday, what do they need from you? Nothing: they clone it, install it and deploy it with your credentials.
- What stops working the day I stop paying you? Publishing stops, and the site keeps serving what was last built.
- Is there a per-site or per-seat fee to a third party, and what is it over three years? Only your host's own plan, at the host's own price, with no licence fee to us and nothing per seat.
- Can I export the content, and in what format? Yes: the repository, plus a JSON export of every row the site reads.