Cloudflare Ships EmDash 1.0, an Open-Source CMS with a Sandboxed, Decentralized Plugin Registry

Not an April Fools' joke after all

When Cloudflare introduced EmDash on April 1 as the 'spiritual successor to WordPress,' plenty of people assumed it was a prank. It was not. As detailed on the Cloudflare Blog by Scott Buscemi, Matt Kane, and Noah Pham, the company has now released EmDash 1.0: a stable, free, and open-source content management system built on the Astro web framework, aimed at powering production websites, agencies, and hosting platforms alike.

What EmDash is

EmDash is a modern CMS where developers build with Astro, editors manage content through the EmDash admin, and AI agents can work through its API, CLI, or a built-in MCP (Model Context Protocol) server. Version 1.0 bundles production-tested editorial, media, localization, migration, and deployment workflows. It is MIT-licensed and, per Cloudflare, has drawn more than 175 contributors across 1,800+ commits, with translations into 25 languages. Cloudflare also migrated its own blog to EmDash in August as a 'Customer Zero' proof point, handling millions of weekly pageviews.

The big idea: sandboxed plugins

EmDash's most significant departure from WordPress is plugin security. In WordPress, plugins run inside the same process as the site with direct access to the database, filesystem, and network, so a simple contact-form plugin could technically read unpublished posts or exfiltrate data, and you just have to trust it will not. EmDash instead runs each plugin in an isolated runtime with only its own private storage, gaining extra abilities (reading media, sending email, calling a specific service) only when the plugin declares them and the admin approves. Cloudflare compares it to installing a mobile app: you see what it wants to do before it runs, and the runtime enforces those limits.

How the sandboxing works

The isolation is not Cloudflare-only. On Cloudflare, each plugin runs as a Dynamic Worker via the Worker Loader; on Node.js, EmDash launches workerd (the open-source Workers runtime) and runs each plugin as an isolated service inside it, using the same manifests and capability-gated APIs. The upshot is that granting a plugin access to media does not also expose users or unpublished content, and letting it contact one service does not open the rest of the network. Those boundaries are enforced by the runtime rather than left to the plugin author's good intentions.

A decentralized plugin registry

EmDash also launched a plugin registry that deliberately avoids being a single gatekeeper. Traditional registries bundle three roles, your publisher identity, the authoritative package record, and the discovery catalog, into one company, so a suspension or shutdown can strand developers. EmDash separates the plugin from the catalog: it is built on AT Protocol (atproto), the decentralized network behind Bluesky, so authors publish with a portable 'Atmosphere' identity and their signed package and release records live in their own account. Cloudflare hosts a default catalog (with content moderation on names, descriptions, and images) but cannot take over or erase the underlying publications, and others can build competing catalogs on the same records.

Verified, not just trustless

Decentralized does not mean unverified. Atproto repositories use signed Merkle Search Trees, so EmDash can independently confirm that a release record traces to a signed commit from the publisher's account, then check the plugin's checksum, name, version, requested access, and build provenance, and confirm the downloaded bundle matches the signed record. The registry supports free plugins now, with paid plugins planned under the same decentralized model.

More than one site: a platform play

Beyond single sites, EmDash targets companies that build website-creation and hosting products. Paired with Cloudflare's Workers for Platforms, each customer site can run as a Worker on Cloudflare's network, with EmDash providing the content layer via admin, API, CLI, or an agent in front of the MCP server. Cloudflare also open-sourced an alpha of 'EmDash Build,' an AI site builder that spins up a full EmDash site (Astro pages, database, media, admin) from a prompt rather than leaving you stuck re-prompting a chatbot for every change. For developers weighing a WordPress alternative, EmDash 1.0 is a notably modern, agent-friendly, security-first option worth a look.

Related on Skillo

See also: What is open source software?, What is a CDN? Content delivery networks explained.

Sources

• EmDash 1.0: the stable CMS with a secure plugin registry (Scott Buscemi, Matt Kane, Noah Pham, The Cloudflare Blog, 28 Sep 2026)

Published date reflects the original event date (2026-09-29). This article is original Skillo editorial written from the sources above; facts were verified in September 2026.