WordPress hosting is simple: pay $20 a month, get a server, hope it doesn’t crash. EmDash flips that model completely. Every page view, every admin click, every API call is a Cloudflare Worker invocation. You pay only for what you use. That sounds terrifying if you’ve ever seen a surprise cloud bill. But the numbers tell a different story \u2014 one where EmDash is cheaper for nearly everyone.<\/p>\n
Managed WordPress hosting starts around $25 a month. WP Engine’s cheapest plan is $20 for the first year, then jumps to $28. Over three years, that’s over $800. And that’s<\/a> before you add premium plugins. Yoast SEO costs $99 a year. A caching plugin? $50. A forms plugin? $60. By the time you have a functional site, you’re past $100 a month.<\/p>\n EmDash replaces all of that. SEO is built in. Forms are built in. Caching is the architecture. The only recurring cost is Cloudflare infrastructure.<\/p>\n Cloudflare’s Workers Paid plan starts at $5 a month<\/strong>. That includes 10 million requests<\/strong> \u2014 enough for a small to medium blog. After that, you pay $0.30 per additional million requests<\/strong>, plus CPU time charges. D1 database reads are billed per row. R2 storage charges per operation, but egress is free.<\/p>\n For a typical blog with 10,000 visitors a month, each visitor might trigger 10\u201315 requests (page loads, media, API calls). That’s 100,000\u2013150,000 total requests. You’d use about 1.5% of your included 10 million. Your bill stays at $5.<\/p>\n Even at 100,000 monthly visitors, you’d use roughly 3% of the included requests. The $5 plan covers most small publishers.<\/p>\n Let’s model a real site. A portfolio or marketing site with 50 pages, 20 images, and a contact form. Monthly traffic: 5,000 visits. Each visit loads the page (1 request), loads images (1\u20133 requests), and maybe submits a form (1 request). Total monthly requests: around 25,000. That’s 0.25% of the 10 million included. Your bill: $5.<\/p>\n Compare that to managed WordPress hosting: $25 a month, plus $10 for a security plugin, plus a domain. That’s $420 a year. EmDash: $60 a year.<\/p>\n Now scale up. 500,000 monthly visitors. You’d burn through the 10 million requests in about two weeks. Your overage: maybe 15 million additional requests. At $0.30 per million, that’s $4.50 extra. Total monthly bill: $9.50. Still less than the cheapest WordPress host.<\/p>\n Critics point to the worst-case scenario: a DDoS attack that drives millions of requests and racks up a $13,000 bill. One forum post calculated that 10,000 bots hitting your site at 1 request per second<\/a> each would generate 26 billion requests in a month. That’s a real risk<\/a>.<\/p>\n But here’s the flaw in that argument: Cloudflare is a CDN and security company. Every EmDash site sits behind Cloudflare’s network. You can configure WAF rules, rate limiting, and bot management \u2014 all included on the free plan. A DDoS attack that large would be mitigated at the edge before it ever hits your Workers. The $13,000 scenario only happens if you deliberately disable all protections and have no spending cap. And yes, Cloudflare doesn’t offer a global spending cap \u2014 but they do offer CPU time limits per request, rate limiting per IP, and automatic bot detection. A properly configured site is safe.<\/p>\n The real counterargument isn’t about attacks. It’s about the lack of a kill switch. If you accidentally write a bad loop that triggers infinite Workers, you could run up a bill. That’s a legitimate concern for developers. But it’s a solvable one: set CPU time limits, use Cloudflare’s observability dashboards, and monitor your usage. WordPress hosts don’t protect you from bad code either \u2014 they just crash your site instead of billing you.<\/p>\n For small publishers, bloggers, and portfolio sites, EmDash is a no-brainer. $5 a month for a full CMS with built-in SEO, forms, and image optimization beats $25 a month for WordPress with paid plugins.<\/p>\n For agencies building client sites, the economics are even better. Deploy 10 client sites on EmDash for $50 a month total. That same portfolio on managed WordPress hosting would cost $250 a month.<\/p>\n The catch: EmDash is v0.1.0. No plugin ecosystem, no theme marketplace, no visual page builder. You need TypeScript and Astro knowledge. The pricing is cheap, but the developer time is not. For a business that needs WooCommerce or Elementor, EmDash is not ready.<\/p>\n Serverless pricing is great for consistent traffic. But what about a viral post that brings 1 million visitors in a day? WordPress hosting would throttle or crash your site. EmDash scales \u2014 but you’d pay for those 1 million visitors. At $0.30 per million requests, a massive spike costs pennies. The real cost is D1 database reads and R2 operations, which are also negligible at that scale. The architecture that makes EmDash secure \u2014 sandboxed plugins, V8 isolates \u2014 also makes it cheap. No cold starts, no over-provisioned servers.<\/p>\n The future of CMS economics is pay-as-you-go. EmDash is the first serious attempt to apply that model to a full-stack CMS. For anyone who can trade a weekend of learning Astro for a lifetime of $5 hosting bills, it’s a trade worth making.<\/p>\n","protected":false},"excerpt":{"rendered":" WordPress hosting is simple: pay $20 a month, get a server, hope it doesn’t crash. EmDash flips that model completely. Every page view, every admin click, every API call is a Cloudflare Worker invocation. You pay only for what you use. That sounds terrifying if you’ve ever seen a surprise cloud bill. But the numbers […]<\/p>\n","protected":false},"author":7,"featured_media":99235,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/98017.png","fifu_image_alt":"The Economics of EmDash: How Serverless Pricing Works for a CMS","footnotes":""},"categories":[31],"tags":[],"class_list":["post-98017","post","type-post","status-publish","format-standard","has-post-thumbnail","category-technology"],"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/98017.png","fifu_image_alt":"The Economics of EmDash: How Serverless Pricing Works for a CMS","_links":{"self":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/98017","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/comments?post=98017"}],"version-history":[{"count":1,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/98017\/revisions"}],"predecessor-version":[{"id":99236,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/98017\/revisions\/99236"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media\/99235"}],"wp:attachment":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media?parent=98017"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/categories?post=98017"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/tags?post=98017"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}EmDash Pricing Breakdown<\/h2>\n
The Real Cost: A Worked Example<\/h2>\n
The Counterargument: Unpredictable Bills<\/h2>\n
Who Should Use EmDash Today<\/h2>\n
The Nuance: What Happens When Traffic Spikes<\/h2>\n