Change your own site in minutes. Your visitors load nothing but the page.
We build your site by hand, host it as static files on your own domain, and give you an editor at a separate address behind its own login. Type the new words, press Save and Publish, and the site is re-rendered and live in about one to two minutes.
Three pages, one site. Each describes something that runs today.
A site we host has three parts worth knowing: the editor you type into, the static output a visitor loads, and the layers that decide who can open the editor at all. Each has its own page, written from the code behind it.
What do you host for me?
A static website, built by a person for your business and served from Cloudflare Pages on your own domain. Your site has its own page templates and one content file that holds the words. We render the templates against that file into plain HTML, and those files are what a visitor downloads. No CMS answers behind the public page. No database is consulted per request. No editor code reaches the browser.
That is the whole line: the static output, the deploy that ships it, and an editor at a separate address. It runs on client sites and on our own concept sites today. Every site in it was built by hand.
Can I change the words myself?
Yes, from the editor at its own address, never on your site. Open the link we send, enter the code Cloudflare Access emails to your work address, and your pages load as tabs. Each tab lists that page's fields with a plain label and the current text. Move between pages without losing anything. A tab is marked once you have touched it, so you can see what you changed before you publish. One button, Save and Publish, sends the lot.
The fields are the words: headings, paragraphs, service descriptions, questions and answers, the footer line. A fact your business publishes, a price, an opening hour, a rating, can be kept out of the editable fields, so rewording a page cannot change a number by accident. A few sentences carry a placeholder in double braces that the site fills in at build time; the editor tells you to edit the words around it and leave it alone. See the editor, field by field.
What happens when I press Save?
Four things, in order. Dashes that word processors insert are normalised. The content file is written. The site is re-rendered from its templates against the new content, and a bad value is refused at that step. The result deploys to Cloudflare Pages, and the editor tells you the site will update in about one to two minutes.
A failed render publishes nothing. The previous content file is put back and the editor says so, instead of shipping a broken page. Every deploy to Cloudflare Pages runs through one guarded script. It refuses a build that is missing the site's own marker text, refuses review furniture such as a draft banner on a live client domain, and refuses a live domain with no real 404 page, because without one Cloudflare Pages answers every wrong address with the homepage at status 200. Where your project has a preview address, larger changes made by our team are staged there before they reach your domain.
Will the editor slow my site down?
No. The editor is not on the site. It is a separate application on a separate hostname, and your public pages are the rendered output only: static HTML and the assets it references, with zero runtime CMS and zero extra JavaScript for editing. A page builder that ships its editor to the visitor loads that weight on every visit, whether or not anyone is editing. Here the visitor loads the page and nothing else, so speed is decided by the page itself, not by the tool you edit it with.
A blog post reaches your site the same way. The piece is slotted into the site's data, the affected pages are regenerated, and the site is redeployed, still static. Why the public page stays static and the pipeline that writes the posts each have their own page.
Who can edit my site?
The people whose work email we have listed for your site, plus our own team, and nobody else. Three layers sit between the internet and the editor. First, the editor's hostname is its own Cloudflare Access application with its own guest list, and Access emails a One-Time PIN before anything loads, so you need no account and no password. Second, the tunnel behind that hostname answers only the editor's own paths; every other path returns a 404, so the hostname cannot reach the rest of our API. Third, a per-site allowlist maps each verified email to the sites it may edit, so nobody can open another client's editor.
The link we send you is plain. It carries no key or token, because your Access session is what identifies you. We add or remove addresses for you, and someone not on the list is told to ask us rather than shown anything. The three layers, in detail, and the product's write paths and seat rules are both published.
Where do my form leads go?
To your team by email and, where your site is wired to one, to your lead sheet, both server-side. The form posts to a small function on the site's own hosting, not in the visitor's browser. It emails the submission to your team and, on sites wired to a sheet, appends a row: when it arrived, who it was, what they wrote, and where the visit came from. The email is the first job and the sheet is best effort, so a sheet hiccup never loses a lead that has already been emailed.
The Leads view in the Command Center reads that same sheet, newest first, with our own test submissions filtered out. The site and the dashboard agree because they share one record. How that ledger is compared with what Google Ads and GA4 report is its own page, and the situation it exists for shows why the form is the record a web lead is counted from.
The line, in one table.
| Part | What it is | Where it runs |
|---|---|---|
| Public site | Static files: no runtime CMS, no editor code | Cloudflare Pages, on your domain |
| Editor | Your pages as tabs, plain labels, Save and Publish | Its own hostname, behind its own Cloudflare Access app |
| Sign-in | One-Time PIN to an allowlisted work email; no account, no password | Cloudflare Access |
| Save | Validate, write the content file, re-render, redeploy | Our backend, then Cloudflare Pages |
| Failed render | Previous content restored, nothing published | Our backend |
| Forms | Server-side handler: emails your team, appends your lead sheet | A function on the site's own hosting |
| Site generator | None. Every site is built by a person | Nowhere yet |
There is no generator that turns a prompt into a site: every site in the line was built by a person for one business, and the editor exists so you can reword that work without opening a ticket.
Questions, answered.
Do I need an account to edit my site?
No. Cloudflare Access emails a One-Time PIN to your work address, which must be on the list for your site. There is no password to keep, and the link we send carries no secret.
Can a save break my site?
A failed save publishes nothing. If the re-render fails, the previous content is put back and the editor tells you. The deploy step also refuses a build that is missing the site's marker, and a live domain with no real 404 page.
How long until my change is live?
About one to two minutes after you press Save and Publish. The editor says so when the save is accepted.
Is there a site builder or generator?
No. Every site in the line was built by a person for one business, and the editor changes the words on that site.
My site is on WordPress. Does any of this apply?
The editor is for the sites we build and host. A WordPress site keeps its own editor, the content engine publishes to it through its API, and the Website view in the Command Center shows its status either way.
Do leads from the site reach the Command Center?
Yes, where your site's form is wired to a lead sheet. The handler appends each submission server-side and the Leads view reads that sheet newest first.
See it running
before you decide.
The demo is the real product on a fictional company, with no form in front of it. Pricing is three published tiers. Setup on your own accounts takes two to four weeks.
Open the live demo See pricing
New here? See what the Command Center is. Prefer to write? Send us the one thing you want to know.
- Refreshed when you open itLive data on page load, never a monthly PDF
- Counted from your own formsLeads recorded server-side, compared daily with Ads and GA4
- Four answer engines, measuredChatGPT, Gemini, Claude and Grok, with a published denominator
- A review-first queue on every sendEvery draft waits in a review-first queue and every send is logged.