Is EmDash Ready for a Business Website? What 1.0 Changed

The short answer

For most business websites, yes, since version 1.0 shipped on September 28, 2026. A site for a service business, a portfolio or a blog can run on EmDash today, and ours does. A site that sells products online should wait, and a few others need checking first.

If you've read that EmDash is an early beta, that was accurate in the spring. Here's what changed, and what still hasn't.

What the April coverage described

Cloudflare launched EmDash on April 1, 2026 as a "v0.1.0 preview" and called it an early developer beta. Many of the articles that still come up when you search for EmDash were written that month. They describe software to try out, and at the time that was fair.

Before 1.0, any minor release was allowed to break a site. We ran EmDash sites through that stretch, and every update started with reading the release notes for what had been removed and checking our code against the list.

What 1.0 changed

Cloudflare says it spent the five months between the preview and 1.0 on data safety, database migrations, editorial workflows, translation support, plugin security and performance. For a business owner, four results stand out:

• A stability promise. The 1.0 release notes say breaking changes now ship only in a new major version, so an update within 1.x is meant to install without changes to the site built on it.
• A plugin registry. Each plugin release is signed by its publisher and checked against that signature before it installs.
• A heavy production site. Cloudflare moved its own blog to EmDash in August and says it handles spikes of up to 5,000 requests a second.
• A choice of hosting. EmDash runs on Cloudflare or on a Node.js server, and plugins stay sandboxed on both.

Three updates since, on our own sites

A promise in release notes is worth whatever the next few releases do with it. EmDash has shipped three minor versions since 1.0: 1.1 on October 1, 1.2 on October 6 and 1.3 on October 15. We installed each one on every EmDash site we run, after comparing every page on a copy of the site before and after.

None of the three listed a breaking change, and none needed a change to our sites' code. Pages rendered the same afterwards, apart from small markup changes the release notes had described in advance.

The 1.2 release fixed a security bug in the editor toolbar, and it was on our sites the next day. Testing and installing each release like that is most of the upkeep an EmDash site asks for.

The jump from the beta to 1.0 was harder. Most of our sites needed no code change, but one client build, still in staging, did. 1.0 changed how links between pieces of content are stored. That site looked identical after the upgrade, but edits to those links would have been ignored until its code was updated. We caught it before anyone was editing the site.

What editors will notice

Versions 1.2 and 1.3 changed the admin as well. Editing a page now looks more like the page itself, with a toolbar that stays in view as you scroll, and posts can carry video. Revision history became readable too: it lists what changed in plain words and puts a Restore button beneath it.

What still isn't ready

• Online stores. EmDash has nothing to match WooCommerce. Cloudflare's announcement mentions a store plugin being built by another company, Urumi, and we'll look at it when it ships. Stores we build stay on WordPress for now.
• Paid plugins. The registry carries free plugins only, with paid ones planned. If your site depends on a premium WordPress plugin, there's nothing to buy in its place yet. The feature has to be built into the site, or it waits.
• A tested catalogue. The registry arrived with 1.0, and CMSWire's launch coverage called it "new and untested at scale." Expect far fewer ready-made plugins than WordPress has.
• The AI site builder. EmDash Build, Cloudflare's tool for generating sites with AI, launched as an alpha. It's separate from the CMS, and a site doesn't need it.
• Distance from Cloudflare. Search Engine Journal points out that many 1.0 features, from performance options to deployment, depend on Cloudflare's infrastructure. EmDash runs on other Node.js hosting, but some of those features stay behind.

Is your site ready for EmDash?

The software is ready for production. Whether your site belongs on it comes down to what the site has to do:

• A service business site, a portfolio or a blog: yes. Pages, posts, forms, SEO fields, redirects and scheduled posts are all available.
• A site that takes payment for products: not yet. Keep it on WordPress.
• Memberships or online courses: ask first. Some can be rebuilt into the site and some can't yet.
• A WordPress site built on custom fields: yes, with extra work on the move. EmDash's standard WordPress import leaves custom field values behind, so on our own move we scripted them across.

For the longer side-by-side, read what running EmDash and WordPress together taught us. To see what a build includes, look at the EmDash websites built for businesses we offer, or tell us what your site does and we'll say which platform it belongs on.

Frequently asked questions

When did EmDash reach version 1.0?

On September 28, 2026. The first public preview came out on April 1 of the same year.

Will EmDash updates break my site?

Within version 1.x they aren't supposed to. Since 1.0, breaking changes are held for a new major version. We still test every update against a copy of each site before it goes live.

Do I need a developer to use EmDash?

To build the site, yes. To change your own words and images afterwards, no: you log in to the admin, or click Edit on the live page while signed in.

Can I move my WordPress site to EmDash now?

If it doesn't sell products, usually yes. Your addresses carry over or redirect, and our WordPress to EmDash migration is free on any monthly plan.