EmDash vs WordPress: Honest Comparison (2026)

I run dashtro.com on EmDash. I spent years building WordPress sites before that. This comparison comes from hands-on experience with both platforms, not a spec sheet.

EmDash and WordPress solve the same problem — publishing content on the web — but they approach it from completely different directions. WordPress is a 20-year-old PHP application. EmDash is a TypeScript CMS that runs on Cloudflare's edge network. The differences go deeper than language choice, and the right answer depends on what you're building.

Quick comparison

Architecture: origin server vs edge network

WordPress runs on a single origin server. You rent a VPS or shared hosting, install PHP and MySQL, and every request travels to that one server. Even with caching plugins and CDNs layered on top, the origin server is always there — needing updates, restarts, and monitoring.

EmDash runs on Cloudflare Workers. There is no origin server. Your site runs in 300+ data centers worldwide, serving pages from whichever is closest to the visitor. Content lives in D1 (Cloudflare's distributed SQLite) and media in R2 (object storage). Deployment is git push — Cloudflare builds and deploys automatically.

In practice, this means EmDash sites have no server to crash, no operating system to patch, no MySQL to optimize. The trade-off is that you're locked into Cloudflare's ecosystem. WordPress runs anywhere.

Security: plugins are the real difference

The root cause is architectural. WordPress plugins have full access to your database, filesystem, and server environment. A contact form plugin can read your wp-config.php. A gallery plugin can execute arbitrary SQL.

EmDash plugins run in sandboxed Worker isolates. Each plugin declares exactly what it needs — read content, send email, access storage — and can’t do anything else. There’s no ambient access to the database or filesystem. A malicious plugin literally cannot read data it wasn’t granted access to. This isn’t a security feature bolted on — it’s how the platform works. Read more in the EmDash security model deep-dive .

Performance: edge vs origin

The gap is real. I've watched my EmDash pages load faster than the WordPress admin dashboard loads its own settings page.

Cost: free tier vs hosting bills

WordPress is free software, but running it isn’t. Add premium plugins, security scanning, and backup services, and a typical WordPress site costs $40–100/month to run properly. EmDash on Cloudflare’s free tier costs $0/month for most content sites.

Content editing experience

WordPress's block editor (Gutenberg) is a visual page builder. You drag blocks around, see roughly what the page will look like, and publish. It's intuitive for non-technical users, and the editing experience is mature after years of iteration.

EmDash uses Portable Text — structured JSON blocks for paragraphs, headings, lists, images, and custom block types. The editor is closer to Notion than Gutenberg. You write structured content and your Astro templates control how it renders. It's clean and focused, but less visual than WordPress. If your editors need drag-and-drop page building, EmDash isn't there yet.

The admin panel itself is solid for v0.1 — content editing, media library, taxonomy management, menus, user management, and plugin management. Authentication is passkey-based, which is more secure than passwords but requires a device with passkey support.

Ecosystem: 20 years vs 2 weeks

This is WordPress's overwhelming advantage. 59,000+ plugins. Thousands of themes. Millions of developers. Twenty years of tutorials, Stack Overflow answers, and YouTube videos. Whatever you need to do with WordPress, someone has built a plugin for it.

EmDash has a handful of official starter templates, a plugin system that's architecturally excellent but empty, and a community that can fit in a Discord channel. If you need a specific feature — an ecommerce checkout, a booking system, a membership portal — you're building it yourself or waiting.

I'm not going to spin this as a feature. It's a limitation. But it's also temporary. Every mature platform started here. WordPress in 2003 was a fork of b2/cafelog with no plugins at all.

Developer experience

If you're a developer, this is where EmDash pulls ahead. The entire stack is TypeScript. Templates are Astro components. Styling is Tailwind. Content queries are typed. The development server runs locally with Miniflare simulating D1 and R2 — no remote services needed during development.

EmDash also has an MCP server for AI-native content management. You can manage content through Claude, Cursor, or any MCP-compatible tool. I use it daily for dashtro.com — it's faster than the admin panel for bulk operations.

When to choose each

The bottom line

The question isn't which is better — it's which trade-offs matter for your project. I chose EmDash for dashtro.com because the security model convinced me, the performance is real, and I wanted to build on a modern stack. I wouldn't recommend it for a client who needs WooCommerce or a non-technical team that needs Gutenberg's visual editing.

But for developers building content-focused sites, EmDash is the most interesting thing to happen to CMS architecture in years. Build your first site and see for yourself.