Can Cloudflare’s EmDash CMS threaten WordPress in market share?
The short answer is almost zero. It took me all of 5 minutes clicking around the demo and reading Cloudflare’s public announcements to understand this.
I’m sorry to anybody who thought Cloudflare made a “better WordPress”. They didn’t. They simply copied its (familiar) backend UI and gave credit (*cough* name-drop! *cough*) to WordPress’ success over the years.
So if EmDash isn’t a WordPress-killer, what is it?
EmDash – the new Cloudflare CMS
Launched April 1, 2026 (not as an April’s fools joke)
Yeaup, many thought Cloudflare’s beginning-April 2026 announcement was a joke but it wasn’t. They had seriously created a new CMS called EmDash.
- Introducing EmDash — the spiritual successor to WordPress that solves plugin security – Cloudflare (blog)
Having WordPress mentioned in the title would be the most exciting and controversial part about it.
- Is a new player coming to the WordPress/CMS market?
- Can it solve common WordPress problems?
- Can it bring new features WordPress doesn’t have?
Took me just 20min to find out…
My review of EmDash
EmDash backend looks a lot like WordPress.
Similar greyish/blue color scheme, labels (pages, posts, categories, plugins, etc). Almost zero learning curve, it looks and behaves very much like WordPress.
Very smooth, responsive load on backend. Things load super fast, like razor quick 5ms.
EmDash doesn’t have all of WordPress’ features.
EmDash doesn’t have the large 3rd-party directories for themes and plugins. I only played with the demo and didn’t see options for these anywhere. Of course, it’s not hard to imagine how they would work and to assume they would also have similar smooth WP-familiar settings UI.
EmDash also doesn’t have the giant user community of noobies to help other noobies. It’s mainly a strictly-dev app for devs to work with. Only devs can code and configure it. Or if you’re a client, you can only manage content changes. But it’s not a fun tool for DIY power-clients, and you’ll feel handicapped in terms of explore-ability.
EmDash’s main advertised strengths/difference from WordPress are its “enterprise mentality” (in plugin security & performance architecture).
1st argument – WordPress has a massive plugin security problem. Plugins have too much power over the site, with full unconstrained rights to the database and filesystem. This not only leaves potential security vulnerabilities in millions of sites, but also bottlenecks the plugin-approval process by the official WordPress repo team (said to have a queue of 800 plugins).
- EmDash’s approach to this problem is making plugins request granular access for every function it wants to do, and then manually approve or deny. It’s similar to 3rd-party authentication between different apps. The plugin can’t do anything without your knowledge. This (theoretically) puts the power of security in your hands, and weakens the temptation in malicious developers.
2nd argument – WordPress has performance issues due using old-school style (PHP stack) hosting architecture that requires having your own server. Which is never the right fit, you often have too much (expensive) or too little server in most periods…and still never scales well with sudden unexpected bursts of traffic.
- EmDash’s approach to this problem is using modern serverless architecture. The kind of enterprise stack that scales up and down, and you pay only for your server use (e.g. $0.000005 per cpu/mem/storage used per sec).
The 1st argument, I fully stand with and can agree. WordPress needs a better way of dealing with security. If WP manages this one day, its moat widens even more and WP becomes that much more future proof.
The 2nd argument, blehhhh. Not relatable for 99.99% of WP use cases. The only WP sites with actually scaling issues are the ones taking millions of hits and have thousands of dollars to pay for bigger servers and dev-ops staff to manage more advanced cloud-hosting technical matters.
The average WP site with performance issues are just small-timers with code-bloated sites. Scaling more processors is not the right answer for them. Having variable server costs calculated by the per-second usage billing model is also not for them. Using overly technical container-hosting architecture is also not for them.
Final thoughts on EmDash
EmDash is zero threat or replacement for WordPress (whatsoever).
- EmDash doesn’t have the wide range of 3rd-party themes, with many options and creative/fun features.
- EmDash doesn’t have the wide range of 3rd-party plugins, with unless features and capabilities.
- EmDash doesn’t have the big user community, to ask for help or hangout with. Nonexistent user-base to hire devs or find work for. Hahaha, I joke and call it a “true DIY” (because you have nobody to help you).
- EmDash is not cheaper. It’s a better enterprise-grade tool for enterprise-grade devs. It will not help end-users or non-devs to make custom sites cheaper or easier.
EmDash is like every WordPress-competitor…they do some things (arguably) better, overly-complicate other things, and ultimately can’t touch WordPress’ most powerful and unique strengths.
Don’t be fooled by the migration tool either. EmDash only imports pages and posts, not WooCommerce products, membership courses, or whatever else custom post type you have. I also doubt it carries over all your customized Gutenberg blocks content, layouts, and functions. EmDash only looks like WordPress, it’s not a comparable replacement and will not easily migrate from WordPress.
EmDash is an enterprise-grade CMS that only looks like WordPress. Its underlying code, hosting architecture, and way in which it works is nothing alike. Only a small number of enterprise use-cases can appreciate its strengths.
What’s the best way to start a site on EmDash?
- Play with the free demo
- Deploy EmDash CMS to a Cloudflare worker
- Deploy EmDash CMS (github) anywhere you want (self-hosted container)
- Deploy using 3rd-party host: Tailway (container), Dashem.io (managed)
So who are the only real competitors to WordPress?
- The ones with actual user-base and big market of themes, customizations, and 3rd-party add-ons. Shopify, Squarespace, Wix, Weebly, Joomla, Drupal. That sorta thing. They are the closest to WordPress in usability, approach, and DIY-ness.
- EmDash has a lonnnnng way to go before entering that list.
Leave a Reply