Both belong in it. Support time is #3 with a price tag: every edit a client can’t make on their own becomes a ticket you eat.
Exit cost is the number nobody prices until a client leaves. If you can’t hand over content, media and structure in an open format without rewriting the site, you didn’t sell a website. You sold a dependency.
If you run 10+ client sites, "best CMS" is the wrong question. Four numbers decide it.
1. Cost per site at 10, 25, 50 sites. Not at one.
2. Moving parts per client.
3. What a non-technical client can change without emailing you.
4. The compliance you inherit and have to defend to their legal team.
Start with the first one. At list price, as of writing, Storyblok Growth is $99/month for one space. Ten client sites is about $11,880 a year. Neleto Solo is EUR 19/month, EUR 190 on annual billing, so ten sites is EUR 1,900. Contentful Lite is $300/month, extra spaces $850/month each, and past a handful of sites the list price stops being a price at all.
Two caveats. Nobody at 25 sites pays list, and the real number comes out of a sales call. And the headless figures exclude frontend hosting, which you may be paying for anyway if you have a frontend team. (Currencies differ: competitors in USD, Neleto in EUR.)
The second number matters more. A EUR 39/month site is EUR 468 a year. Three hours of unplanned maintenance costs more than the licence. A stack with a CMS, a framework, a build pipeline and three services gives you four things that can page you per client. A complete CMS that renders its own pages gives you one.
Where an agent fits: a law change means a new imprint on 30 sites. With Neleto's built-in MCP server, Claude Code makes the edit project by project and you review the diffs. Each site is a separate connection, it makes no design decisions, and you check site one before the other 29. The typing goes away. The judgement stays with you.
When not to use us: you already ship fast on Webflow or WordPress, your clients need a specific ecommerce stack, or you need custom content types. We don't ship user-defined types yet.
What does one client site cost you per month, all in?
@qianl_cs Works well as long as everyone who edits the site can open a PR. The first time someone in marketing needs a typo fixed on the pricing page at 6pm, an engineer has to drop what they're doing. Is everyone touching the DBOS site an engineer right now?
@wilreynolds Picking the host by which MCP is most complete makes sense, and I don't see many people doing it yet. We build a CMS, and that hour of plugins and permissions before the agent can start is the part we're trying to get rid of. What tipped it to WordPress over Webflow?
@gregoryjhickman Cloudflare or Netlify are both fine for hosting. The blog is the annoying part. Once it's all code, every new post means a Claude Code session and a deploy. Who's going to write the posts, you or someone on your team? I'd decide that before picking a host.
Stop maintaining WordPress. Tell your AI what to build. Neleto has hosting, updates and an MCP server built in, so Claude Code does the setup and nobody patches plugins again. Free plan.
@InhimillinenE Update since you’re testing: every new free site now runs on https://t.co/SCwj8CkNS7, so the “free” is gone. If you already set one up, I can move it over for you. To be upfront, free sites show a small Neleto badge. Solo removes it and adds your own domain.
@InhimillinenE Fair point, thanks for saying it. A neutral address on its own .app domain is on the roadmap, so the “free” will go. Until then you can still test everything, nobody has to see the URL while you try it. Happy to help if you do.
@InhimillinenE Fair, I get it. The address is the one thing the free plan gives up. Everything else stays free for good, no feature limits and no trial that runs out. If the address bugs you, Solo is €19/month and puts the site on your own domain.
@liadyosef Useful map. From the CMS side I keep wondering which of the twelve a normal content site should bother with today. Our MCP is in the core, but ARD and WebMCP are still drafts. If you ran a plain marketing site, what would you add first?
Every CMS opens with the same question: "Pick a template."
That made sense when the alternative was hiring a designer and a developer. A template was a shortcut: someone else had done the design and the code, you paid a small fee, and you got most of a website on day one.
The rest was the price of the shortcut.
Your site looks like thousands of others, because it runs the same theme. Spacing, fonts and section order were decided for a customer who isn't you. The theme ships with options and scripts you'll never use, and your site loads them anyway. Every change fights the structure, and an update can break what you customized.
We watched customers go through this for years. The template was rarely what they wanted. It was what they could afford.
What changed: design stopped being the expensive part. Describe a site to an AI and you get a working design back in minutes, with your colors, tone and sections, as real HTML and CSS.
So the bottleneck moved. The hard part is now getting the design into the CMS, and a template system makes that harder, because it wants your design to fit its structure.
In Neleto the MCP server is part of the core. Claude creates the layouts, pages and content directly in the CMS. You don't paste, zip or run a theme installer. You say "make the hero shorter" and it lands in the same place.
Does that mean every site becomes a mess? Only if you skip the boring parts: reusable components, brand colors and fonts set once, nothing live until you approve it.
If a ready-made design is exactly what you want, use one. It just shouldn't be the first thing a CMS asks you.
What would you build if templates didn't exist?
@WPtips 51 tools with 5 permanent deletes, from one plugin. That's the number people should look at before connecting. Our CMS has deletes over MCP too, so I'm curious: can the adapter switch off single abilities per site, or is it all or nothing?
@bernirov Half agree. Our CMS has MCP in the core, so agents already read and write content for us. But somebody still signs the invoice, and that person reads a landing page. In your api-only world, who's the buyer: the agent or the human behind it?
Your AI can now build your website. Neleto is a CMS with an MCP server in its core: connect Claude Code once, describe the site, and it builds, publishes and checks the pages. EU-hosted. Free plan, no credit card.
@lucperkins Agreed, and it already happens under other names. Once content has a schema and an API it's a data source for whatever reads it, and the reader we see most now is an agent. That's why we put MCP tools in front of our CMS. What use did you have in mind?
@masonwenlaunch Would read it. The part I'd want is what Ridham asked: who edits the site after handover. Framer gives the client an editor, Astro gives them a repo. We built a CMS where the client gets the editor and their AI gets the same thing over MCP. What do your clients ask for?
@natmiletic@thepearsonified Static plus Claude Code covers most client sites. Where it broke for us: the client wants to change an opening hour on a Sunday and nobody wants to run a deploy. That's the one job a CMS still has, and the agent needs a way in too. How do you handle client edits after handover?
@Cliffinkent@bttsmatt "I never have to log in" is the line that matters. We built Neleto around the same idea: the agent gets the CMS as MCP tools, you only open the admin to check its work. How does ChatGPT push to Sanity, their MCP or a custom action? Does anything go live before you read it?
One prompt in Claude Code, one live website. Pages, layouts, components, events and files are all MCP tools in Neleto, so the agent works in the same CMS your editors use. Free to try.
When it's not worth it: no personal data beyond logs, you're US-owned anyway, or nobody asked the question. The middle path is usually right: move fonts, analytics, DNS, email, keep what's load-bearing, document why.
Free test: open your network tab, list every domain your site contacts. How many?
A rack in Frankfurt owned by a US company is still reachable by US law.
"Hosted in the EU" is a location. "Outside US reach" is a question of who controls the provider. Most websites only answer the first. 🧵