Global MoQ CDN for Low Latency CMAF

How It Works
Encoder
DASH-IF Ingest (CMAF) from your encoder
Cloudflare MoQ
Published to Cloudflare's global MoQ relay network
MoQpush
Orchestrated edge servers pull streams to warm relays
Playback
Shaka Player with MoQ streaming support
Getting Started

Sign in and create a namespace

Go to the Dashboard and sign in with Google or Discord. Create a namespace (e.g. my-stream) and select which regions to warm.

Run the MoQpush app

# Run it with your Push Key
./moqpush-app --push-key mpk_YOUR_PUSH_KEY_HERE --port 8888

The app will authenticate with moqpush.com, get the relay URL for your namespace, and start listening for CMAF-IF ingest on the specified port.

Point your encoder

Configure your encoder (e.g. Ateme Titan Live, FFmpeg, GPAC) to push CMAF-IF segments via HTTP PUT to:

http://localhost:8888

Once the first init segment arrives, moqpush-app connects to the Cloudflare MoQ relay and begins publishing. Your configured edge servers will automatically start pulling to warm the network.

Share the playback link

Your stream is live! Share the link with anyone:

https://moqpush.com/my-stream

Viewers get low latency playback via Shaka Player and WebTransport in a browser.

Features

Global Pre-positioning

Edge servers in 5 regions pull your stream through Cloudflare.

Low Latency

MoQ over QUIC/WebTransport delivers low latency streaming.

Simple Ingest

Standard DASH-IF CMAF ingest over HTTP PUT.

Real-time Stats

Live publisher and player metrics, per-region warm status, and real-time dashboards.

One-click Sharing

Share a link and anyone can watch in their browser.

Secure

QUIC is always TLS 1.3 end-to-end. CMAF DRM is supported.

Why MoQ & QUIC

Beyond HLS & DASH

Traditional ABR protocols buffer 6-30 seconds of content, making true live interaction impossible. MoQ Transport delivers media over QUIC streams with low latency while maintaining broadcast-scale reliability — no trade-off required.

No Head-of-Line Blocking

Unlike TCP-based protocols (RTMP, HLS, DASH), QUIC provides independent stream multiplexing. A lost packet on one video track doesn't stall audio or other tracks. Each media stream flows independently through the connection.

Network Resilience

QUIC's Connection ID replaces TCP's fragile 4-tuple. Streams survive WiFi-to-cellular handoffs, NAT rebinding, and IP changes seamlessly — the connection just keeps going. Critical for mobile and field production.

Pull-Based Architecture

Unlike push-based protocols (WebRTC, SRT, RTMP) that stream constantly regardless of viewers, MoQ only transmits tracks when explicitly subscribed. Bandwidth-efficient by design — critical for satellite, cellular, and constrained networks.

Priority-Based Congestion

When bandwidth drops, MoQ doesn't blindly drop frames like WebRTC. Subscriptions carry priority levels — the QUIC library transmits packets in priority order. Low-res streams and audio survive while high-res feeds gracefully degrade.

Encrypted by Default

QUIC mandates TLS 1.3 and encrypts packet headers — even packet numbers. No middlebox interference, no ISP throttling, no protocol ossification. Uses UDP port 443 for universal firewall traversal.

Userspace Innovation

Unlike TCP (locked in OS kernels), QUIC runs in userspace. Apps ship their own implementation with modern congestion control (BBR) without waiting for OS updates. Deploy improvements instantly across all platforms.

Production Proven

MoQ is not theoretical — it's been deployed in production, proving real-world reliability in harsh network conditions.

Request Binaries

Get early access to MoQpush