Cloudflare Launches an API for Provisioning Isolated MoQ Relays
Original title:An API for MoQ: provision your own isolated relays
AI Summary
Cloudflare has introduced a provisioning API for Media over QUIC relays, adding application isolation and access controls to its previously public global MoQ endpoint. Developers can create isolated relays through the API or dashboard and issue separate credentials for publishers and subscribers. Cloudflare says provisioned relays become available across its network within seconds, without customers deploying, sizing, or load-balancing servers. The service currently supports authenticated versions of MoQ Transport draft-14 and draft-16 and is free during the beta period.
Why it's worth reading
MoQ is moving from open network experimentation toward deployable infrastructure, and this API addresses the immediate operational gaps of isolation, authentication, and globally distributed relay provisioning.
Deep Read
1. What happened
Original facts: Cloudflare announced a provisioning API for MoQ relays. Developers can create an isolated relay for an application and issue separate publisher and subscriber credentials. The same capability is available through the Cloudflare dashboard. This extends Cloudflare’s earlier deployment of a public MoQ testing endpoint across its network.
2. Core technology
Original facts: MoQ Transport is an open publish/subscribe protocol being developed at the IETF on top of QUIC. Cloudflare currently supports draft-14 and draft-16 with authentication, application isolation, and role-specific credentials. Publishers send content to a relay, while authorized subscribers retrieve it.
Analysis: Isolated relays and separate credentials add tenant boundaries and access control needed for application deployment. The supplied article excerpt does not describe the underlying isolation mechanism, token format, or credential-rotation model.
3. Key evidence and numbers
Original facts: Cloudflare says newly provisioned relays become available across its network within seconds. Two draft versions are supported: draft-14 and draft-16. The service is completely free during beta, and users do not need to deploy, size, or load-balance relay servers.
Caveat: No latency, throughput, concurrency, availability, or cross-region benchmark is provided in the supplied material. The “within seconds” statement is therefore a vendor claim, not an independently verified performance result.
4. Why it matters
Analysis: Because MoQ remains an IETF draft, adoption depends on operational capabilities as well as protocol design. Packaging authentication, isolation, and globally distributed relays as a managed service could reduce the cost of experimenting with MoQ for live video, interactive media, and other real-time publish/subscribe workloads.
5. Practical impact
Original facts: Teams can create relays through an API or dashboard and issue different credentials to content producers and consumers.
Analysis: This is directly useful for prototypes, cross-region media tests, and teams that do not want to operate relay clusters. Before production use, developers should verify draft-14 or draft-16 client compatibility and evaluate revocation, observability, quotas, and failure handling.
6. Limitations and uncertainty
Original facts: The service is in beta, and free usage is only promised for the beta period. MoQ Transport itself remains a draft rather than a finalized RFC.
Unknowns: The excerpt does not specify post-beta pricing, an SLA, regional restrictions, quotas, data retention, logging, security audits, or protocol migration policy. The supplied publication date is 2026-07-31, a future date that should be verified against the live page before publication.
7. Original sources
- Cloudflare Blog: An API for MoQ: provision your own isolated relays
- Supplied page publication date: 2026-07-31