By Sagar Shankaran, Founder of CallSphere
MoQ is on draft-17 with a December 2026 IESG target. Here is what that means for AI voice teams already shipping on WebRTC, and when (if ever) to migrate.
Key takeaways
Media over QUIC reached draft-17 in March 2026 with a December 2026 IESG publication target. It is real, it is funded, and Cloudflare's relay is live. It is also still not a finished standard, and it does not replace WebRTC for AI voice today.
Media over QUIC Transport (MOQT, draft-ietf-moq-transport-17) is an IETF effort to move real-time media off RTP/SRTP onto QUIC streams. The data model is publishers-relays-subscribers; tracks are sequences of groups, groups contain objects, relays cache and forward. It is built for very large fan-out (millions of subscribers per track) with sub-second latency.
The selling pitch over WebRTC: one transport for both unicast voice calls and live broadcast, with the same congestion control, the same head-of-line-blocking-free streams, and the same NAT story (QUIC traverses better than SRTP). For AI voice specifically, the appeal is the unified transport story — your inference cluster could publish into the same relay mesh as your live audio, simplifying the data path for retrieval-augmented voice agents that need real-time context.
```mermaid flowchart LR Pub[Publisher / AI agent] -- objects --> Relay1[MoQ relay 1] Relay1 --> Relay2[MoQ relay N] Relay2 --> Sub1[Subscriber A] Relay2 --> Sub2[Subscriber B] ```
MoQ relays cache by group, so a late joiner can be served the last keyframe without round-tripping to the publisher. For broadcast that is a huge win. For one-to-one AI voice it does not matter — there is no fan-out.
The 2026 milestone that actually matters: WebTransport crossed Baseline. Your application layer can now safely speak QUIC across all major browsers without polyfills. Whether you build MoQ on top of that, or just use WebTransport for signalling alongside WebRTC media, is the practical 2026 question.
Hear it before you finish reading
Talk to a live CallSphere AI voice agent in your browser — 60 seconds, no signup.
CallSphere is not migrating production voice from WebRTC to MoQ in 2026. Reasons:
We are tracking MoQ for two specific cases:
Across 37 agents, 90+ tools, and 115+ database tables, the production stack remains WebRTC + Pion + NATS + 6-container pod (CRM, MLS, calendar, SMS, audit, transcript), with SOC 2 + HIPAA controls auditing only the WebRTC paths. Pricing $149/$499/$1499 with the 14-day trial across all six verticals (real estate, healthcare, behavioral health, legal, salon, insurance); affiliates 22% — see /affiliate.
```ts const wt = new WebTransport("https://moq.example.com/relay"); await wt.ready;
const reader = wt.incomingUnidirectionalStreams.getReader(); while (true) { const { value: stream, done } = await reader.read(); if (done) break; // each stream is a MoQ object on a track for await (const chunk of stream as any) { // dispatch chunk to decoder } } ```
Will MoQ replace WebRTC? Not for one-to-one voice. For broadcast it likely will.
Is WebTransport part of MoQ? WebTransport is the browser-side QUIC transport. MoQ is the application protocol. Yes, related, no, not the same.
Does Safari support MoQ? Not yet. WebTransport yes (since 26.0); MoQ application layer no.
Still reading? Stop comparing — try CallSphere live.
CallSphere ships complete AI voice agents per industry — 14 tools for healthcare, 10 agents for real estate, 4 specialists for salons. See how it actually handles a call before you book a demo.
Should I learn MoQ? Yes — for the 2027–2028 horizon. Do not bet production on it in 2026.
Can MoQ carry voice calls? Technically yes; in practice the missing AEC/jitter pieces make it impractical for 1:1.
When will MoQ be RFC? IESG publication targeted December 2026; an RFC could ship by mid-2027.
Should I switch from RTMP to MoQ? For broadcast, yes — within 12–18 months. For voice agents, not in 2026.
Does WebTransport on Safari include datagrams? Yes since 26.0; the datagram path is what makes MoQ feasible there.
Three rules for tracking MoQ without betting on it:
Cloudflare's open-sourced moq-rs and Meta's moq-js are the right reference implementations to read. The ecosystem is small enough that you can fit the whole story in your head; it is also growing fast enough that you should re-check every quarter.
Stay on the proven path with WebRTC: see /demo or start a /trial.
Written by
Sagar Shankaran· Founder, CallSphere
Sagar Shankaran is the founder of CallSphere, where he builds production AI voice and chat agents deployed across healthcare, hospitality, real estate, and home services. He writes about agentic AI, LLM engineering, and shipping voice agents that handle real calls in production.
See how AI voice agents work for your industry. Live demo available -- no signup required.
A founder's guide to texto a voz (text-to-speech in Spanish): LATAM vs Castilian voices, free options, and how CallSphere ships Spanish agents.
A founder's guide to the female voice generator landscape: AI female voices, Japanese voices, robot voices, and how CallSphere ships 57+ voices live.
A founder's guide to the Siri voice generator landscape: how AI voice cloning works, what is legal, and how CallSphere uses 57+ voices in production.
A founder's guide to AI voice assistants for ecommerce: customer service, order lookup, and how CallSphere fits in versus virtual receptionists.
Robot text to speech in 2026: how I pick TTS APIs, when robotic voices help, and how CallSphere ships 57+ language voice agents. Hands-on guide.
The customer support specialist role in 2026 is half human, half AI. Here is what the job looks like, the AI tools that pair with it, and how we ship it.
© 2026 CallSphere LLC. All rights reserved.