per second<\/a> could rack up $13,000 in a month. Cloudflare offers no global spending cap. Your site keeps running, and your credit card keeps charging.<\/p>\n\nKirby costs $59 once. You host it on any $5 VPS or shared PHP host. Flat rate. No surprises. The cost ceiling is the hosting plan, not the traffic.<\/p>\n\n
AI Readiness: Built-In vs Bolt-On<\/h2>
EmDash ships with a built-in MCP server and agent skills files. You can point Claude or Cursor at your CMS and say “create a new custom content type” \u2014 it works. The AI integration is architectural, not an afterthought.<\/p>\n\n
Kirby has no native MCP server. But its file-based architecture is fundamentally machine-readable. Content lives as structured Markdown with YAML front matter. Any script \u2014 AI-powered or not \u2014 can read, write, and transform it. You don’t need a plugin to give an agent access. You just point it at the content folder.<\/p>\n\n
For a developer comfortable with the terminal, both approaches work. For a non-technical client who wants to edit their site through a browser, Kirby’s panel is simpler and more predictable than EmDash’s passkey-first, serverless admin.<\/p>\n\n
Where the Common Advice Breaks Down<\/h2>
The “EmDash is the WordPress successor” narrative assumes you need what WordPress offers: a plugin ecosystem, multi-user roles, extensibility at scale. That’s true for large publishers and agencies.<\/p>\n\n
But many projects don’t need that. A photographer’s portfolio. A consultant’s landing page. A local restaurant menu. These sites need to load fast, stay secure, and let someone update text without calling you. Kirby does that with zero ongoing cost and zero infrastructure decisions.<\/p>\n\n
EmDash asks you to choose a database provider, configure rate limiting, understand V8 isolate pricing, and monitor Cloudflare dashboards. For a three-page site, that’s not modernization. That’s overhead.<\/p>\n\n
Edge Case: The Client Handoff Problem<\/h2>
You build a site. You hand it to the client. Six months later, they call: the hosting bill was $200 this month, or the import tool broke, or the sandbox plugin stopped working.<\/p>\n\n
With Kirby, you hand them a folder. They upload it to any PHP host. Done. No phone call.<\/p>\n\n
EmDash is not designed for this scenario. It’s designed for developers who control the full stack. That’s fine for in-house projects. It’s a liability for agencies.<\/p>\n\n
FAQ<\/h2>
Can I migrate my WordPress site to Kirby?<\/strong><\/p>\nYes. Kirby includes a migration tool for importing posts, pages, and media from WordPress XML exports. Custom post types require manual mapping, but content structures are straightforward.<\/p>\n\n
Does EmDash work without Cloudflare?<\/strong><\/p>\nIt runs on any Node.js server, but plugin sandboxing is not available outside Cloudflare’s runtime. Self-hosting gives you the CMS without the security model that justifies it.<\/p>\n\n
Which CMS is better for SEO?<\/strong><\/p>\nBoth generate clean HTML and support meta tags, sitemaps, and structured data. EmDash has built-in SEO controls from the start. Kirby relies on a small official plugin, but the output is identical in quality.<\/p>\n\n
Can non-developers use Kirby?<\/strong><\/p>\nYes. The panel is simpler than WordPress. Content editing is Markdown-based with a visual preview. Clients who have used any CMS find it intuitive. EmDash’s passkey authentication and CLI setup create a higher initial barrier.<\/p>\n\n
What the “Successor” Framing Gets Wrong<\/h2>
Calling EmDash a spiritual successor to WordPress implies a linear upgrade. Better security, better performance, better AI integration. For certain use cases, that’s true.<\/p>\n\n
But the framing ignores that WordPress succeeded partly because it ran anywhere. You could hand a client a WordPress site and walk away. EmDash cannot make that promise. Its best features are tied to Cloudflare’s runtime, its billing is unpredictable, and its ecosystem is nonexistent.<\/p>\n\n
Kirby made different tradeoffs. Less extensibility. Less hype. But a site you build today will work tomorrow on any server, with no surprise bills, and no vendor dependency. That’s not a spiritual successor to WordPress. It’s a practical alternative that solves a different problem.<\/p>\n
\n
\n
\n
Can I migrate my WordPress site to Kirby?<\/h3>\n\n\n
Yes. Kirby includes a migration tool for importing posts, pages, and media from WordPress XML exports.<\/p>\n\n<\/div>\n<\/div>\n
\n
Does EmDash work without Cloudflare?<\/h3>\n\n\n
It runs on any Node.js server, but plugin sandboxing is not available outside Cloudflare’s runtime.<\/p>\n\n<\/div>\n<\/div>\n
\n
Which CMS is better for SEO?<\/h3>\n\n\n
Both generate clean HTML and support meta tags, sitemaps, and structured data.<\/p>\n\n<\/div>\n<\/div>\n
\n
Can non-developers use Kirby?<\/h3>\n\n\n
Yes. The panel is simpler than WordPress. Content editing is Markdown-based with a visual preview.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"
Everyone says the same thing: EmDash CMS is the future. Cloudflare’s spiritual successor to WordPress fixes plugin security, runs on serverless infrastructure, and comes AI-native out of the box. Move your content there, they tell you. It’s what WordPress should have been. But that advice misses something fundamental. For a specific class of projects \u2014 […]<\/p>\n","protected":false},"author":7,"featured_media":100419,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/98094.png","fifu_image_alt":"EmDash CMS vs Kirby: Why the \"Modern WordPress Successor\" Advice Falls Short","footnotes":""},"categories":[31],"tags":[],"class_list":["post-98094","post","type-post","status-publish","format-standard","has-post-thumbnail","category-technology"],"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/98094.png","fifu_image_alt":"EmDash CMS vs Kirby: Why the \"Modern WordPress Successor\" Advice Falls Short","_links":{"self":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/98094","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/comments?post=98094"}],"version-history":[{"count":1,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/98094\/revisions"}],"predecessor-version":[{"id":100420,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/98094\/revisions\/100420"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media\/100419"}],"wp:attachment":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media?parent=98094"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/categories?post=98094"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/tags?post=98094"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}