Compare

How MOQOM compares, from each vendor's own pages.

Competitor figures are what each vendor's own documentation says, accessed 6 Oct 2026. Where a vendor does not document something, we say so rather than guess.

Latency by resolution

From 4K broadcast to co-host tiles

Glass to glass is the time from light hitting the sender's camera to the frame being on the receiver's screen: capture, encode, network, decode and display.

Median glass-to-glass latency by resolution
ResolutionTypical useMedian glass-to-glassStatus
4K (2160p30)Solo host, broadcastNot yet measured4K rung in the Swift SDK camera ladder (opt-in)
1080p30Host / spotlightNot yet measuredSupported (top rung of default camera ladder)
720p30Two-person call56–57 ms (p95 70 ms)*Measured: two iPhone 15 Pros, home Wi-Fi, relay in Los Angeles, both directions at once, 90 s, every frame delivered
540p60, 600 kbpsCo-host tiles69 ms*Measured, same relay
360p30Co-host tiles in shared callsNot yet measuredSupported (600 kbps rung)
Shared video calls (360p–540p per tile)Group calls, co-host gridsNot yet measuredClosest references: 540p60 at 69 ms; 720p30 with the layout changing every 8 s at 61 ms

* Built to scale: a Rust media plane and a Go control plane, each scaling out horizontally. Measured in lab: 6,000 viewers on one 4-vCPU relay, every frame delivered. Full data at moqom.cloud/benchmarks/load-tests.md.

Why MOQOM

What you get today

One protocol for calls and broadcast

Built on the IETF's Media over QUIC Transport (speaking drafts 22 and 19 of draft-ietf-moq-transport): the stream that carries a two-person call also reaches an audience of thousands, without moving to a second product.

Conversational latency, measured end to end

56–57 ms median glass-to-glass at 720p30 (p95 70 ms), camera to screen on two iPhone 15 Pros.*

Broadcast scale on modest hardware

6,000 viewers on one 4-vCPU relay with zero loss (5.46 Gbit/s), the largest size tested.*

Encryption that costs almost nothing

Per-frame end-to-end encryption (SFrame, AES-256-GCM) at 54 µs per 1080p keyframe,* with post-quantum key agreement and signatures (ML-KEM, ML-DSA). TLS 1.3 on every connection, always.

Tokens bound to the device

A join token copied off one device does not work on another.

Your relays or ours

Self-host relays and pay only the platform fee.

Prepaid, 15% under Agora

85% of Agora's list price at every tier and every volume band, always at least 1¢ under, enforced in code.

Open-source SDKs

Go and Rust backend SDKs and a Swift client shell are open source; the media cores ship as signed binaries.

* Built to scale: a Rust media plane and a Go control plane, each scaling out horizontally. Measured in lab: 6,000 viewers on one 4-vCPU relay, every frame delivered. Full data at moqom.cloud/benchmarks/load-tests.md.

Where we are honest about gaps

  • Fewer platforms today. MOQOM launches on iOS and macOS only. Android and Desktop are in progress. The OBS plugin is scoped.
  • No independent audit yet.
  • Lab numbers. Every number above is from the lab, including the 6,000-viewer load test; full data at moqom.cloud/benchmarks/load-tests.md.
  • The protocol is still a draft. Media over QUIC Transport is an IETF Internet-Draft, not yet an RFC. MOQOM speaks draft-22 and draft-19.
  • Post-quantum end-to-end encryption is required in every room, which is why only Apple platforms are supported today.
Latency and scope

Documented latency, calls and broadcast

No latency figure below was measured by us on the same rig as MOQOM's, so read them as published claims, not a head-to-head test.

ProviderDocumented latencyCalls and broadcast
MOQOM56–57 ms median glass-to-glass, 720p30 (measured in lab)*One stream and one protocol for both
Agora"<200 ms global latency" (homepage). Docs: Interactive Live Streaming 400–800 ms host to audience; Broadcast Streaming 1,500–2,000 msOne SDK; the audience latency level affects the price
Tencent RTC (TRTC)Average end-to-end under 300 ms globally; live co-anchoring as low as 200 ms, viewing under 1 sCalls and live rooms in TRTC; CDN delivery through Cloud Streaming Services: LEB 300–1,000 ms, HTTP-FLV 2–3 s, HLS 10–30 s
AWS IVS Real-TimeUnder 300 ms host to viewerUp to 12 publishers per stage; 10,000 subscribers per stage by default (adjustable); publish up to 720p. Stage broadcast to an IVS channel: those viewers get low latency
AWS IVS Low-LatencyUnder 5 sBroadcast only
AWS Chime SDKNot documentedMeetings: up to 250 participants at 720p, or 25 at 1080p; replication to 10,000 / 1,000
Google CloudNo end-to-end figure documented; Live Stream API segments are 2–20 s (default 6 s)Broadcast: Live Stream API (HLS/DASH) with Media CDN. No Google Cloud real-time video-calling SDK found; Meet Media API (Developer Preview) reads media from Google Meet calls
CloudflareNot documented for MoQMoQ relays (beta) on draft-14 and draft-16. Its MoQ docs list no Cloudflare client SDK for MoQ (examples use open-source moq-rs). WebRTC SDKs: RealtimeKit, Realtime SFU

