offloadcms vs EmDash

Two different answers to replacing WordPress on Cloudflare. EmDash is Cloudflare's own open-source CMS; offloadcms is a single-tenant CMS built to run entirely on Cloudflare's free tier. Here's an honest, sourced comparison.

EmDash launched 2026-04-01 as a "v0.1.0 developer preview," pitched by Cloudflare as "the spiritual successor to WordPress." It's a full-stack TypeScript CMS built as an Astro integration, MIT licensed, developed in the open at github.com/emdash-cms/emdash (11.1k stars, 427+ releases as of 2026-07-10). offloadcms takes a narrower, more constrained approach: one self-contained instance per Cloudflare account, running entirely inside the free tier, built for small sites that need zero-cost hosting and machine-readable output for AI answer engines.

Two differences that matter most

offloadcms runs fully on Cloudflare's free tier. EmDash's flagship plugin sandbox does not. EmDash's headline security feature — running every plugin in its own isolated Dynamic Worker — requires a paid Cloudflare Workers plan. Deploying the stock EmDash template to a free-tier account fails outright with "In order to use Dynamic Workers, you must switch to a paid plan" (error 10195); GitHub issue #149 was closed by the maintainers as "not planned." offloadcms has no plugin system, so there's no sandbox to gate behind a paid Cloudflare plan — self-host it and every feature runs on the free tier.

SEO and generative-search output is built into the render pipeline, not bolted on as a plugin. Every offloadcms entry gets JSON-LD structured data, canonical URLs and Open Graph/Twitter meta, a sitemap, an AI-bot-allowing robots.txt, RSS, and image SEO straight from the core renderer — no plugin to install or configure. EmDash ships no built-in SEO suite; that surface comes from the community jdevalk/emdash-plugin-seo plugin (built by Yoast's founder — a serious, well-regarded plugin, but third-party and optional), and RSS depends on whichever theme is installed rather than being core CMS behavior.

Side by side

Where each one actually stands.

Axis	offloadcms	EmDash
Cost to run everything shipped	Self-host it and the whole CMS runs on Cloudflare's free tier — no paid plan needed to run any feature.	Core CMS runs on the free tier; the plugin sandbox needs a paid Workers plan (issue #149).
Rendering model	Every entry printed to static HTML at publish time — nothing rendered per request on the public site.	Astro SSR/hybrid — public pages rendered per request (or per cache-invalidation) by a Worker.
SEO / generative-search output	JSON-LD, sitemap, AI-bot robots.txt, canonical/OG meta, RSS, image SEO — built into the renderer, no plugin required.	No built-in SEO suite; covered by the community jdevalk/emdash-plugin-seo plugin. RSS is theme-dependent.
Content model	TipTap JSON, rendered to HTML by the renderer at publish/preview time.	Portable Text (structured JSON), edited with a TipTap-based editor, rendered via a PortableText component.
WordPress import	Reads directly from the WordPress database + filesystem — no REST/WXR dependency.	WXR export (via wp-admin or the EmDash Exporter plugin), or a REST-API route for WordPress.com.
Plugin / extension system	None — a fixed, non-extensible feature set per instance.	Sandboxed Dynamic Worker plugins with capability-manifest permissions (paid-plan caveat above).
Compute portability	Cloudflare Workers only — one instance per account.	Workers, portable to any Node.js server; D1/SQLite/Turso/PostgreSQL; R2/S3/local filesystem.
Maturity	New, single-instance product — the one this site describes.	Launched 2026-04-01, MIT licensed, 11.1k stars, 427+ releases; ecosystem still early ("Right Architecture, Empty Ecosystem" — CMSWire).

Where EmDash is ahead

EmDash is Cloudflare's own product, and offloadcms runs on Cloudflare too — this isn't a rivalry with the platform, just an honest look at two different answers to the same problem. EmDash's core bet is a genuinely different, and in several respects more ambitious, response to WordPress's plugin-security problem than simply not having a plugin system at all.

MIT license — more permissive than WordPress's GPL, and possible because, per Cloudflare, "no WordPress code was used to create EmDash."
A real security improvement, paid-plan caveat aside — capability-scoped, sandboxed-Worker plugins (a plugin granted read:content and email:send can do exactly that and nothing else) are a step up from WordPress's unrestricted-PHP-in-process model.
Astro — a well-regarded, modern rendering framework, with Astro 6's Live Content Collections for runtime content updates.
An agent-native interface layer offloadcms doesn't yet have — every EmDash instance ships a remote MCP server, a CLI, and "Agent Skills" documentation, a coherent and currently-unmatched combination for letting a coding agent operate an install without step-by-step guidance. offloadcms's own admin surface today is its Admin API + OpenAPI spec and an Admin SPA — no MCP server, CLI, or agent-skill docs yet; that's a genuine feature gap, not a difference of emphasis.
First-party Cloudflare backing and fast iteration — 427+ releases in roughly three months of a project publicly launched 2026-04-01.

The honest gap, named by both critics and supporters in our research, is ecosystem maturity and the free-tier accessibility of EmDash's own signature feature — not architectural ambition.

See how offloadcms migration works → View pricing