Cloudflare Migrates Major CDN Service cdnjs to Developer Platform
Cloudflare has fully migrated cdnjs, a critical open-source CDN serving billions of daily requests, to its internal Developer Platform, enhancing its infrastructure and development pipeline.
Cloudflare announced that as of June 23, 2026, cdnjs, one of the internet's most heavily utilized open-source content delivery networks, is now exclusively running on Cloudflare’s Developer Platform. This significant migration consolidates the infrastructure for cdnjs—which serves JavaScript and CSS libraries to an estimated 12% of all websites—onto Cloudflare Workers, KV, D1, R2, and other platform services. The move aims to streamline the development process and improve the pipeline for publishing updates to the widely used service.
cdnjs, initially created in 2011 as a free mirror for open-source libraries, has grown to serve an average of 108,000 requests per second, totaling over 9 billion requests daily across more than 330 Cloudflare data centers. Its continued relevance is partly attributed to its consistent URL patterns and immutable versions, making it a reliable dependency for AI models scaffolding web demos, as well as for developers seeking a free, hash-verified source of popular libraries amidst growing concerns about supply-chain attacks.
While cdnjs's serving infrastructure has been on Cloudflare for years, the internal publishing pipeline—responsible for fetching new library versions from sources like npm and GitHub, processing them, and making them available—remained on Google Cloud Platform (GCP). This hybrid architecture, while resilient, presented internal challenges. Shipping new features or fixing issues required coordinating deployments across multiple cloud environments, and observability was fragmented, making debugging a complex, manual process.
The previous publishing pipeline relied on a chain of GCP Functions, a virtual machine for git synchronization, and a GitHub repository as the source of truth. This system suffered from several pain points, including a lack of shared tracing across different cloud services, leading to difficulties in diagnosing partial failures. Furthermore, the split-brain storage between Workers KV and the GitHub repository meant that inconsistencies could persist unnoticed for extended periods.
To address these issues, Cloudflare leveraged its maturing Developer Platform. The migration involved re-architecting the publishing pipeline to run entirely within Cloudflare's ecosystem. This includes utilizing Cloudflare Workers for compute, KV for storage, and potentially other services like Queues for managing asynchronous tasks and D1 for database needs. The goal was to create a unified, observable, and more efficient system for managing cdnjs.
This internal "dogfooding" effort has not only improved cdnjs's operational efficiency but also contributed to the platform's development. By pushing the limits of Cloudflare's Developer Platform with the demands of a high-traffic CDN, the company identified areas for improvement and growth within its own services. The migration represents a significant step in Cloudflare's strategy to offer a comprehensive suite of tools for developers to build and deploy applications at the edge.
The migration ensures that cdnjs can continue to serve the web reliably while allowing for faster iteration and better maintenance. The move to a fully integrated platform simplifies deployment, enhances observability, and positions cdnjs for future growth and feature development, all while maintaining its commitment to being a free and open resource for developers worldwide.