Browser-based low-latency end-to-end encrypted streaming. No apps required.
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.
Peer-to-peer networking keyed on Ed25519 identities. A stream is named by an Ed25519 key minted in your browser — base32(publicKey) is the shareable stream key. The relay that serves it has its own, separate iroh EndpointId (a transport address), so an origin relay behind NAT can be dialled by key for relay-to-relay federation, no public port.
Hardware-accelerated virtualization. Every micro-relay runs as its own KVM guest with a strong isolation boundary and near-native performance — one broadcast per VM, booted on demand and reaped when idle.
A Rust unikernel. Each relay is a single-address-space OS image that boots straight into the MoQ server — no general-purpose userland — shrinking the attack surface and cutting cold-start to milliseconds.
Our fleet manager and unikernel build of a MoQ relay. An autoscaler boots a per-broadcast-keyed micro-relay on demand — hardened with no shell or SSH — that admits only viewers holding an access token the content owner issued and carries media the content owner has already end-to-end encrypted.
Our open-source browser player and broadcaster for MoQ — the engine behind this site. Picture-in-picture compositing, WebCodecs encode/decode, and mandatory relay-blind end-to-end AES-GCM crypto so no server sees the media.
Each stream names itself with a browser-minted Ed25519 key — base32(publicKey) is the stream key you share — and is served by an autoscaled micro-relay. On the encrypted MoQplay flow, security is built on one separation: who may reach a relay is distinct from who may watch the media. A per-broadcast token authorizes one browser on one relay; a separate content key — shown to no server — encrypts the media end-to-end, so relays only ever move ciphertext.
That stream key is also the seed of a larger design: a federated multi-CDN of all-microkernel relays. Discovery is decentralized and runs in the browser — no directory server: to publish, your browser signs a record and puts it on the public Mainline DHT, keyed by its own key; to watch, another browser resolves that key off the DHT. The record points at the origin relay's own iroh endpoint, so any fleet can find the origin and pull from it. Your browser always reaches its nearest edge over QUIC/WebTransport; the origin → edge federation hop then carries the media on native QUIC by default, or over iroh when a viewer opts in with ?xport=iroh — NAT-friendly, no public origin port. Proven in July 2026: one fleet resolved another's stream key off the DHT and pulled a live stream across two independent networks. (This watch-by-key path rides the relay's open subscribe — the stream key is the capability. The relay-blind end-to-end encryption above is the separate MoQplay flow.)
?xport=iroh transport option (developer reference)
Paste a node id or a share link to tune into a live broadcast.