I've been working with WordPress for over twenty years. Themes, plugins, hosting, updates, client projects, the occasional security cleanup. It's been my main tool for most of my career.
WordPress gave me a career. And honestly, for a long time, it was the right tool. You could get a client from zero to a working website in a weekend. The community was generous. The plugin ecosystem meant you didn't have to reinvent the wheel for every project.
But somewhere along the way, it stopped being fun.
The weight of it all
I don't know exactly when it happened. Maybe it was the third time I spent a full day debugging a plugin conflict. Maybe it was when Gutenberg landed and I realized the editor I'd gotten good at was being deprecated under my feet. Maybe it was when I looked at my hosting bills and realized I was paying for servers that mostly sat idle, spinning up PHP just in case someone visited a page that hadn't changed in six months.
WordPress didn't get worse, exactly. It just stayed the same while everything else moved forward. The web got faster, the expectations got higher, and WordPress kept being this PHP monolith that needed constant babysitting.
I tried the alternatives. Moved some projects to static site generators. Built a few things with headless setups. They were fast, sure — but the editing experience was either nonexistent or required developers for every content change. Not exactly what you want to hand off to a client.
Then Emdash showed up
Cloudflare launched Emdash in April 2026, and I'll be honest — my first reaction was skepticism. Another CMS? From a CDN company? The WordPress-killer claims have been made before. Many times.
But I kept reading. And a few things caught my attention.
First: it runs on Cloudflare Workers. That's not a traditional server. There's no PHP process waiting around, no database connection pooling, no server to patch. Your site literally runs at the edge, in the same data centers that serve your static files. The performance implications of that are significant.
Second: it's built on Astro. If you haven't used Astro, it's the framework that finally got the balance right between developer experience and output quality. Fast builds, clean HTML output, islands of interactivity only where you need them.
Third — and this is the one that actually made me set up a local instance — it's agent-native. Not "AI-compatible" in the way that every SaaS product is suddenly "AI-powered" because they stuck an LLM in a sidebar. I mean the entire CMS is designed so that AI agents can work with it directly. Create content types, manage entries, configure plugins, deploy. All through an MCP server that tools like Claude can talk to natively.
Setting it up
I spent a Saturday morning getting emdash.solutions running locally. Node 22 (not 24 — learned that the hard way), npm install, dev server up. The admin UI appeared at localhost:4321/_emdash/admin, and it felt... familiar. Not a clone of WordPress, but clearly built by people who understood why WordPress's admin worked.
Passkey authentication instead of passwords. Portable Text instead of HTML strings in the database. TypeScript instead of PHP. Every choice felt like someone had made a list of WordPress's structural weaknesses and addressed them one by one.
The content modeling is clean. You define collections in a seed file — think of it as your schema — and the CMS generates types, builds the admin UI, and handles migrations automatically. No more ACF field groups configured through a UI that doesn't version control well.
What I'm not sure about yet
Let me be clear: this is a v0.1.0 beta. I'm not putting client sites on this tomorrow.
The plugin ecosystem is empty. Not thin — empty. If you need a form builder, you're building it yourself. If you need e-commerce, you're integrating something external. For a WordPress person used to "there's a plugin for that," this is a shock.
The community is tiny. Reddit threads about Emdash have people asking if it's an April Fools joke. The Discord is small. There's no Stack Overflow tag with ten thousand questions and answers.
And there's a real vendor lock-in question. Cloudflare Workers is the primary deployment target. Yes, you can deploy to Netlify or Vercel, but the deepest integration is with Cloudflare's stack. If you're the kind of person who worries about being dependent on one company's infrastructure, that's worth thinking about.
Why I'm paying attention anyway
Because the fundamentals are right.
The architecture makes sense for 2026. Serverless compute, structured content, edge delivery, agent-native tooling. These aren't buzzwords — they solve real problems I've hit over twenty years of building websites.
The security model is better. Every WordPress developer has a story about a plugin vulnerability that took down a client site. Emdash sandboxes plugins in their own Worker isolates with capability-based permissions. That's not just an improvement — it's a fundamentally different approach.
And the agent-native part isn't a gimmick. I set up the MCP server, pointed Claude at it, and had it create a content type, seed some entries, and configure the site — all without touching the admin UI. For someone who builds sites for clients, the workflow implications are enormous.
What comes next
I'm building this site — emdash.solutions — on Emdash. Not because it's ready for production client work, but because the best way to evaluate a CMS is to actually use it. To hit the edges, file issues, and form opinions based on real experience rather than documentation.
I'll write more as I go. What works well, what's frustrating, what's missing. Honest takes, not marketing. If you're a WordPress person who's been looking at the landscape and feeling that same restlessness I felt — this might be worth your time to follow.
The next post will be a proper comparison: Emdash vs WordPress for agency use. Not a spec sheet — a practical evaluation of what it's actually like to build, deploy, and maintain a site on each platform in 2026.
No comments yet