Bunny CDN Delivers Content Globally. Cache Governance Is Still Central.
by Nick Clark | Published March 28, 2026
Bunny CDN built a global content delivery network that competes with providers many times its size by offering fast edge delivery, real-time image optimization, and edge scripting capabilities at competitive pricing. The network spans edge locations across every continent. But cache governance — when to purge, what to cache, how to route, when to pull from origin — is defined centrally through pull zone configurations and propagated to edge nodes. The edge delivers content. It does not govern what it holds. The structural gap is between content delivery and scope-governed namespace authority.
Bunny CDN's performance-to-cost ratio is impressive. The Bunny Optimizer, edge storage, and stream platform extend beyond basic CDN functionality. The gap described here is about cache and namespace governance, not delivery performance.
Pull zones define governance centrally
A pull zone in Bunny CDN defines the origin, caching rules, edge scripting configuration, and delivery policies for a set of content. Edge nodes serve content according to the pull zone configuration. When configuration changes, the control plane propagates the update to all edge nodes.
Edge nodes do not independently decide what to cache, when to invalidate, or how to route. They execute the policies defined in the pull zone. The governance is central; the execution is distributed.
Purge propagates from center to edge
When content needs to be invalidated, a purge request is sent to Bunny's API. The control plane then propagates the purge to all edge locations holding the content. The edge node cannot independently determine that content is stale. It must be told by the control plane.
This propagation model means there is always a window between the purge request and the last edge node clearing its cache. During that window, some users see stale content. The edge has no mechanism to govern its own cache validity.
What scope-governed indexing provides
In a scope-governed model, each edge region or content group would be a namespace scope with local anchors governing cache policy. Cache invalidation would be a governed mutation validated through scoped consensus among the anchors responsible for that content region. Edge nodes would participate in governance rather than just executing propagated policies.
The namespace would adapt structurally to content delivery patterns: splitting high-demand content regions across additional governance scopes and consolidating low-traffic regions. Cache validity would be locally determined through governed consensus rather than centrally propagated purges.
The remaining gap
Bunny CDN delivers content globally at impressive speed and cost. The remaining gap is in cache governance: whether edge nodes can participate in governing what they hold rather than executing centrally defined policies.
