Cloudflare migrates blog to EmDash CMS using Workers infrastructure
Cloudflare has migrated its corporate blog to EmDash, a CMS built for Astro and Cloudflare Workers. The new architecture leverages Workers Cache, Workers KV, and Hyperdrive to improve latency and support agentic AI via the Model Context Protocol.
Key Takeaways
- Architecture utilizes Workers Cache, Workers KV, and Hyperdrive integration with PlanetScale to serve 70% of requests from cache.
- New Model Context Protocol (MCP) servers enable agentic AI to search, list, and edit blog content without additional costs.
- Performance testing via Grafana K6 validated system stability during a 28,000 RPS DDoS attack and high-traffic 'Agents Week' events.
- Deployment strategy used a proxy Worker and service bindings to route traffic gradually from 1% to 100% with zero downtime.
Why It Matters
This migration demonstrates the viability of building high-traffic content platforms entirely on edge computing infrastructure rather than traditional centralized servers. By utilizing Workers Cache and Hyperdrive, Cloudflare has eliminated the typical latency spikes associated with viral content cycles in the streaming and tech ecosystems. The inclusion of Model Context Protocol servers signals a shift toward 'agentic' web design, where infrastructure must serve both human readers and AI agents with equal efficiency. Watch for whether other high-scale media entities adopt similar edge-first CMS architectures to reduce database load and improve global delivery speeds.
Additional Context
Cloudflare has been aggressively expanding its Workers platform beyond simple edge functions into full application infrastructure. In early 2025, Cloudflare announced that Workers AI had surpassed 1 billion daily inference requests, signaling that the platform is handling production workloads at scale well beyond static content delivery. The EmDash CMS migration fits into a broader strategy of positioning Workers as a complete application runtime, competing directly with Vercel's Edge Functions and AWS Lambda@Edge for developer mindshare in content-heavy workloads. PlanetScale, which provides the underlying database layer for EmDash, announced in March 2025 that it had launched Metal, a dedicated bare-metal database service designed for high-throughput applications that need predictable performance without multi-tenant noise, a capability directly relevant to the Hyperdrive connection pooling described in this migration.
The business implications of edge-native CMS architectures extend into the streaming and media vertical, where content platforms face similar traffic-spike challenges. Cloudflare reported in its Q2 2025 earnings that developer platform revenue grew 48% year over year, driven by enterprises migrating workloads from centralized cloud providers to edge infrastructure. Grafana Labs, mentioned as part of the observability stack in this migration, announced in June 2025 that Grafana Cloud had added support for OpenTelemetry-based edge monitoring, giving operators visibility into distributed edge workloads like those running on Workers. This observability layer is critical for media companies evaluating whether to move content management to edge platforms.
On the technical side, the Model Context Protocol integration in EmDash represents an emerging pattern for making web content accessible to AI agents. Anthropic published the Model Context Protocol specification in November 2024, and adoption has accelerated rapidly since. Cloudflare added native MCP server support to Workers in April 2025, allowing any Workers application to expose structured data to AI agents without additional infrastructure. For streaming platforms and media publishers, this pattern suggests that future CMS architectures must serve both human readers and AI crawlers with equal efficiency, a requirement that traditional server-based CMS platforms like WordPress and Contentful were not designed to handle. The combination of Workers Cache for sub-millisecond reads and Hyperdrive for connection pooling creates a reference architecture that other high-traffic publishers may replicate.
Read full article at blog.cloudflare.com
Enjoy our coverage?
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source