The hype around EmDash CMS has been hard to miss. Cloudflare backing, TypeScript-first, Astro-native, and a positioning that openly takes shots at WordPress. Naturally, I had to test it.
So I spent a week building with EmDash. Real content, real deploys, real comparisons. Here is the honest report.
What I actually liked
The build experience is fast. Local development feels closer to a modern frontend stack than a traditional CMS. Content models are typed, the editor is clean, and the Cloudflare integration means deploys are essentially instant.
For a developer-led team that already lives in TypeScript and Astro, EmDash is a natural fit. Performance out of the box is genuinely impressive, the kind of Core Web Vitals scores you would normally have to engineer toward.
My results after a week of building: under 1.2s LCP on every page I shipped, sub-50KB initial JavaScript, and a content editing experience that felt closer to Notion than to a traditional admin panel. That is not nothing.
What I actually built during the test
To make the test honest I needed something with real content shape, not a single landing page. I built a small documentation site with twelve pages, three content models (Article, Author, Category), two image-heavy long-form posts, and a basic search. That setup forced every part of the system to do work: typed content modelling, relations, asset handling, build performance, and editorial flow.
The build pipeline impressed me. A full rebuild of the twelve-page site took under four seconds locally and roughly fifteen seconds on Cloudflare Pages. Image transforms ran on Cloudflare's edge with sensible defaults, so I shipped 1200 pixel and 800 pixel variants without writing a sharp pipeline myself. Coming from a stack where image handling is its own afternoon of work, that was a quiet relief.
What WordPress muscle memory did not translate
Two things tripped me up coming from WordPress. First, there is no equivalent of the post revisions UI yet. You get version history through git, which is fine for engineers but worthless for a writer who hit publish and wants to see what they wrote yesterday. Second, role-based permissions are early. WordPress lets a non-technical editor publish without seeing the whole admin. EmDash today assumes everyone touching the CMS is comfortable in a developer-shaped tool.
On the same theme: there is no Yoast or Rank Math equivalent. SEO metadata is a content field you define yourself, which is correct architecturally but means the editor sees an empty field rather than guidance. For an agency shipping to clients who rely on those plugin training wheels, that is a real gap.
What it might cost when this leaves beta
Pricing is the question I cannot answer yet. EmDash is currently free during the beta and Cloudflare have not signalled the production pricing model. The reasonable guess is something between Sanity and Contentful: per-seat for editors, usage-based for API and bandwidth. If they price aggressively and bundle with the rest of the Cloudflare stack, that changes the calculus for a lot of agencies.
What I would not do today is sign a client onto EmDash for a five-year content commitment without that pricing clarity. The platform is good. The economics are unknown.
Where it falls short, for now
Plugin ecosystem is the obvious gap. WordPress has roughly 60,000 plugins. EmDash has a small set of starter integrations. If you need a specific membership system, an e-commerce flow with regional tax rules, or a learning management platform, you are building it yourself.
The same applies to themes. EmDash assumes you are shipping a custom design. WordPress lets a non-developer get to good enough in an afternoon.
Migration tooling is also early. There is no first-class importer from WordPress, Sitecore, or Drupal. For agencies handling enterprise moves, that matters.
Why WordPress is still the right answer for most teams
Here is the thing nobody covering EmDash wants to say out loud: WordPress in 2026 is not the WordPress of 2018. Block themes have made performance and maintenance dramatically easier. The site editor is genuinely usable. Hosting infrastructure has caught up.
I run an agency that ships WordPress sites at scale. The pain points that drove people to look for alternatives, slow admin, fragile plugins, security risk, have been quietly fixed in core over the past three releases.
Modern WordPress with a managed host, a tight plugin diet, and Cloudflare in front of it is fast, predictable, and maintainable. The reputation lag is real, but the platform itself has moved on.
WordPress 7 is going to be the moment
The WordPress 7 release is coming. From what has been previewed so far, it is the biggest jump in years: a rebuilt admin with sub-second navigation, native server-side blocks, smaller default JavaScript footprint, and a much improved interactivity API.
For anyone considering EmDash as a hedge against WordPress stagnating, wait. The platform is moving faster than it has in a decade, and 7 is the milestone that makes that obvious to everyone, not just the people watching the GitHub.
My verdict
EmDash CMS is the most impressive new entrant I have tested in years. If you are a developer-led team building a marketing site or documentation hub from scratch, give it a serious look. The performance and developer experience are real.
But it is not replacing WordPress. WordPress has the ecosystem, the talent pool, and now the performance to match. EmDash is a healthy competitor that will push the WordPress core team to keep moving. That is good for everyone.
I am rooting for EmDash. I am still betting on WordPress.
Related reading
→WordPress vs Next.js in 2026: my honest comparison
→Headless WordPress in 2026: the complete practical guide
→Sitecore and Typo3 to WordPress: a migration playbook
→How to choose the best WordPress hosting in 2026
Frequently asked questions
What is EmDash CMS?
EmDash is a Cloudflare-backed, TypeScript-first, Astro-native open-source CMS positioned as a WordPress alternative. It uses sandboxed plugins and an AI-first build approach. As of this test it was early-stage: promising on architecture but not yet a WordPress replacement for most teams.
Is EmDash CMS ready to replace WordPress?
Not yet for most teams. The architecture is genuinely interesting, but a week of testing showed the gaps you expect from a young product: a missing ecosystem, rough edges, and features WordPress users take for granted. It is one to watch, not one to migrate to today.
Who is EmDash CMS for right now?
Developers who want a TypeScript-first, Astro-native CMS and are comfortable on the edge of a young product. Teams that need a deep plugin ecosystem, mature editing, or stability should stay on WordPress for now and revisit EmDash as it matures past beta.
How much will EmDash CMS cost?
It is open-source, but the test flagged that the hosted or production version will likely carry costs once it leaves beta, tied to Cloudflare's platform. Budget for that uncertainty rather than assuming free forever, and treat current pricing as provisional.