An honest comparison of WordPress and EmDash. One is mature, opinionated about almost nothing, and powers most of the web. The other is months old, opinionated about its architecture, and bets that the next decade of the web will look different from the last twenty.
Most CMS comparison articles fail in the same way. They list features in two columns, mark check-marks on both sides, and conclude that “the right platform depends on your needs.” That’s true and useless. The actual decision between WordPress and EmDash isn’t a feature checklist. It’s a question about how much you value a mature ecosystem you can hire into immediately, set against the case for a modern architecture that’s still proving itself in production.
I’m a WordPress consultant. I’ve been shipping on WordPress since 2007. I’ve read the EmDash documentation, tracked the project since Cloudflare launched it, and run the sample install on Workers. I haven’t shipped a production EmDash site, and the platform itself is months old, not years. That’s the honest position from which I’m writing this comparison.
What EmDash actually is
EmDash is a content management system built by Cloudflare and released as an open source project, MIT licensed, with no shared lineage to WordPress code. The platform runs on Cloudflare’s serverless stack — Workers for compute, D1 for the database, R2 for media — and also runs on any Node.js host with SQLite if you’d rather not be dependent on Cloudflare. The codebase lives on GitHub.
What distinguishes EmDash from most CMS options on the market is the architectural rebuild. Plugins run in sandboxed Worker isolates rather than as PHP files with full filesystem access, which is a substantive answer to the WordPress plugin security problem that has spent twenty years as a target. The platform ships with an MCP server so AI agents can read and write content as a first-class operation, not a bolt-on integration. Schemas are typed in TypeScript. The admin interface is built on Astro 6.0. Cloudflare’s framing is that EmDash is a “spiritual successor to WordPress” — same extensibility model, modern security and runtime defaults.
EmDash is free software. There is no licence fee. The cost is whatever you spend on infrastructure (Cloudflare Workers and D1 scale with usage, typically tens of dollars a month for a publisher-sized site) plus whatever it costs to build on the platform. There is no Cloudflare-as-vendor SaaS contract; you self-host on Cloudflare or on your own infrastructure, and Cloudflare is the project’s sponsor and primary maintainer rather than a service provider gatekeeping access.
What WordPress actually is
WordPress is the open source content management system that powers somewhere north of 40 percent of all websites. At the publisher tier the list includes TIME, Wired, TechCrunch, BBC America, The New Yorker (through Condé Nast), and Variety. It also includes The Verge, Polygon, Vox.com, and SB Nation: Vox Media moved its entire portfolio from its own Chorus CMS to WordPress VIP across 2023 and 2024 after deciding the cost of maintaining a proprietary publishing platform wasn’t worth what it returned. At the enterprise publisher level WordPress is usually deployed via WordPress VIP (Automattic‘s managed enterprise offering) or via an enterprise managed host like WP Engine or Pressable.
What distinguishes WordPress is the opposite of what distinguishes EmDash. WordPress is opinionated about almost nothing. The platform gives you a content engine, an extensibility model (plugins, themes, REST and GraphQL APIs), and an editor. Everything else — editorial workflow, content models, page structure, integrations — is something you assemble. That assembly is either a feature or a bug depending on what your team needs.
WordPress costs whatever you decide to spend on hosting and development. The software is free. Hosting ranges from $30 a month shared hosting to $5,000-plus a month enterprise managed plans. Most serious publisher implementations sit in the $1,500 to $3,000 a month managed hosting range plus a one-time build cost.
The frame that actually matters
A useful comparison isn’t “which platform has more features.” Both will eventually have enough features. The useful question is: do you value a mature ecosystem you can hire into and integrate against today, or a modern architecture that bets correctly on the next decade?
EmDash carries the modern architecture. Sandboxed plugins, type-safe schemas, serverless deployment, an MCP server for AI agents, and a surface area small enough to hold in your head. The cost is everything that comes with a platform months old. The plugin ecosystem is dozens of plugins, not sixty thousand. The talent pool is the people who’ve been reading the docs since launch, not a generation of developers. If your problem doesn’t have a published solution yet, you write it, or you wait for someone else to.
WordPress carries the mature ecosystem. Twenty-two years of plugins, themes, conventions, documentation, agencies, training, and people who’ve shipped through every edge case at least once. The cost is everything that comes with twenty-two years of accumulated decisions: backwards-compatibility constraints, PHP, a plugin security model that puts trust in the developer rather than in the runtime, and an editorial workflow that is whatever you’ve stitched together from plugins.
That’s the real fork in the road. The rest is consequences.
When EmDash is the right call
A small number of organisations should pick EmDash over WordPress today. The pattern looks like this:
- You’re already on Cloudflare’s stack. Workers, D1, and R2 are familiar tools your team uses for other reasons. EmDash slots into infrastructure you already operate, which is a real cost saving the comparison articles rarely credit.
- AI agents in your content workflow are a real requirement, not a future maybe. The bundled MCP server isn’t theatre. It’s the right primitive for an editorial team that’s actually planning to let an agent draft, revise, schedule, or summarise content as part of the production loop.
- Plugin security has bitten you, or your audit posture won’t let it. If you’ve been compromised through a WordPress plugin, or you have compliance requirements that make the WordPress plugin model uncomfortable, EmDash’s sandboxed Worker isolates are a substantive architectural answer rather than a hardening layer bolted on top.
- Your team is comfortable being an early adopter. EmDash is months old. Some of the integrations you need will not exist yet. Your developers will write them, or you’ll wait for the community to. You’re paying the early-adopter premium in exchange for the modern-architecture upside.
If three or four of those apply, EmDash is worth the conversation.
When WordPress is the right call
Most organisations should pick WordPress. The pattern is broader, but the strongest indicators are:
- You need extensibility you can’t predict in advance. WordPress has roughly 60,000 plugins and a generation of developers who can write custom ones. EmDash has a small ecosystem growing from zero and a much smaller pool of developers. If the integration you’ll need in eighteen months hasn’t been imagined yet, WordPress is the safer bet for finding (or building) it when the time comes.
- Your hiring strategy assumes you can find people who already know the tool. Every working web developer has touched WordPress. The EmDash talent pool today is the people who’ve been reading the docs since launch. That pool will grow, but it isn’t where you can recruit from in the current quarter.
- You can’t absorb the cost of betting on a platform this young. Cloudflare is a serious sponsor and the codebase is open source, so EmDash isn’t going to quietly disappear. “The project is still alive in 2031” is a different statement, though, from “all the integrations you need exist, the patterns are settled, and the agency market can quote your build in week one.”
- Your cost model assumes managed hosting, not infrastructure assembly. WordPress on WP Engine or Pressable is a managed service you pay a monthly fee for. EmDash on Cloudflare is infrastructure you assemble — cheaper per dollar of compute, but more team time to operate. The maths depends on what your team is already doing.
- You want a tool the team can grow into rather than be shaped by. WordPress’s neutrality is the feature here. You can configure it to match how your team actually works, instead of the other way around.
If three or four of those apply, the conversation should start at WordPress and stay there unless something specific drags it elsewhere.
The wrinkle most comparisons skip
There’s a third option that comparison articles rarely name: WordPress configured well enough to do what most publishers actually need. It exists. Publishers like TIME, TechCrunch, and Variety run WordPress at the scale and complexity of the largest newsrooms. They’ve invested in editorial workflow plugins (Edit Flow, Co-Authors Plus, PublishPress), content modelling (custom post types, Advanced Custom Fields, Block Bindings), and governance (capability customisation, audit logging). The result is a publishing platform as opinionated as you’d want, with the WordPress trade-offs reversed: you own the stack, you maintain it, and the talent pool to do that maintenance is global.
This is the path Vox Media took when it retired Chorus. The Verge, Polygon, Vox.com, and SB Nation now run on WordPress VIP. The publisher with the most credible “we’ll build our own publisher-grade CMS” story in the industry decided to stop maintaining their own platform and move to WordPress. That isn’t a verdict on EmDash, which Cloudflare built later and from different first principles. It is, however, a meaningful data point about the cost of running a publishing-specific CMS at scale, and worth holding in mind when an early-stage CMS pitches you on doing exactly that.
The honest comparison isn’t WordPress against EmDash. It’s three options:
- EmDash, which gives you a modern serverless architecture with strong security defaults, in exchange for the immaturity that comes with any platform months old.
- WordPress out of the box, which is cheap and flexible but won’t feel like a publisher’s tool.
- WordPress configured for a publisher, which costs less than enterprise SaaS, gives you control, and works on the condition that someone who knows what they’re doing does the configuration.
Option 3 is what most of the publishers I work with end up at. It’s also what Vox Media chose for the properties they used to run on their own platform. That’s not me selling. It’s me reporting what tends to happen when the decision gets made with all three options on the table.
How to decide if you’re still unsure
Three questions usually settle it:
- Can you describe your editorial workflow in two sentences? If yes, you can probably implement it in either platform; pick the one whose talent market, hosting profile, and risk appetite fit. If no, neither platform will fix your workflow for you — figure out the workflow first, then pick the platform.
- Are you comfortable being an early adopter? EmDash is months old. Some of what you need will not exist yet. You will be writing it, or paying someone to write it, or waiting for the community to write it. WordPress is twenty-two years old; whatever you need probably exists, probably twice. If your organisation can absorb the early-adopter cost, the modern-architecture upside is real. If it can’t, that’s a decisive answer on its own.
- Who’s going to maintain this in five years? WordPress maintenance has a global talent market. EmDash maintenance is a small but growing community months old. If your organisation depends on being able to swap developers without retraining, WordPress wins by default. If you’re committed to one team for the long haul, the platform choice matters less.
That’s the actual decision framework. Everything else is feature comparison theatre.
Last reviewed May 17, 2026.
Rate and review this content
Be the first to rate this. Submissions are reviewed before they appear.