MoQ Alliance Members<br>Akamai<br>AWS<br>Bitmovin<br>Cisco<br>Cloudflare<br>Datum<br>Demuxed<br>Fastly<br>Iroh<br>moq.dev<br>MOQtail<br>Mux<br>Norsk<br>OpenMOQ<br>Qualabs<br>Red5<br>Software Mansion
Get involved
GitHub:<br>github.com/moqalliance
Discord:<br>join the MoQ Alliance Discord
IETF MoQ working group:<br>datatracker.ietf.org/wg/moq
Subscribe to MoQ Alliance updates:<br>Email Subscribe
By subscribing, you agree to receive emails from MoQ Alliance.<br>Unsubscribe anytime.
Media<br>MoQ: Not Another Tech Demo<br>Luke Curley · December 2025 · 23:01<br>Update on the state of MoQ beyond demos, into real applications.
MOQ vs. WebRTC: a Cloudflare panel discussion<br>Renan Dincer, Mike English, Nils Ohlmeier · November 2025 · 1:05:47<br>Cloudflare engineers discuss the trade-offs between MoQ and WebRTC, with use cases for each.
Replacing WebRTC with Media over QUIC<br>Luke Curley · February 2025 · 20:38<br>Why MoQ aims to replace WebRTC, RTMP/SRT, and HLS/DASH using WebTransport and WebCodecs.
Media over QUIC contribution with Rust<br>Mike English · February 2024 · 12:19<br>Practical experience implementing the MoQ protocols in Rust for broadcast-scale ultra-low latency streaming.
Cacheable live under 200ms glass to glass: It is MoQ<br>Jordi Cenzano · February 2024 · 24:50<br>An end-to-end MoQ proof of concept built with WebCodecs, WebTransport, and quic-go showing sub-200ms latency.
Low-Latency Video over QUIC<br>Luke Curley · December 2021 · 15:41<br>Foundational early talk on low-latency video over QUIC by the creator of moq.dev.
FAQ<br>Where is MoQ being developed? Media over QUIC is developed and standardized at the IETF (Internet Engineering Task Force), in the MoQ working group. What is the IETF? The Internet Engineering Task Force is the open standards body responsible for the Internet's core protocols, including TCP, HTTP, TLS, QUIC, and MoQ. It operates through open working groups and rough consensus. What does the MoQ Alliance do? We promote the use cases, diversity, and interoperability of MoQ as an open protocol through education, community programs, and active support of multiple independent implementations. How does MoQ compare to WebRTC? WebRTC is designed for peer-to-peer real-time communication and small group calls, with complex signaling and tight latency. MoQ is designed for one-to-many fan-out at Internet scale, with publish/subscribe semantics on top of QUIC. They solve different problems and can coexist. Is MoQ production ready? MOQT is an active IETF draft and the protocol is still evolving. Early production deployments and interoperability between independent implementations are happening today. The protocol is maturing rapidly. How can I try MoQ today? Several open source implementations are available, including moq.dev. See our developer page for implementations, libraries, and tooling. Who is running MoQ in production? Members of the MoQ Alliance and other organizations in the working group are actively deploying MoQ. Specific deployment details are published by each operator. How do I contribute? Join the IETF MoQ working group mailing list, attend working group meetings, contribute to open source implementations, or email the MoQ Alliance directly.