Cloudflare and the Astro team launch EmDash CMS

Cloudflare and the team behind Astro launched EmDash, an open-source full-stack TypeScript CMS, on 1 April 2026.

The headline positioning is as a WordPress alternative that addresses plugin security: plugins run in isolated Worker sandboxes via Dynamic Worker Loaders, each declaring a capability manifest, so a plugin requesting read:content and email:send can do those things and nothing else. Content is stored as Portable Text in SQL — SQLite, libSQL, D1 or Postgres — with media in S3-compatible storage.

Two details make it directly relevant to AEO practice.

Content is server-rendered by default. EmDash uses Astro's islands architecture, shipping no JavaScript unless a component needs it, and serves pre-rendered HTML from the edge. As we have argued repeatedly, client-side-only rendering is among the most common reasons AI crawlers receive an empty shell instead of content. A CMS whose default output is server-rendered HTML removes that failure mode structurally rather than requiring teams to remember to avoid it.

It ships an MCP server. AI tools can query and manage content directly through the Model Context Protocol. That is the same capability CiteCue reserves for its Enterprise tier, and its appearance in an open-source CMS suggests MCP access is on its way to becoming an expected feature rather than a premium one.

Disclosure of the obvious: this site runs on EmDash. We chose it after the launch for the reasons above — every page here is server-rendered, and our llms.txt, structured data and sitemap are generated from CMS content on request rather than hand-maintained, so they cannot fall out of date.

Source: Cloudflare blog · EmDash documentation