EmDash CMS: 10 Questions Cloudflare Engineers Answered

1. How does EmDash’s plugin sandbox actually work under the hood?

The plugin sandbox isn’t just a permission layer—it’s a full V8 isolate powered by Cloudflare’s dynamic workers. Each plugin runs in its own lightweight context that spins up in about 5 milliseconds and disappears when execution ends. The plugin declares exactly what it needs in a capability manifest: read content, send email, but nothing else. The runtime enforces that boundary at the hardware level using Linux namespaces, seccomp filters, and memory protection keys. A compromised plugin cannot touch the database, file system, or network unless explicitly granted. This is not policy—it’s architectural enforcement. The cold start penalty is essentially zero because V8 isolates reuse an existing Node.js process and create a sandboxed context, not a full container.

2. Why did Cloudflare choose MIT over GPL?

The GPL’s copyleft nature creates compliance overhead for enterprises. Any plugin or theme that integrates deeply with WordPress core must adopt GPL, which forces commercial developers to either open-source their code or avoid the ecosystem entirely. Cloudflare wanted to remove that friction. With MIT, developers can keep plugins closed-source, license them under any terms, and even use AI agents to generate code without worrying about viral licensing. The lead engineer spent weeks with lawyers to ensure EmDash had no derivative relationship with WordPress—no reference to its source code, different language, different architecture. MIT also simplifies the AI agent play: agents can read, modify, and generate plugins without triggering license restrictions.

A compromised plugin cannot touch the database, file system, or network unless explicitly granted.

3. What’s the real cost of running EmDash on Cloudflare?

Serverless billing is unpredictable. Every page view can hit multiple meters: Workers (per request and CPU time), D1 database reads, R2 storage operations, KV lookups, and potentially Workers AI. A single user action might trigger four or five separate billing events. Cloudflare offers no global spending cap—you can wake up to a $13,000 bill from a DDoS attack, as one forum post calculated. The paid plan starts at $5/month for 10 million Workers requests, but after that you pay $0.30 per million plus CPU time. For a small blog with steady traffic, costs stay low. But for any site that could be targeted by bots, the lack of a kill switch is a real risk. The sandbox feature (dynamic workers) requires the paid plan—free tier gives you in-process plugins with no isolation.

4. How does EmDash handle WordPress migrations in practice?

The migration tool imports content only: posts, pages, media, custom post types (via WXR export). It does not migrate plugins, themes, WooCommerce data, forms, SEO configurations, or any custom functionality. Those must be rebuilt from scratch. Content format conversion is a deeper issue: WordPress stores content as HTML, while EmDash uses portable text (structured JSON). That means custom blocks, advanced layouts, and complex content structures require manual re-engineering. The import tool does map Yoast SEO fields to EmDash’s built-in SEO, and you can install a plugin to streamline the process. But for any site with more than basic blog posts, migration is a serious engineering project, not a one-click affair.

5. Why is EmDash considered “AI native”?

Most CMS platforms bolt AI on as a plugin—a grammar checker, a title generator. EmDash builds AI into the architecture. Every instance ships with a built-in MCP (Model Context Protocol) server, so agents like Claude, Cursor, or Copilot can connect directly and manage content, schema, plugins, and deployments. There’s also a CLI and structured agent skills files that tell AI agents exactly how to operate the CMS without custom prompting. The non-obvious part: agents can generate and deploy plugins and themes programmatically. Because plugins run in isolated sandboxes (dynamic workers), an AI can create a new plugin, test it, and deploy it without ever having access to the core database or file system. That’s a fundamentally different security model for agent-generated code.

Stop Creating Custom Post Types in EmDash’s Admin Panel (Here’s Why)

Repeatable AI Characters: Production Pipeline for Consistency

EmDash Playground: What Everyone Gets Wrong About Cloudflare’s CMS

6. What is the significance of dynamic workers beyond plugin security?

Dynamic workers are not just for plugins. They allow any piece of untrusted code to run in a secure, isolated environment with millisecond cold starts. That’s a game-changer for AI agent workflows. For example, an LLM can generate a script to analyze data, create a dynamic worker with that code, pass it the data, and get back results—without the LLM ever seeing the raw data. This pattern separates computation from data access. Cloudflare’s Craig Dennis demonstrated this with a chat agent that generated dashboards from sensitive data without exposing it. The same mechanism could power custom hooks, webhook handlers, or even user-submitted code. Dynamic workers turn the CMS into a secure execution platform, not just a content repository.

7. How does EmDash’s theming differ from WordPress?

WordPress themes rely on functions.php, which has full access to the database and all core functions. That’s a security risk. EmDash themes are built with Astro components, layouts, and CSS. They are strictly frontend—they cannot perform database operations. Themes get read-only access to content through a well-defined API. Developers can use modern tools like Tailwind, TypeScript, and any Astro-compatible UI library. The theme is decoupled from the backend, so a compromised theme cannot steal data or modify settings. Selling themes is also easier: no GPL constraints, so you can license themes under MIT or any proprietary license. Performance is baked in because Astro ships zero JavaScript by default.

8. What are the current limitations that make it unsuitable for production?

Version 0.1.0 with about 89 commits. Zero third-party plugins or themes. No hosting partners outside Cloudflare. Known bugs: passkey authentication fails on some Linux setups, magic link fallback returns 404, multi-tab editing can lose content (no real-time conflict resolution). The admin UI has contrast issues and feels sparse. There is no visual drag-and-drop editor, no page builder, no WooCommerce equivalent. The full security model requires Cloudflare’s paid Workers plan. Self-hosting on Node.js loses the sandbox entirely. As one reviewer put it: “Bad architecture in beta with zero ecosystem doesn’t beat good enough with 60,000 plugins and 20 years of battle testing.” For any business, production use is reckless.

9. How does EmDash’s architecture compare to headless CMS approaches?

EmDash is full-stack, like WordPress: it handles both backend and frontend in one repository. But unlike WordPress, it uses Astro for the frontend, which can be static or server-rendered. That gives you the simplicity of a monolithic deploy with the performance of a modern framework. You are not forced to go headless, but you can use the API to connect a separate frontend if needed. The difference from typical headless CMS (like Contentful or Sanity) is that EmDash owns the frontend layer, so you don’t need a separate deployment for the admin and the site. The tradeoff: you are locked into Astro for theming, and the CMS’s data is structured JSON (portable text), not arbitrary content models.

10. What did WordPress co-founder Matt Mullenweg actually say about EmDash?

Mullenweg published a detailed review. He pushed back on the “spiritual successor” branding, calling it a vehicle to sell Cloudflare services. He questioned the open-source-but-vendor-locked dynamic. But he also wrote: “The product is very solid. There’s some excellent engineering.” He specifically praised the agent skills approach as “a brilliant strategy” and said WordPress needs to do the same as soon as possible. That’s the non-obvious take: even the creator of WordPress acknowledged that EmDash’s AI-native architecture is a genuine innovation worth copying. He didn’t dismiss the project; he recognized the threat and the opportunity. The review is a signal that the CMS landscape is shifting, even if EmDash itself is far from ready.