EmDash is the newest serious content management system in years, and it calls itself the spiritual successor to WordPress. We maintain thousands of WordPress sites and now build on EmDash too, so this is not a pitch for either side. It is the comparison we walk clients through when they ask which one to pick.
What each one is
WordPress is a PHP application with a MySQL database. A theme renders the pages, plugins add features, and the admin has been refined for twenty years. It runs a huge share of the web, and almost any feature you want already exists as a plugin.
EmDash is an open-source CMS built on Astro and written in TypeScript. It started at Cloudflare, is MIT-licensed, and reached a stable 1.0 in September 2026. You get a familiar admin with posts, pages, media, menus, widgets, taxonomies, drafts, revisions and scheduling. Underneath, the CMS and the website are one Astro project rather than a theme on top of a database.
The useful mental model: EmDash sits where WordPress sits (the place content is edited), and Astro sits where a WordPress theme sits (how pages render). Our stack guide lays out how they combine.
The comparison
| Factor | WordPress | EmDash | Edge |
|---|---|---|---|
| Editing | Mature block editor, page builders | Familiar admin, rich-text editor, no visual page builder | WordPress |
| Content modeling | Custom fields via plugins such as ACF | Content types and fields defined in the admin, each a real database table | EmDash |
| Plugins | Tens of thousands | A young registry and a handful of first-party plugins | WordPress |
| Plugin security | Plugins run with full access to the site | Registry plugins run sandboxed, with permissions you approve | EmDash |
| Front end | PHP themes | Astro, with TypeScript types generated from your content | EmDash for developers |
| E-commerce | WooCommerce, mature | No equivalent yet | WordPress |
| AI agents | Possible with plugins and the REST API | MCP server built into every site, scoped to user roles | EmDash |
| Hosting | Any PHP host | Cloudflare Workers or any Node.js server | Tie |
| Who can help you | Nearly every agency and freelancer | A small, fast-growing pool | WordPress |
| License | GPL | MIT | Depends on you |
Why the plugin model matters
Security research firm Patchstack found that 96% of the WordPress vulnerabilities it uncovered in 2024 were in plugins. The reason is structural: a WordPress plugin runs inside the same PHP process as everything else, so a flaw in one plugin can reach the whole site.
EmDash’s answer is isolation. A plugin installed from its registry runs in its own sandbox, declares what it needs (read content, send email, call one named host) and gets only that. It cannot see environment variables, the filesystem or other plugins’ data. There is a caveat: the strictest limits apply on Cloudflare, and “native” plugins that need custom admin UI still run without isolation. We go deeper in our guide to the EmDash plugin sandbox.
Choose WordPress if
- You sell online. WooCommerce, memberships, bookings and courses have no EmDash equivalent yet.
- Your site depends on several plugins that would each be a project to rebuild.
- Editors lay pages out visually, every week, in a page builder.
- You want the widest choice of people to hire, now and in five years.
WordPress is not going anywhere, and a well-maintained WordPress site is still the right answer for most small businesses. If that is you, WP Services has a free WP Care tier to keep it fast and patched.
Choose EmDash if
- You are starting a new content site, blog or publication with no plugin baggage.
- A developer, or a developer partner, will own the site and wants one TypeScript codebase.
- You want AI agents to draft, edit and schedule content through MCP, under the same permissions as your team.
- Your WordPress site is mostly posts and pages, and the theme and plugin upkeep has started to outweigh what they give you.
The cost is maturity. EmDash is stable, but its ecosystem is young, and features you take for granted on WordPress may need building. Budget for a developer the way you would budget for WordPress maintenance.
What about Mullenweg’s criticism?
WordPress co-founder Matt Mullenweg praised EmDash’s engineering and its open license, but argued it was built to sell Cloudflare services and that its plugin security only worked on Cloudflare. That was fair of the April preview. By 1.0, EmDash runs on any Node.js server and sandboxes plugins there too, though with looser limits than on Cloudflare. Our view: both projects are open source, both are good at different jobs, and you should pick by the site, not the debate.
A quick way to decide
Ask two questions. Do you sell or rely on plugins? If yes, WordPress. Is the site new, and will a developer own it? If yes, EmDash is worth a serious look. If you are somewhere in between, WordPress with an Astro front end gives you both, and our WordPress vs Astro guide covers that path.
Next step
If EmDash looks right, talk to Seahawk about EmDash: we will scope a build or a migration, say plainly if WordPress is the better call, and look after the site afterwards. Already on WordPress and staying there? Start with free WP Care.