Cloudflare announced the launch of EmDash 1.0, the stable release of its open-source content management system built on Astro. The system targets production websites, website-building and hosting platforms, and development and editorial teams that want to combine a traditional management interface with tools that software agents can use through an API, CLI, and built-in MCP server.
Cloudflare says the release follows five months of testing real-world use cases, with a focus on data integrity, database migrations, editorial workflows, localization, extension security, performance, and the reliability of management interfaces, APIs, and media management. As examples of its use, Avulux moved a custom website to EmDash, while Cloudflare moved its blog to the system in August to test operation under traffic reaching millions of visits per week, with peaks of 5,000 requests per second from legitimate traffic, in addition to intermittent DDoS attacks.
Extensions with Defined Permissions
EmDash’s model differs from traditional extensions that run within the same process and theoretically have broad access to the database, files, and network. Each EmDash extension runs in an isolated environment with private storage and, by default, cannot access content, media, users, secrets, the file system, or the network.
The platform displays the permissions an extension requests before running it, and the extension receives no additional capabilities unless it declares them and the site administrator approves them. For example, an extension can be granted permission to read media to optimize images without being granted access to user content, or it can be allowed to read specific events and send notifications without access to private networks or other extensions’ storage. These boundaries are enforced by the runtime environment, rather than relying solely on the extension developer’s commitment.
On Cloudflare, extensions run as Dynamic Workers through Worker Loader, while deployment on Node.js uses workerd as a separate process. Both platforms use the same metadata and capability-restricted APIs, with differences in configuration and runtime environment.
A Decentralized Extension Registry
With version 1.0, Cloudflare launched an extension registry that separates the extension itself from the catalog that enables its discovery and installation. The developer maintains the extension package, its release history, and its identity, while EmDash provides a default catalog that other services can index or use to create alternative catalogs with different policies.
The registry is based on the AT Protocol, also used by Bluesky, and package and release records are published within the publisher’s account and signed by the publisher. EmDash verifies the release record, package name, version number, requested-permissions list, and build source when necessary, then confirms that the downloaded package matches the signed record. The default catalog also moderates names, descriptions, links, and images without rewriting or owning the release.
The registry currently supports free extensions, while Cloudflare plans to make paid extensions available in the future. The company has released the registry services, including the aggregator and the classification service that uses Workers AI, as open-source components.
What Changes in Practice?
EmDash combines Astro-based content management, native integration with agent tools, and a more restrictive security model for extensions. This may matter to development teams that want to reduce the risks of installing external code, and to platforms that manage multiple websites and need to grant each extension the minimum possible permissions. However, the release does not eliminate the need to review extensions: isolation limits the scope of access, while the extension’s ability to perform the task for which it was granted permission and the consequences of relying on it remain the site owner’s responsibility.
Cloudflare says that more than 175 people contributed to the project through more than 1,800 changes, and that the community translated EmDash into 25 languages. The company also launched an open-source preview of EmDash Build, an AI-powered website-building tool. Each project receives a Cloudflare Sandbox container, and the MCP agent is used to create the content model and pages, while Artifacts record changes as Git commits before the website is deployed on Workers for Platforms.
A website can be created locally using the command npm create emdash@latest. Open questions remain related to the system’s maturity outside the Cloudflare environment, the breadth of the extension ecosystem, and how the decentralized payments model will be implemented when it launches.