Cloudflare adds isolation and token-based access controls to global MoQ relays
Cloudflare has introduced a provisioning API for its Media over QUIC (MoQ) relays, providing users with the ability to create isolated relay scopes and manage access through token-based authentication. The update adds support for IETF MoQ Transport drafts 14 and 16, allowing for more secure and scalable live video and real-time messaging applications on the company's global network.
Key Takeaways
- Provisioning API allows creation of isolated relay scopes across 330+ cities within seconds without manual server deployment or load balancing.
- Token-based authentication provides granular control, enabling separate credentials for publishers and subscribers to prevent track hijacking.
- Draft-16 support introduces PUBLISH functionality, allowing tracks to be sent to relays before viewer requests, and SUBSCRIBE_NAMESPACE for multi-track requests.
- The MoQ provisioning model is being documented as an IETF Internet-Draft to promote multi-CDN interoperability and common semantic standards.
Why It Matters
This launch transitions MoQ from a testing curiosity to a production-ready alternative for low-latency delivery at scale. By providing isolation and authentication, Cloudflare addresses the security gaps that previously barred MoQ from enterprise use cases like live auctions or betting. The infrastructure effectively collapses the traditional trade-off between the sub-500ms latency of WebRTC and the cost-effective fan-out of HLS/DASH. For the ecosystem, this signals a shift toward pub/sub media delivery architectures that leverage QUIC’s multiplexing to avoid head-of-line blocking. Watch for other major CDNs to adopt similar provisioning APIs as the IETF working group moves toward a formal RFC in 2027.
Additional Context
The standardization of Media over QUIC (MoQ) is accelerating as major infrastructure players align behind the protocol to replace aging low-latency solutions. Per IETF documentation from July 2026, the working group has advanced the core transport spec to draft-19, focusing on refining end-to-end secure objects and mitigating relay-based amplification attacks. Industry consensus is forming around a hybrid workflow where WebRTC remains the standard for two-way conversational contribution, while MoQ handles one-to-many fan-out to reach larger audiences with traditional CDN economics.
Competitive activity in the MoQ space has intensified throughout 2026. Per Fastly and Oracle reports from April 2026, both providers have demonstrated production-level MoQ capabilities, with Oracle integrating MoQ into its Video @ Edge platform for multi-vendor streaming pipelines involving Ateme and Broadpeak. Furthermore, browser support reached a critical milestone in March 2026, when WebTransport achieved 'Baseline' status across Chrome, Edge, and Safari, effectively solving the client-side delivery bottleneck that previously required custom plugins or native applications.
Financial analysts note that the shift toward MoQ could significantly impact Opex for high-concurrency live events. Per Forasoft reporting in April 2026, early production deployments suggest 40–60% savings compared to WebRTC Selective Forwarding Units (SFUs) at the 10,000-concurrent viewer mark. This economic advantage, combined with glass-to-glass latencies of 200–300ms, positions MoQ as the primary successor to Low-Latency HLS (LL-HLS) for interactive broadcast workflows.
Read full article at blog.cloudflare.com
Enjoy our coverage?
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source