The Norwegian-led initiative combines distributed edge delivery with content-access controls and an independent control plane, giving broadcasters and digital businesses a foundation for managing how their content is delivered, protected and withdrawn.
WAYSCloud is introducing WAYSCloud CDN, a European content delivery initiative built around customer control, distributed delivery and the operational demands of live and on-demand content.
The product direction extends across video and general HTTP content delivery. Customers are intended to retain their existing origins while using WAYSCloud to manage delivery zones, domains, caching policies and access controls.
The opportunity is substantial. Grand View Research estimates that Europe’s CDN market generated approximately US$6.5 billion in revenue in 2025, with video delivery representing its largest segment. Source: Grand View Research
A delivery architecture with local control
WAYSCloud separates its control plane from the delivery path. Edge nodes use authenticated local state to apply relevant policies, avoiding a central management-system lookup for every video segment.
The implemented technical foundation includes:
Varnish-based edge delivery, with caching and request coalescing tested against real running instances.
Authenticated, versioned policy state, supported by purpose-specific trust management and mechanisms for key overlap, rotation and retirement.
Content-access enforcement and revocation, including controls that apply when protected content is already cached.
Freshness and applied-state checks, tying authorization decisions to the revocation state a delivery node has actually received and applied.
Independent emergency blocking, providing a separate mechanism for withdrawing access alongside cache invalidation.
Failure and recovery verification, using deliberately introduced regressions, restarts and interrupted processes to test detection and cleanup.
These capabilities address a practical requirement for media distribution: delivering cached content must remain consistent with the current authority to deliver it.
Customer origins, programmable operations and accountable usage
The next integration stages connect these foundations into a customer-facing service.
The repository includes contracts and reference implementations for API-driven zone management, revisioned configuration, audit trails and clear separation between requested, observed and applied changes. This supports a product direction in which customers can automate delivery operations and see whether changes have reached the intended nodes.
Origin and shielding work addresses secure upstream retrieval, origin protection and separation of ingest credentials from edge delivery. The wider roadmap covers general HTTP delivery profiles, HLS/DASH workflows and integration with WAYSCloud’s customer identity, usage measurement and billing.
Capacity planned around real delivery demands
The network strategy centres on leased dedicated edge capacity, regional locations and direct peering, with reserved capacity and burst planning shaped by customer requirements.
Large live events are a defining design case. WAYSCloud’s planning includes a 2027 engineering target of 100,000 or more concurrent viewers per event, subject to capacity and operational validation.
This announcement introduces WAYSCloud CDN and its technical foundation. Access to the new service will be available through the My WAYSCloud platform from 1 November. Delivery locations, supported configurations and service commitments will be announced as integration and validation milestones are completed.
WAYSCloud welcomes discussions with broadcasters, content owners and technology partners about their distribution requirements.