EmDash isn\u2019t just another CMS. It\u2019s a deliberate assembly of Cloudflare\u2019s infrastructure products, each chosen to solve a specific problem that WordPress architecture can\u2019t touch. The CMS runs on Workers for compute, D1 for the database, R2 for media storage, and KV for session state. Every one of those products has a billing meter, a performance profile, and a lock-in trade-off. Understanding how they fit together \u2014 and where they break \u2014 is the only way to decide if EmDash is worth your time.<\/p>\n
WordPress runs on a persistent PHP process. EmDash runs on Cloudflare Workers<\/a> \u2014 stateless JavaScript functions that execute at the edge, across 330+ data centers. The difference isn\u2019t just speed; it\u2019s the billing model.<\/p>\n Every page view, admin panel click, and API call on an EmDash site translates to a Worker invocation. The paid Workers plan starts at $5 per month and includes 10 million requests. After that, you pay $0.30 per additional million requests, plus CPU time charges.<\/p>\n Consider a typical blog with 50,000 monthly visits. Each visit triggers one Worker request for the HTML page, plus additional requests for images, CSS, and JavaScript \u2014 roughly 3\u20135 requests per page view depending on caching. That\u2019s 150,000 to 250,000 Worker requests per month, well within the free tier\u2019s 100,000 requests per day limit. But if a post goes viral and hits 500,000 visits in a day, you\u2019re suddenly looking at 1.5 million requests \u2014 still inside the paid plan\u2019s 10 million monthly allowance, but edging closer to the overage threshold.<\/p>\n Workers spin up in milliseconds, not seconds. Cloudflare\u2019s V8 isolates are the engine behind that speed. A Docker container takes 3\u20135 seconds to cold start. A V8 isolate starts in under 5 milliseconds, uses roughly 10 times less memory, and scales down to zero when idle.<\/p>\n For EmDash, this means a plugin that only runs on the \u201cpost_published\u201d hook doesn\u2019t waste resources sitting idle. The isolate spawns, executes the plugin\u2019s code, and terminates \u2014 all within a few hundred milliseconds. In WordPress, that same plugin lives in the same process as every other plugin, consuming memory and CPU even when it\u2019s not doing anything.<\/p>\n The headline security feature \u2014 sandboxed plugins \u2014 only works with Cloudflare\u2019s Dynamic Workers, which require the Workers Paid plan ($5\/month). On the free Workers tier, plugins run \u201cin process\u201d with no isolation. Self-host EmDash on a Node.js server and sandboxing isn\u2019t available at all.<\/p>\n This isn\u2019t a bug. It\u2019s a deliberate architectural dependency. The sandbox is enforced by V8 isolates and Linux namespaces, not by EmDash\u2019s code. Without Cloudflare\u2019s runtime, the security advantage evaporates.<\/p>\n EmDash uses D1, Cloudflare\u2019s serverless SQLite database, as its default storage engine. D1 is built on SQLite, but with a global replication layer that lets you run queries at the edge.<\/p>\n WordPress stores content in MySQL or MariaDB tables. That database runs on a persistent server, consuming resources even when no one is visiting your site. D1, by contrast, is serverless. You pay only for the storage and reads you actually use.<\/p>\n A typical blog with 1,000 posts and 10,000 monthly visits might store 5 MB of content data. D1\u2019s free tier includes 5 GB of storage and 1 million monthly read rows. That\u2019s more than enough for most small sites. The paid plan starts at $0.85 per month for 1 GB of storage and 10 million read rows.<\/p>\n WordPress stores content as HTML in MySQL tables. EmDash stores content as portable text \u2014 a structured JSON format. When you migrate a WordPress site to EmDash, you\u2019re not doing a simple database dump. The migration tool converts HTML to portable text, but it only handles posts, pages, media, and custom fields. It does not migrate plugins, themes, WooCommerce products, or user roles.<\/p>\n For a site with 500 posts and 30 custom blocks, the migration took roughly 15 minutes in tests. But a site with 2,000 products and 50 WooCommerce extensions would require weeks of manual conversion.<\/p>\n D1 is not portable. You cannot export a D1 database and import it into PostgreSQL or MySQL. The closest you get is a SQLite dump, but that loses the global replication and edge query routing. If you ever want to leave Cloudflare, you\u2019re rebuilding your data layer from scratch.<\/p>\n Compare that to WordPress. You can export a MySQL dump, import it into any MySQL-compatible host, and your site keeps running. Same code, same database, same functionality. EmDash\u2019s data is technically portable (SQLite is an open format), but the runtime that makes it perform is not.<\/p>\n Media files \u2014 images, videos, PDFs \u2014 are the biggest cost driver for any CMS. WordPress stores them on the local filesystem or an S3-compatible bucket, but egress fees from AWS or Google Cloud can eat into your budget fast.<\/p>\n R2 is Cloudflare\u2019s object storage, designed to be S3-compatible but with no egress fees. That means you can serve a 2 MB image to 1 million visitors without paying a cent in bandwidth charges.<\/p>\n A typical portfolio site with 500 images (average size 500 KB) would use about 250 MB of storage. R2\u2019s free tier includes 10 GB of storage and 10 million monthly read operations. After that, storage costs $0.015 per GB per month, and operations are $0.01 per million reads.<\/p>\n Every page view on EmDash can trigger multiple R2 operations \u2014 one for the featured image, one for inline images, one for the CSS file. If a page has 10 images, that\u2019s 10 read operations per visitor. At 50,000 monthly visitors, you\u2019re looking at 500,000 reads per month. Still within the free tier, but add a video file and the numbers climb fast.<\/p>\n A managed WordPress host like WP Engine charges for bandwidth above a certain threshold. WP Engine\u2019s Starter plan includes 50 GB of bandwidth. A site with 100,000 monthly visitors and 2 MB per page view would exceed that limit and incur overage charges. R2\u2019s zero-egress model eliminates that entirely.<\/p>\n EmDash uses Cloudflare KV (key-value store) for session management and transient data. KV is designed for high-read, low-write workloads \u2014 perfect for caching user sessions, rate limits, and plugin state.<\/p>\n In WordPress, session data is stored in the EmDash\u2019s passkey authentication uses KV to store the public key for each user. When a user logs in, the Workers runtime checks KV for the key, verifies the signature, and grants access. No database query, no password hash to leak.<\/p>\n KV is eventually consistent. A write to KV can take up to 60 seconds to propagate globally. That\u2019s fine for session data \u2014 a user won\u2019t notice a 10-second delay in their login session being available everywhere. But it\u2019s not suitable for transactional data like payment confirmations or inventory counts.<\/p>\n Every EmDash site on Cloudflare uses at least five separate products: Workers, D1, R2, KV, and Workers AI (for automated moderation and SEO suggestions). Each product has its own billing meter, rate limits, and performance characteristics.<\/p>\n A Reddit user calculated that a sustained DDoS attack of 10,000 requests per second<\/a> could generate 26 billion billable requests in a month \u2014 far beyond the paid plan\u2019s 10 million allowance. At $0.30 per million requests, that\u2019s $7,800 in Workers charges alone. Add D1 read rows, R2 operations, and KV lookups, and the total exceeds $13,000.<\/p>\n Cloudflare does not offer a global spending cap. You can set CPU time limits per request and configure rate limiting, but a distributed bot attack from thousands of different IPs bypasses those protections. The site stays online, the Workers keep firing, and your credit card keeps getting charged.<\/p>\n A managed WordPress host charges a flat $20-$50 per month regardless of traffic spikes. The server might crash under load, but the bill doesn\u2019t change. EmDash inverts that: the site scales perfectly, but the bill is unpredictable.<\/p>\nHow Workers Power Every Request<\/h3>\n
The Cold Start Problem \u2014 Solved by V8 Isolates<\/h3>\n
The Catch: Sandboxed Plugins Require Paid Workers<\/h3>\n
D1: The Database That Scales to Zero<\/h2>\n
What D1 Means for Content Management<\/h3>\n
The Migration Pain Point<\/h3>\n
The Vendor Lock-in Reality<\/h3>\n
R2: Object Storage With Zero Egress Fees<\/h2>\n
How R2 Changes the Economics<\/h3>\n
The Hidden Cost: Operations per Request<\/h3>\n
The Egress Advantage Over WordPress<\/h3>\n
KV: Session State Without a Database Hit<\/h2>\n
How KV Avoids Database Bottlenecks<\/h3>\n
wp_options<\/code>codecodecodecode table or in the database directly. Every page load queries the database to check if the user is logged in. With KV, that lookup happens at the edge \u2014 sub-millisecond latency, no database hit.<\/p>\nThe Consistency Trade-Off<\/h3>\n
The Five-Product Dependency<\/h2>\n
The $13,000 Bill Scenario<\/h3>\n
Contrast With WordPress Flat Pricing<\/h3>\n
AI-Native Architecture: MCP Server and Agent Skills<\/h2>\n