--- title: "What is a Decentralised CDN?" description: "A decentralised CDN delivers content from a network of independent nodes rather than data centres owned by one company. Learn how it works and why it matters." url: https://edge.network/academy/what-is-a-decentralised-cdn/ --- # What is a Decentralised CDN? [Back to Academy](https://edge.network/academy) Information 7 min read # What is a Decentralised CDN? Content delivery networks have traditionally been built from data centres owned by a single company. A decentralised CDN takes a different approach — and it changes the economics and resilience of content delivery. ## The short answer A decentralised CDN is a content delivery network built on nodes run by independent operators rather than on data centres owned by one company. Content is cached and served from whichever participating node is closest to the user, and the network as a whole — not any single facility — provides the capacity and redundancy. The result is the same job a traditional CDN does — caching content close to users so it loads quickly — delivered by a fundamentally different architecture. It is the CDN expression of the broader [decentralised cloud](https://edge.network/academy/what-is-a-decentralised-cloud) model. ## How centralised CDNs work — and where they fall short A conventional CDN operates a fleet of points of presence (PoPs): racks of servers in data centres, placed in cities the provider has chosen to invest in. When a user requests a file, DNS or Anycast routing directs them to the nearest PoP, which serves the content from cache or fetches it from your origin server. This model works, but its constraints are structural. Coverage only extends to locations that justify the cost of a data centre presence, so users far from major hubs see higher latency. The provider's network is a single administrative domain — a bad configuration push or a core outage can affect every PoP at once, as several high-profile CDN outages have shown. And because the provider must recover the cost of building and running those facilities, bandwidth is metered and charged, usually per gigabyte of egress. ## The decentralised approach A decentralised CDN replaces the company-owned PoP fleet with a network of independent nodes. Anyone with suitable hardware and connectivity can contribute capacity, and the network's software handles the hard parts: verifying node performance, routing each request to the best available node, and moving traffic away from nodes that go offline. On Edge, node operators are rewarded in the network's native token for the capacity they contribute, which gives them a direct economic stake in keeping their nodes fast and reliable. You can read more about how that works in [What is the Edge Token?](https://edge.network/academy/what-is-the-edge-token) Because the network grows wherever operators join rather than where a company builds, coverage extends into regions and smaller cities that centralised CDNs skip. Edge's network currently spans 994 nodes — more edge locations than any traditional CDN operates. ## Centralised vs. decentralised CDN Centralised CDN Decentralised CDN PoPs owned and operated by a single company Nodes run by independent operators worldwide Coverage limited to commercially viable cities Presence wherever operators run nodes One outage can affect the whole network Failures are isolated to individual nodes Capacity requires new data centre buildout Capacity grows as operators join the network Bandwidth priced to recover facility costs Uses spare capacity, enabling zero egress fees ## Why decentralisation matters for content delivery Resilience, coverage, and economics all improve when delivery capacity is distributed rather than concentrated. ### Broader Coverage Independent operators bring nodes to places centralised providers never build, putting content closer to more users. ### No Single Point of Failure If a node goes offline, requests are routed to the next nearest node automatically. There is no central facility to take the network down. ### Better Economics The network runs on spare capacity rather than purpose-built data centres, which is how Edge can serve traffic with zero egress fees. ### Lower Environmental Impact Using hardware that already exists means fewer new data centres and less wasted capacity. ## Edge CDN in practice [Edge CDN](https://edge.network/cdn) is a working decentralised CDN, not a research project. You create a deployment, point it at your origin, and content is served from the nearest node with automatic SSL, instant cache purging, image optimisation, and DDoS protection included. Crucially, the economics follow the architecture. Because the network runs on contributed capacity rather than company-owned data centres, Edge charges [zero egress fees](https://edge.network/academy/zero-egress-explained) — you pay [$0.25 per million requests](https://edge.network/cdn/pricing) beyond a free tier of 500,000 requests a month, and nothing for bandwidth. On a traditional CDN, bandwidth is usually the largest line on the bill. To users, none of this is visible: they simply get content from a nearby node over a standard HTTPS connection. The decentralisation is an implementation detail that shows up as better coverage, better resilience, and a smaller bill. ## Try a decentralised CDN Serve your first site from Edge's network free — 3 deployments and 500k requests a month, with zero egress fees. [Start Free](https://edge.network/account) [Explore Edge CDN](https://edge.network/cdn) ## Related articles [What is a Decentralised Cloud? 8 min](https://edge.network/academy/what-is-a-decentralised-cloud) [CDN vs Edge Computing 7 min](https://edge.network/academy/cdn-vs-edge-computing) [CDN Pricing Comparison 8 min](https://edge.network/academy/cdn-pricing-comparison) Coming soon ### Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. [Learn more about accreditation](https://edge.network/accreditation)