- Published
- Updated
- 10 min read

TL;DR: No, you do not need to move your WordPress site because Cloudflare shipped EmDash. EmDash is a real, open source CMS with sandboxed plugins, but that sandbox runs only on Cloudflare. The bigger lesson is about operations: a WordPress site that is updated, backed up and watched is in far better shape than one nobody owns.
Update, October 2026: an earlier version of this note quoted WordPress at 42.5% of the web and leaned on vulnerability counts from a third-party security vendor. We have replaced those with W3Techs' current figure and with what Cloudflare, WordPress.org and CISA publish themselves.
If you run a WordPress site, April 1, 2026 probably landed in your inbox as a headline: Cloudflare previewed EmDash, an open source content management system it called "the spiritual successor to WordPress." The date made people wonder if it was a prank. It was not.
Here is what actually shipped, what the WordPress side said back, and the short list of things I would check on your WordPress site this month, whether or not you ever touch EmDash.
What did Cloudflare actually ship?
Cloudflare's announcement is plain about the goal: "We think of it as the spiritual successor to WordPress." It also says EmDash is "fully open source, MIT licensed, and available on GitHub," that it "is powered by Astro, the web framework for content-driven websites," and that "you can run it on your own hardware or any platform you choose." (Cloudflare blog (opens in a new tab))
At launch it was labeled "v0.1.0 preview." It moved quickly after that. On GitHub, the core emdash package reached version 1.4.0 on October 29 (EmDash releases on GitHub (opens in a new tab)). So the "it's just a preview" argument has a shelf life, and that is worth knowing if you are planning a rebuild for next year.
The feature list, in Cloudflare's words
- Passkeys by default. "EmDash uses passkey-based authentication by default," so there is no admin password to phish or reuse.
- Sandboxed plugins. "Plugins are securely sandboxed and can run in their own isolate, via Dynamic Workers."
- A built-in AI interface. "Every EmDash instance provides its own remote Model Context Protocol (MCP) server," which lets AI agents read and edit content directly.
- Paid access for bots. "EmDash has built-in support for x402," a payment standard that can charge automated clients per request.
- A way in from WordPress. You can import a WordPress site by "exporting a WXR file" from the WordPress admin.
All five quotes come from the same announcement (Cloudflare blog (opens in a new tab)). The MCP server is the part I would watch. Joost de Valk, who created the Yoast SEO plugin, moved his own blog to EmDash early and wrote: "Every architectural decision in EmDash seems to have been made with the same question: 'What if an AI agent needs to do this?'" (Joost.blog (opens in a new tab))
Why Cloudflare's opinion carries weight
Cloudflare is not a random startup with a CMS. W3Techs reports that Cloudflare "is used by 86.1% of all the websites whose reverse proxy service we know," which is 28.3% of all websites (W3Techs (opens in a new tab)). When the company sitting in front of that much of the web ships its own application layer, it is worth reading closely, even if your WordPress site never moves.
How big is WordPress now?
Still enormous. As of October 31, 2026, W3Techs says "WordPress is used by 58.2% of all the websites whose content management system we know," which works out to 39.5% of all websites (W3Techs (opens in a new tab)). Cloudflare's own post uses the rounder "over 40% of the Internet." (Cloudflare blog (opens in a new tab))
Our original headline said 42%. The number has moved since April, and different surveys count differently, so treat any single figure as a snapshot. What does not change: if you own a small business website, there is a good chance it is a WordPress site, and a good chance the people who built it have moved on.
Is EmDash more secure than a WordPress site?
On paper, Cloudflare's design answers a real weakness. Its post says "96% of security issues for WordPress sites originate in plugins," and "There is no isolation: a WordPress plugin has direct access to the WordPress site's database and filesystem." (Cloudflare blog (opens in a new tab)) That 96% is Cloudflare's figure in a post selling its alternative, so read it as their case, not a neutral audit. The architectural point stands on its own, though: one bad plugin on a WordPress site can reach everything.
The catch: the sandbox lives on Cloudflare
The sandbox is the headline feature, and it is tied to one platform. DevClass reported that "When self-hosting, there is currently no support for sandboxed plugins," and that EmDash has "no plugin ecosystem yet, no community." (DevClass (opens in a new tab)) Self-host it and you get the CMS without the isolation that was the reason to switch.
That is a classic vendor lock-in trade. The safety feature is real, and it is also a reason to stay on one provider's runtime. Neither of those facts cancels the other.
What WordPress's co-founder said back
Matt Mullenweg replied the next day on his own blog. "I think EmDash was created to sell more Cloudflare services," he wrote, and then added that this is okay. He pointed out that "The plugin security only works on Cloudflare," and that you can run WordPress on anything: "You can run WordPress on a Raspberry Pi, on your phone, on your desktop." He also called the product "very solid." (Matt Mullenweg, ma.tt (opens in a new tab))
Cloudflare's CEO, Matthew Prince, answered on X: "Think this is a fair critique from @photomatt of EmDash." He followed with "I remain hopeful it'll bring a broader set of developers into the WordPress ecosystem." (Search Engine Journal (opens in a new tab))
That exchange is the honest version of the story. The vendor admits the trade-off. It is betting you will take it anyway.
Should you move your WordPress site to EmDash?
For most small businesses, not yet, and maybe not at all. Here is how I would think about it.
Reasons to stay put
- Your plugins do real work. Cloudflare describes a WordPress plugin as "a PHP script that hooks directly into WordPress," while EmDash is "written entirely in TypeScript" and "no WordPress code was used to create EmDash." (Cloudflare blog (opens in a new tab)) Booking, forms, memberships and e-commerce have to be rebuilt or replaced.
- Your team knows the editor. If staff update your WordPress site every week, retraining the person who posts your specials has a real cost.
- The ecosystem is young. No community yet means fewer people to hire and fewer answers when something breaks.
Reasons to take a look
- You are already planning a rebuild. If your WordPress site is due for a redesign anyway, an Astro-based headless or modern CMS is worth pricing against another WordPress theme.
- Your WordPress site is mostly content. A brochure site with a blog and a contact form needs very little of what WordPress plugins provide.
- You want AI agents to edit content safely. A CMS designed around an MCP server and structured content is easier to automate with guardrails than one where an agent has to click through an admin screen.
If the honest answer is "we are on WordPress because everyone is," that answer got weaker in April. It did not become wrong. A well-run WordPress site is still a perfectly good choice.
What should you check on your WordPress site this month?
The real question was never WordPress versus something else. It was: who is watching the site, and what happens the afternoon a plugin you forgot about gets a security fix? WordPress.org's own hardening guide is direct: "make sure your plugins are always updated," and "if you are not using a specific plugin, delete it from the system." It also says "Older versions of WordPress are not maintained with security updates." (WordPress Developer Resources (opens in a new tab))
CISA's advice for everyone applies here too: "Many software updates are created to fix security risks," and "turn on the automatic updates in the device's or application's security settings." (CISA (opens in a new tab))
Here is the list I would run on any WordPress site this week. It takes about an hour.
- Count your plugins. Open the Plugins screen. Anything inactive, delete. Anything active that nobody can explain, find out what it does or remove it on a staging copy first.
- Turn on auto-updates where it is safe. Since WordPress 5.5, administrators "can manually opt-in for automatic updates theme by theme and plugin by plugin," and by default WordPress "runs auto-updates twice per day." (WordPress.org documentation (opens in a new tab)) Start with the plugins that matter least, then widen.
- Check that updates actually run. WordPress says auto-updates "rely on WordPress Cron tasks," and points you to Tools, then Site Health, to look for errors. A setting that is on but never fires is worse than one that is off, because you stop looking.
- Test a restore. The same WordPress page recommends making sure "you're able to rollback to a previous version of your website in case things go wrong." A backup you have never restored is a hope, not a backup.
- Check who has admin. Remove old staff, old agencies and the nephew who set it up in 2019. Every admin account on a WordPress site is a door.
- Look at your host. The hardening guide calls your hosting environment "a good place to start" on security. Ask whether your WordPress site shares a server with strangers, and what happens to you when one of them is compromised.
If you want an outside read first, I wrote about what a free website check finds for a small business (opens in a new tab), and LTFI has a free website grade (opens in a new tab) that checks security, search, DNS, email, speed and privacy basics without installing anything.
Why does who runs the site matter more than the CMS?
Because almost every bad outcome on a small business WordPress site is an operations failure, not a platform failure. The plugin that never got updated. The backup that was never tested. The admin account for a contractor who left three years ago. EmDash's sandbox would limit the blast radius of some of those. It would not fix any of them.
Shared hosting is the quiet one. If your WordPress site sits on a box with hundreds of others, your security depends partly on theirs. We explain the difference in shared hosting versus managed hosting. We do not use shared hosting for anything we run.
The other quiet one is ownership. Plenty of owners cannot say who holds the login to their own domain or WordPress site. If that is you, your WordPress site has a single point of failure you cannot see. We cover that in who owns the website and the login, and it is worth ten minutes before any platform decision.
What does EmDash tell us about where the web is going?
Two things, and neither depends on EmDash winning.
First, the infrastructure layer is no longer neutral. The company that proxies a large share of the web now has opinions about the application you run behind it, and it shipped code to back them up. Expect more of that from every large platform.
Second, content management is being redesigned for software readers as well as human ones. De Valk called EmDash "agent-native, not agent-compatible." (Joost.blog (opens in a new tab)) WordPress is moving the same direction, which we covered when WordPress gave AI the publish button. Whatever you run, and especially if you run a WordPress site with AI tools connected, decide now who and what is allowed to publish on your behalf.
Frequently asked questions
What is Cloudflare EmDash?
An open source, MIT licensed content management system from Cloudflare, written in TypeScript and built on Astro. Cloudflare announced it on April 1, 2026 and calls it the spiritual successor to WordPress.
Can I run WordPress plugins in EmDash?
Not directly. WordPress plugins are PHP scripts, and EmDash is written in TypeScript with no WordPress code. You can import your content from a WordPress export file, but plugin features have to be rebuilt or replaced.
Do EmDash's sandboxed plugins work if I self-host?
Not at the time of the April coverage. Plugin isolation runs on Cloudflare's Dynamic Workers. Self-hosted, you get the CMS without the sandbox.
Is my WordPress site unsafe?
Not by default. Most WordPress site problems come from outdated or unneeded plugins, old admin accounts and untested backups. Keep things updated, remove what you do not use and test a restore.
How much of the web runs on WordPress?
W3Techs puts it at 39.5% of all websites as of October 31, 2026, and 58.2% of sites whose CMS it can identify. Cloudflare's post says over 40%.
Should I rebuild my site on EmDash?
Only if you are already planning a rebuild and the site is mostly content. If your WordPress site depends on plugins for bookings, memberships or a store, the switch costs more than it saves today.
Where we fit
Kief Studio is in Shrewsbury, and this is the work our managed website operations covers: we take over hosting, domain and security on dedicated machines, keep the site updated, and watch uptime, speed and security so problems get fixed before visitors see them. You never log into a server. Security is included on what we host, and we have kept client relationships going for 13 years and more.
We are not attached to one platform. If your WordPress site is fine with better care, we will say so, and we will run that WordPress site properly. If it has outgrown its theme and its plugins, our custom web application work builds around how the business actually runs.
First conversation is free. No commitment.




