An API for MoQ: provision your own isolated relays
- ID
- 9621
- Status
- summarized
- Published
- 31 Jul 2026, 9:00 PM
- Fetched
- 31 Jul 2026, 10:54 PM
- Provider
- Cloudflare Blog
- Category
- infrastructure
- Original URL
- https://blog.cloudflare.com/moq-relays/
- Source URL
- https://blog.cloudflare.com/rss/
Summary
- Score
- 6.5
- Created
- 31 Jul 2026, 10:55 PM
- Tags
- Audience
- developersvibe_coderssaas_founders
What happened
Cloudflare added a provisioning API for Media over QUIC (MoQ) that lets you create isolated relays with separate credentials for publishers and subscribers, upgrading last year's unauthenticated global test endpoint into something production-usable. Relays provision within seconds across Cloudflare's 330+ city network with no servers to deploy or load balance, support MoQ Transport draft-14 and draft-16, and are free during beta.
Why it matters
If you're building live video, real-time bidding, or low-latency messaging, you can now skip running your own WebRTC or specialized streaming fleet and publish to Cloudflare's relay network via API with proper access control. The free beta makes it worth prototyping now to evaluate latency and cost against your current stack before the protocol standardizes as an RFC.
Discussion angle
Compare MoQ's publish/subscribe relay model against existing WebRTC SFU or HLS/LL-HLS setups for a Malaysian live-streaming or auction use case — what latency and cost differences would actually matter, and what's the risk of building on a draft protocol that hasn't become an RFC yet?