# The Cloudflare Blog – Brought to you by EmDash

[Cloudflare](https://yomu.fyi/company/cloudflare) · Kody Jackson · Aug 24, 2026

**Type:** Problem & solution

## Summary

Cloudflare migrated its official blog to EmDash, an Astro-focused content management system, acting as internal Customer Zero to evaluate scaling and usability. To prepare for traffic spikes reaching thousands of requests per second, engineers used k6 to execute ramp, breakpoint, and burst load tests. The resulting production architecture runs EmDash on Cloudflare Workers, pairing it with Workers Cache, an object cache backed by Workers KV, and Hyperdrive connected to PlanetScale. This layered caching design serves 99.5 percent of static files and 70 percent of requests from cache, flattening p95 latency under real-world loads reaching 850 requests per second. The migration also introduced a frontend redesign using the Kumo design system and added Model Context Protocol servers for automated agent workflows.

## Context

The Cloudflare Blog faced platform limitations with its existing CMS vendor and needed to handle erratic traffic patterns that routinely spiked from a baseline of 75 requests per second to over 5,000 requests per second, while acting as Customer Zero to validate the pre-1.0 EmDash platform.

## Approach / What changed

Engineers validated EmDash with usability audits and k6 performance testing up to 7,000 requests per second. They deployed the CMS to Cloudflare Workers using Workers Cache, a Workers KV object cache, and Hyperdrive connected to PlanetScale, followed by a phased traffic rollout from 1% to 100% and the integration of Model Context Protocol (MCP) servers for agent workflows.

## Takeaways

- A multi-layer caching architecture combining Workers Cache and a Workers KV object cache served 99.5% of static files and 70% of requests from cache, eliminating p95 latency spikes.
- Load testing with k6 evaluated availability and latency under 7,000 RPS bursts, enforcing strict thresholds of under 0.01% 5xx errors and sub-500ms p95 response times.
- The platform integrated Model Context Protocol (MCP) servers, enabling external agents to query posts and allowing authors to create, edit, and schedule content via agentic tooling.

**Tags:** [Architecture](https://yomu.fyi/topic/architecture), [Caching](https://yomu.fyi/topic/caching), [Migrations](https://yomu.fyi/topic/migration), [Performance](https://yomu.fyi/topic/performance), [Serverless](https://yomu.fyi/topic/serverless)

[Read original post](https://blog.cloudflare.com/cloudflare-blog-uses-emdash)