Demo
Try it, with nothing to sign up for.
Not a sales call and not a video. The admin and the published site, running in your browser tab with nothing behind them — so you can change anything, publish it and break it, and there is no account to make and nothing for anybody else to see.
It is not a mock-up either: the blocks, the block renderer, the theme tokens and the editor’s own forms are all the product’s, imported. What is simulated is persistence, sign-in, uploads and email.
No account · nothing saved · seven professions and six themes
Run it
Or run the whole thing, in one command
The browser demo simulates sign-in, saving, uploads and email. If you want those working — a real database, a real inbox, a real publish — the product ships a demo mode of its own, and it is one command.
docker compose -f docker-compose.demo.yml upOpen http://localhost:3000 and sign in with the details printed on the page. Every browser that visits gets its own copy of the site, held in memory and discarded after an hour.
That mode is part of the product rather than a sandbox somebody maintains, which is the only version of this that stays alive. Every hand-maintained demo instance in the research was dead or retired.
What to try
What to try in the first five minutes
Change a headline and publish
The loop the whole product is built around. Edit, see the draft, press publish, look at the public site.
Reorder the blocks on the page
Move the contact form above the work, hide the numbers, watch the preview follow. This is the part that decides whether the tool is for you.
Add a block, and delete one
All twenty-seven, grouped as your own install groups them. Each arrives empty, which is what adding a block actually looks like — including the warning telling you it will render nothing until you fill it in.
Switch theme
Six of them, changing palette, typeface, spacing and radius together. Then change a colour on top and switch again — your change survives.
Try to make it unreadable
Open Appearance and pick a terrible accent. Every text, border and link colour is derived from your background and clamped before it is drawn, so it is harder than you expect — and a publish-time check catches what clamping cannot.
Limits
What is real, and what is not
Worth being precise about, because a demo that overstates itself is worse than no demo.
Real, and imported from the product: every block and the renderer that draws them, the theme token generator, the profession vocabulary that renames your sections, the editor’s forms — which are generated from each block’s own field metadata — and the content warnings, including the one telling you a block will render nothing.
Simulated: signing in, saving, uploading and email. There is no server, so pressing Publish moves one array in your browser to another — and signing out drops your edits rather than ending a session, because there is none.
Absent: three screens that cannot exist without a server, and each says so when you open it — uploading a file, saving a service password, and reporting a bug through GitHub under your own account.