Cloudflare has moved its main blog from WordPress to EmDash, a content management system it developed in-house. The company says the new setup delivers more consistent performance during traffic spikes and tested successfully at up to 7,000 requests per second. Its gradual rollout also offers useful lessons for teams maintaining high-traffic websites.
Key takeaways
Cloudflare’s migration highlights the value of testing performance and planning a safe transition, rather than treating a platform change as a quick fix.
- EmDash runs on Cloudflare Workers, with several caching layers and a PlanetScale database connection.
- A proxy Worker shifted visitors from WordPress to EmDash gradually, with a fallback to the existing site.
- The change improved the blog’s reported response-time consistency, though editors found some early workflow issues.
Why Cloudflare changed platforms
Cloudflare says its blog typically receives around 75 requests per second, with spikes above 5,000. Under that kind of variable load, page speed and reliability matter to readers. The company identified limitations with its existing WordPress setup and chose to test EmDash, its TypeScript-based, open-source CMS, on its own site.
EmDash was introduced as a developer preview in April 2026. Cloudflare’s production configuration runs it on a Worker, using Workers Cache and an object cache built on Workers KV. Hyperdrive connects the application to a PlanetScale database. The results therefore reflect a complete hosting and caching architecture, not simply a CMS swap.
A gradual rollout reduced risk
Instead of switching every visitor at once, Cloudflare used a proxy Worker to direct traffic between the old and new sites. A version cookie kept visitors on the same experience, while the system could send requests back to WordPress if EmDash returned server errors. The team started with 1% of traffic, increased the share as it checked the results and reached full migration in one day.
Cloudflare reports that the new architecture kept p95 response latency more consistent under load than the previous setup. That kind of staged release, with monitoring and a fallback ready, is a useful principle for any major website change—including WordPress updates or infrastructure work.
What WordPress site owners can learn
A migration is not automatically the right answer for every WordPress website. Many performance problems can be addressed by reviewing caching, hosting, plugins and site maintenance before changing platforms. A WordPress maintenance plan can help keep updates, backups and routine performance checks on a schedule, reducing the chance that avoidable issues build up unnoticed.
Cloudflare also added MCP servers to let AI agents interact with its blog and EmDash, including managing content. However, editors reported early difficulties with the editing experience and scheduled posts. The EmDash team is working towards a version 1 release, but no date has been announced. For now, the rollout demonstrates both the potential of a carefully engineered migration and the importance of checking editorial workflows alongside speed and uptime.