A CMS without dashboards. You say what needs to change, and there it is — no configurations, no edit forms, no update button.
Agreements with the machine
The schema is the agreement — and the agent keeps to it.
A site with an identity that's yours — designed by hand, fully bespoke — and that you then manage in plain language: say what needs to change, and there it is. The content lives as readable, structured data; pages roll straight out of it, and the rest follows on its own — speed, findability, installable as an app. Not content management, but data management. From € 6,750 for an interactive site, design and groundwork included.
“Set the opening hours on the contact page to 9 to 5.”
The text is there, the structured data that search engines read matches it, and the change is recorded with an overview of exactly what changed. Undoing it is always an option.
“Write an article about the new coating, in our tone, and add it to the overview.”
Page, data, place in the overview and the findability all handled at once — because the structure is fixed and the tone is on record. You read it afterwards, not beforehand.
“Add a page for the branch in Breda.”
New page, included in the menu, in the breadcrumbs and in the sitemap. No template to pick, no fields to fill in, no forgotten setting that surfaces later.
The structure and the rules are handed over, not withheld. So whoever works on it next understands straight away how it fits together — whether that's a person or an AI. And the creativity does not run through that AI: design, tone and brand are thought up by hand and set down as instructions. The agent works within that — you keep your identity, fully bespoke.
No login, no dashboard, no hunt for the right field. You describe what needs to change the way you'd ask a colleague, and it happens — including the structured data underneath that search engines and AI assistants read.
Every change is recorded with an overview of exactly what changed and when. Undoing it is a single action, even a week later. That's a better way back than most CMSes offer, and you don't have to learn anything for it. That history grows into a timeline: every instruction with user and moment, neatly out of a queue — see the roadmap below.
No database, no login screen, no third-party plugins — the three routes sites actually get hacked through don't exist here. And a visitor is served a ready-made page, as good as static: nothing is assembled at the moment it gets busy. Findability, structured data and load speed sit baked into the way of working instead of in a separate round afterwards.
Existing clients are already switching over — what's still to come is developed against real situations, not on the drawing board.
The structure stands: content in readable, structured data — pages render straight out of it, with no layer in between.
Say what needs to change and there it is — including the data underneath that search engines and AI assistants read.
Every change recorded with an overview of exactly what changed. Undoing it is a single action.
A change can sit ready next to the live site: review it through a preview link, and it only goes live once you approve.
Design, tone and brand thought up by hand and set down as a rule — the agent works within it.
SEO, structured data and load speed sit in the way of working, not in a separate round afterwards.
New articles appear automatically in a feed, and an AI overview lets assistants read the whole site in one go.
Every page is kept ready after the first visit and refreshes itself the moment something changes.
The PWA base is in there: the site installs on phone and desktop, with its own icon and colours.
Every instruction with user and moment in a readable log — the history is a timeline you walk back.
Same structure, another language: the agent translates the content, the pages follow on their own.
Simultaneous instructions handled neatly one by one — no clashing changes.
Queue and user log together make working with more people possible; the permissions model follows the same route.
Try it yourself instead of reading: a demo environment in the examples section above.
The craft as it always was: dreaming up a brand identity, designing a website. A process in itself, by hand, fully bespoke — and it never runs through AI.
Developed by Braaf: from schema to page, with no layer in between. With the structure search engines and AI assistants read directly, caching for speed and PWA support.
Over ten years of building, set down in AI-readable rules the agent works with: how to fill a form in pleasantly, when a page feels too slow, where a visitor drops off.
The handover: how changes flow, how knowledge is recorded, how the site explains itself to whoever works on it. With a guided switch — so the management sits with you, not with a supplier.
Structured data, load speed and the readability AI assistants ask for sit baked into every page — sites that are of this time.
Knock out pages like it's nothing — with animations, fully automatic within the brand. The creative foundation guards the style while you make pace.
Not included: an AI subscription, a domain name and hosting — and that's deliberate. Everything is in your name: you stay the owner, from domain to data, and there's nothing between you and your site. Hosting can go through Braaf if you like — taking the load off if you want it, no obligation.
No. You describe in plain language what needs to change — the way you'd ask a colleague. The structure is fixed, so there's little to get wrong. What you don't get is a screen full of buttons; what you get back is not having to hunt for where something lives.
No — quite the opposite. The design isn't generated: layout, tone and brand identity are made by hand, fully bespoke, and then set down as instructions. The AI works within that. Whatever gets added or changed, it happens in your style — the creativity is the foundation, and it doesn't run through AI.
Only if you want it to. A change can also be staged: it sits ready next to the live site, and through a preview link you see the site as it will be — not a loose mock-up, but the real pages with the new content in them. It only goes live once you approve; rejecting it throws it away. You can forward that link to anyone who needs to look, without them having to log in anywhere.
Every change is recorded with an overview of exactly what changed. Undoing it is a single action, even a week later. That's a better way back than most CMSes offer.
It's possible, but this is built for a single owner. The building blocks for it are in place: every change lands in a readable log — who asked for what, and when — and changes can be staged so the owner reviews and approves them before they go live. That's the split between contributor and owner in its simplest form. What's still coming is the queue that handles simultaneous requests one by one. Until it's there: with several editors working on the same content at once, other tooling is wiser.
No. Stock, orders, payments and multiple editors call for exactly the management layer that's deliberately left out here. For a web shop you're better off with a platform built for that.
From € 6,750 for an interactive site: design, structure, schema and the rules you manage it with afterwards. What it comes to exactly depends on the number of pages, the integrations and how much content still needs writing. Not included: the AI subscription you manage the site with — you arrange that yourself, reckon on a few tens of euros a month. That sounds like a downside, but it also means there's no mandatory contract between you and your site.
WordPress and Drupal are building AI in as fast as they can. But what happens when the AI no longer needs the dashboard? Why the CMS structure is being torn up — and what replaces it.
AIWhat does implementing AI cost in 2026? From an afternoon of policy to a fully set-up way of working — what drives the price and where the money leaks away.
WebsitesWordPress or a bespoke website? An honest comparison — without pushing a platform. Read which choice fits your situation.
