e2eMoQ

Media over QUIC with end-to-end encryption

Browser-encrypted WebCodecs, streamed via WebTransport
The key lives in the link fragment — a server never receives it
Sub-second glass-to-glass. No app, no account, no recording

Built on open standards

📡

Media over QUIC

An IETF transport for live media built on QUIC's multiplexed, loss-tolerant streams and built-in TLS 1.3. Publish/subscribe tracks and relay fan-out deliver sub-second, glass-to-glass latency on the open internet.

🌐

MoQ.Pro Video Network

e2eMoQ streams ride moq.pro, Luke Curley's hosted Media-over-QUIC network. Global relays with WebTransport and automatic WebSocket fallback, plus built-in reconnect — so a broadcast plays in every modern browser, including iPhone, and rides out flaky networks.

🔒

How you're protected

Your browser encrypts every frame before it leaves. The key is derived from a secret we never receive — the one living in your share link — so we cannot watch your broadcast. Add a passcode under Protect and a viewer needs that too. No account, no email, no location data is stored.

How it works ↓ · What we can and cannot see →

Passcode

Send this separately from the link. The refresh icon re-keys the stream and cuts off viewers using the old passcode.

When you go live, your browser captures and encodes the media with native WebCodecs, encrypts every frame, and publishes it to the moq.pro CDN over QUIC. Viewers subscribe from the nearest relay and decrypt in the page. The CDN carries only ciphertext it cannot read.

The key never reaches us. It is derived in your browser from a secret we never receive: it lives in the part of the share link after the #, which browsers never send to a server. So the link is what decrypts your broadcast — treat it as the key it is. Switching on Protect mixes in a second secret, the passcode, which is deliberately not in the link: send the two by different routes and intercepting either alone is worthless. Either way, we could not watch your broadcast if we were asked to.

Each broadcast is reached through a short-lived moq.pro access token minted by e2eMoQ's own Cloudflare Worker. It is signed with a key whose public half alone was given to moq.pro, so the CDN can check our tokens and cannot forge one. Live chat is encrypted the same way: messages and display names are sealed in your browser under a key derived from the same link, so the chat server relays text it cannot read. That also means there is no moderation of chat — there is nothing for us to moderate.

More about Media over QUIC → · Browser Support · Close