* Built to scale: a Rust media plane and a Go control plane, each scaling out horizontally. Measured in lab: 6,000 viewers on one 4-vCPU relay, every frame delivered. Full data at moqom.cloud/benchmarks/load-tests.md.

Price, encryption and protocol

List prices and what protects the media

ProviderList price, videoMedia encryptionProtocol
MOQOMPrepaid, per 1,000 min $3.39 HD, $7.64 Full HD, $13.59 2K, $30.59 2K+, lower with volumeTLS 1.3 always; post-quantum SFrame E2EE (AES-256-GCM, ML-KEM, ML-DSA), required in every roomIETF MoQ Transport, draft-22 and draft-19
AgoraPer 1,000 min: $3.99 HD, $8.99 Full HD, $15.99 2K, $35.99 2K+; broadcast audience $1.99–$17.99Built-in media encryption opt-in; E2EE in beta (web, by request)Agora SD-RTN™
Tencent RTCPer 1,000 min: $3.99 HD, $8.99 Full HD, $15.99 2K, $35.99 4K; live audience $2.00–$18.00Built-in transport encryption by default; private payload encryption opt-in, not available with cloud recording or CDN relayUDP-based Tencent protocol; WebRTC on web
AWS IVS Real-Time$0.072 per participant-hour (about $1.20 per 1,000 participant-minutes), North America, first 10,000 h, any resolutionNot stated on pages citedNot stated on pages cited
AWS IVS Low-LatencyOutput per hour delivered: $0.036 SD, $0.072 HD, $0.144 Full HD (North America, first 10,000 h), plus input $0.20–$2.00/hNot stated on pages citedRTMP, RTMPS or SRT ingest
AWS Chime SDK$0.0017 per attendee-minute ($1.70 per 1,000)DTLS transport; E2EE not stated on pages citedWebRTC
Google CloudNot compared (broadcast product)Content encryption: AES-128, SAMPLE-AES, MPEG-CENCSRT/RTMP in, HLS/DASH out
CloudflareMoQ relays free during betaNot stated on pages cited (MoQ)IETF MoQ Transport, draft-14 and draft-16; draft-18 in testing

AWS's per-participant list prices are below MOQOM's HD rate, so compare on features and on your own workload. Estimate a bill →

* Built to scale: a Rust media plane and a Go control plane, each scaling out horizontally. Measured in lab: 6,000 viewers on one 4-vCPU relay, every frame delivered. Full data at moqom.cloud/benchmarks/load-tests.md.

Notes by provider

In context

Agora

MOQOM charges 85% of Agora's list price at every tier, after the same automatic volume discount Agora gives, and always at least 1¢ less per 1,000 minutes; the code enforces it. Agora bills by the total pixels a user receives; MOQOM uses the same tier boundaries so the rates compare like with like.

Tencent RTC

Tencent's video tiers and list prices match Agora's, with the top tier named 4K. TRTC documents that, to meet data-security storage requirements, it stores account and troubleshooting data in the Chinese mainland for Tencent Cloud customers and in Singapore for Tencent Cloud International customers, and that it processes audio and video only to deliver them, without storing them. Teams with data-residency or jurisdiction requirements should check which Tencent entity and region apply to their account. MOQOM runs on Google Cloud today, and you can run relays where you choose.

Google Cloud

Google Cloud's Live Stream API takes SRT or RTMP in and writes HLS or DASH segments of 2–20 seconds to Cloud Storage for delivery through Media CDN: a broadcast pipeline, not a real-time one. MOQOM runs on Google Cloud today.

AWS

AWS splits live video across products: IVS Real-Time (under 300 ms, up to 12 publishers, 720p publish), IVS Low-Latency (under 5 s) for large audiences, and the Chime SDK for meetings. Viewers of a stage broadcast to an IVS channel get low latency, not real-time latency. MOQOM carries the call and the broadcast on one stream and one standard.

Cloudflare

Cloudflare runs MoQ relays across its network (beta, free during the beta), so MoQ is becoming infrastructure, not one company's protocol. Cloudflare's MoQ documentation lists no Cloudflare client SDK for MoQ; its examples use the open-source moq-rs tools, and its client SDKs (RealtimeKit) are WebRTC. MOQOM is the SDK and platform layer. We hope to partner with Cloudflare; no partnership is signed.

All trademarks belong to their owners. This comparison does not imply any affiliation or partnership.

Sources (all accessed 6 Oct 2026)