EmDash Development
EmDash is Cloudflare's TypeScript-native CMS -- sandboxed plugins, edge-first hosting, zero PHP. We are building on it now so you do not have to figure it out alone.
What is EmDash?
EmDash is an open-source CMS launched in April 2026 by Cloudflare. Built on Astro with 100% TypeScript, it runs serverless on Cloudflare Workers and positions itself as a modern, secure alternative to WordPress. The architecture is fundamentally different from every CMS that came before it: sandboxed plugin isolation, edge-first deployment, and zero-PHP.
Think of it as what WordPress would look like if it were built in 2026 -- TypeScript throughout, serverless by default, and every plugin isolated in its own runtime sandbox.
Why EmDash is architecturally significant
WordPress powers 43% of the web. It also accounts for 96% of CMS security vulnerabilities -- almost all of which come from its unrestricted plugin model. Any WordPress plugin can access your database, read your filesystem, and make outbound HTTP requests. That is the attack surface.
EmDash solves this at the architecture level. Every plugin declares its required capabilities upfront. A contact form plugin gets declared access to form submissions and email. Nothing else. A gallery plugin reads image assets. That is it. If a plugin is compromised, the blast radius is bounded by its declared capability set.
The serverless model compounds this: no persistent server processes, no long-lived PHP-FPM workers accumulating state. Every request is stateless and ephemeral.
The Cloudflare advantage
EmDash is not just a CMS -- it is a CMS designed to run on Cloudflare's global network of 300+ data centres. This means:
Edge rendering: Pages render at the Cloudflare node closest to the visitor. London visitor? Rendered in London. Singapore visitor? Singapore. Not from a single-origin server somewhere in Virginia.
Built-in KV storage: Cloudflare Workers KV provides low-latency key-value reads at the edge. EmDash uses this for content caching, session data, and configuration -- without needing a separate Redis layer.
D1 database: Cloudflare's serverless SQLite-compatible database integrates natively. EmDash sites can run with zero external database dependencies.
R2 object storage: Media assets serve from Cloudflare R2 with zero egress fees. No AWS S3 bills scaling with traffic.
Current state (v0.1.0 developer beta)
EmDash is not production-ready for most use cases. Being specific about this is important:
What works today:
- Core content modelling and publishing
- Astro-based frontend rendering
- Plugin system with capability declarations
- Wrangler deployment to Cloudflare Workers
- Basic media management via R2
- TypeScript-native plugin development
What is missing:
- Plugin marketplace (currently empty -- all plugins are hand-built)
- Localisation and multilingual support
- Scheduled publishing
- Granular user roles and permissions
- Official documentation (sparse and incomplete)
- Community ecosystem (forums, third-party plugins, tutorials)
Our assessment: EmDash will reach production readiness for general use cases in late 2026 to mid-2027. Cloudflare has the engineering resources and the financial incentive -- Workers adoption accelerates when EmDash succeeds.
What we build on EmDash today
Developer portfolios and documentation sites
EmDash is production-ready for low-complexity content sites where you control all the content and need zero-maintenance hosting. A developer portfolio or product documentation site has no e-commerce, no membership, no complex workflows. It is a great fit today.
What we deliver: Astro-based EmDash site, custom content schema, R2 media management, deployed globally on Workers with a custom domain. Typical turnaround: 1-2 weeks.
Experimental builds for forward-thinking clients
Some clients want to understand a technology before they need it. We build proof-of-concept EmDash sites that demonstrate the architecture, surface the limitations, and give you a genuine understanding of where the platform is heading.
What we deliver: Working EmDash prototype, written technical assessment, recommendation on whether to adopt now or wait.
Plugin development
EmDash plugins are TypeScript modules. If you need functionality that does not exist yet -- a custom form handler, a content approval workflow, an integration with your CRM -- we write it. The capability model is clean and the TypeScript API is well-designed even in beta.
What we deliver: Scoped TypeScript plugin with capability declarations, unit tests, and documentation.
WordPress to EmDash migration planning
We are not waiting for EmDash to mature to map the migration path. We are doing it now. The key challenges: content schema translation (WordPress post types to EmDash collections), URL preservation (WordPress slug formats differ), plugin replacement (finding or building EmDash equivalents for essential WordPress functionality), and media migration (wp-content/uploads to R2).
What we deliver: Migration feasibility report with full page-type mapping, URL strategy, plugin gap analysis, and phased timeline.
Who is EmDash right for today?
Good fit now:
- Developers comfortable with TypeScript and Astro
- Teams already using Cloudflare Workers for other infrastructure
- Projects where WordPress feels like overkill and Netlify CMS feels too lightweight
- Clients who want to get ahead of a technology shift before it becomes mainstream
Wait until 2027 if you:
- Run e-commerce, membership sites, or complex editorial workflows
- Depend on specific WordPress plugins that have no EmDash equivalent
- Need a team of non-technical editors to manage content without developer involvement
- Are building something mission-critical where you cannot absorb beta-stage instability
EmDash vs the alternatives
| EmDash | WordPress | Contentful | Sanity | |
|---|---|---|---|---|
| Language | TypeScript | PHP | Node.js | Node.js |
| Hosting | Cloudflare Workers | Traditional/managed | Cloud SaaS | Cloud SaaS |
| Plugin security | Sandboxed | Unrestricted | N/A | N/A |
| Open source | Yes (MIT) | Yes (GPL) | No | No |
| Production readiness | Beta | Mature | Mature | Mature |
| Self-hostable | Yes | Yes | No | No |
| Edge rendering | Native | Plugin-dependent | Integration required | Integration required |
Our approach
We are not spectators. We have running EmDash projects, active plugin development, and a clear picture of where the gaps are. When EmDash matures, we will be the agency that already knows the platform from the inside -- not the one reading the documentation for the first time.
If you want to evaluate EmDash seriously, or if you are building something where EmDash is the right call today, we will tell you the truth about what works and what does not.
Common questions
What is EmDash?
EmDash is an open-source CMS launched April 2026 by Cloudflare. Built on Astro with TypeScript, it runs serverless on Cloudflare Workers. Every plugin runs in a sandboxed runtime with declared capabilities -- a fundamental security improvement over WordPress. It is currently at v0.1.0 developer beta.
Is EmDash ready for production?
For simple content sites (portfolios, documentation, blogs) -- yes. For complex sites with e-commerce, membership, or multi-role editorial workflows -- not yet. The plugin marketplace is empty, localisation is missing, and documentation is sparse. We estimate general production readiness in late 2026 to mid-2027.
Should I migrate from WordPress to EmDash now?
Not yet for most sites. EmDash needs time for the plugin ecosystem to mature. We recommend building a migration plan now so you are ready when the platform stabilises. We already offer migration planning as a standalone engagement -- content schema mapping, URL strategy, and plugin gap analysis.
Can you build an EmDash site for me today?
Yes, for the right use case. Simple content sites, developer portfolios, and documentation sites work well on EmDash today. We also do proof-of-concept builds for clients evaluating the platform. Complex sites with e-commerce or membership should use a mature stack now and plan the EmDash migration later.
How does EmDash handle plugin security compared to WordPress?
WordPress plugins have unrestricted access to your database, filesystem, and network -- this is why 96% of WordPress vulnerabilities come from plugins. EmDash plugins declare their required capabilities upfront and run in isolated sandboxes. A contact form plugin cannot read your database. A gallery plugin cannot make outbound HTTP requests. The blast radius of a compromised plugin is bounded.
Do you develop custom EmDash plugins?
Yes. EmDash plugins are TypeScript modules with a clean capability API. If you need functionality that does not exist in the ecosystem yet -- custom integrations, content workflows, form handlers -- we build it. We are already writing plugins for the early ecosystem.
What are the hosting costs for an EmDash site?
EmDash runs on Cloudflare Workers, which has a generous free tier (100,000 requests/day). Most small to medium content sites run for USD 5/month or less. R2 object storage for media is free up to 10GB. There is no egress fee on R2 -- unlike AWS S3. At scale, EmDash hosting costs are materially lower than equivalent WordPress managed hosting.
How does EmDash compare to Astro with a headless CMS?
If you need a modern, production-ready stack today, Astro plus a headless CMS (Sanity, Contentful, or DatoCMS) is the better choice. EmDash eventually replaces that pattern -- it is Astro plus a CMS in one integrated system -- but the headless CMS ecosystem is years more mature. We build both and will recommend whichever fits your timeline and requirements.
Ready to get started?
Free consultation. No commitment. Just an honest conversation about your project.
Let's build
something together.
Whether it's a migration, a new build, or an SEO challenge — the Social Animal team would love to hear from you.