Bee CMS
Bee CMS lets you change your site by writing to ChatGPT or Claude. AI agents work under the same rules as your team, and for quick fixes there is a simple panel.
Built for AI
In WordPress or Webflow, AI comes later, through a plugin or a limited connector. Bee CMS was designed for it: its own MCP server lets ChatGPT, Claude and other assistants read and edit your site under the same rules your team works under.
The assistant works with pages, blocks, menus, SEO fields, translations and media through named tools. It reads the block schema first, so it knows exactly which fields exist before it changes anything.
Access is granted per token, with the same permission levels as a panel account. Editing content and deploying the site are separate permissions.
On a client account every edit goes through a preview first. You open the built page, and only your explicit yes publishes it. A published preview can be undone for 24 hours.
Each call is recorded with the tool, the outcome and the token that made it, so what an assistant did can always be traced.
AI agents at work
Every change follows the same path, whether you asked for a new price or a new form.
Write to your assistant in your own words, or let an agent pick up a task.
Content changes go straight into the blocks. Code changes are made in your site's Git repository.
Code changes pass automated tests, and every change is built into a preview before anyone sees it.
Changes to the site's configuration are always reviewed by our engineer.
The whole site, on a separate address hidden from search engines.
Only your yes puts it live, and a published change can be undone for 24 hours.
For developers
Every site is also a normal Git repository, so a coding agent like Claude Code can change the code itself, not only the content, and its work goes through the same tests and preview. Read what that means if you are not a developer.
The panel
Prefer to click? Every page is built from ready-made blocks with named fields, so a quick fix takes a few clicks and nothing breaks the design. AI assistants build with the same blocks, which is why their changes look like the rest of your site.
Under the hood
Bee CMS is headless: the panel stores your content and serves it through an API, and Astro builds it into plain static pages served from a CDN. Visitors get light pages with almost no JavaScript, and the public site has no database or login.
On Kwalitet, moving from Webflow to Astro raised the mobile PageSpeed score from 24 to 89.
Compared
How a site on Bee CMS compares with the two platforms we migrate people from most often. Where the answer is "partly", the note says why.
| Bee CMS next to the alternatives | Bee CMS | Webflow | WordPress |
|---|---|---|---|
An AI assistant can edit it directly | Bee CMS✓ Its own MCP server, plus repository access for coding agents | Webflow◐ Official MCP covers what Webflow exposes, some tasks still need the Designer open | WordPress◐ Official MCP Adapter plugin, exposes only what plugins register |
You own the code | Bee CMS✓ Plain Astro in a Git repository | Webflow◐ Export gives static HTML for current pages, not CMS data or forms | WordPress✓ Open source, files and database are yours |
No plan-based ceiling on CMS items | Bee CMS✓ | Webflow✕ The plan sets a hard item limit | WordPress✓ No built-in cap |
No per-editor seat fees | Bee CMS✓ | Webflow✕ Workspace seats are billed per person | WordPress✓ |
Languages without extra products | Bee CMS✓ A version of every page per language, with a completeness report | Webflow◐ Localization is a paid add-on, billed per language | WordPress◐ Needs a plugin such as Polylang or WPML |
Light pages on phones | Bee CMS✓ About 10 KB of JavaScript on our Kwalitet migration | Webflow◐ About 1.75 MB of JavaScript on the same site before the move | WordPress◐ Depends on the theme and plugins |
Code, hosting and CMS are separate layers | Bee CMS✓ You can hand each one off on its own | Webflow✕ Site and CMS run as one subscription on Webflow's platform | WordPress✓ Host and CMS are separate |
This comparison reflects public information as of October 2026 and our own measurements. Plans and features change, so check the vendors' pages before you decide.
Pricing
Bee CMS is not sold on its own. It comes with the sites we build or migrate for you, and the panel is included in our CMS hosting plans. Hosting is billed monthly per plan, and the current prices are on our hosting page.
Questions
Yes. Bee CMS has its own MCP server, so ChatGPT, Claude and other assistants can edit it directly, and every site is also a normal Git repository that a coding agent like Claude Code can work in. See how AI editing works.
Yes. An assistant gets only the permissions you give it, and every call it makes is logged. On a client account every change goes through a preview, nothing goes live without your yes, and a published change can be undone for 24 hours.
No. Bee CMS comes with the sites we build and host, and it is not available as a standalone licence. The CMS plans on our hosting page include the panel. The Static plan has no panel, because a static site has nothing to edit.
You own the code: it is a normal Astro project in a Git repository that your own developer can open and extend. Your content can be exported on request as a single JSON file with pages, translations, menus and media records. The image files themselves are stored on our CDN and are not part of that file, so they are handed over separately.
Your site can keep running as plain static files on any host that serves them. To keep editing, you would either move the content to another CMS or stay on a CMS hosting plan with us.
Yes. Every page has a version for each language you switch on, and you edit them side by side in the same panel.
No. Our packages have no per-editor fees and no CMS item limits. Hosting is a monthly fee per plan, listed on our hosting page.
Ready when you are