MoQ Hang Demo

MoQ Hang Demo lets you see sub-second Media over QUIC (MoQ) live in your browser, self-hosted on your own VM. It bundles the reference MoQ relay from the quic.video ecosystem with the open-source hang web demo: a browser publish page (share your camera, screen, or a file into a live broadcast) and a watch page that discovers live broadcasts on the relay and renders them with sub-second latency.

Media over QUIC is an emerging IETF live-media transport that carries live video and audio over QUIC and WebTransport, aiming to combine WebRTC-class latency with HLS/DASH-class scale in one architecture. This appliance is the fastest way to put the canonical quic.video publish-and-watch experience on infrastructure you control.

Key features

• Browser publish page: go live from a camera, screen share, or a file, no plugins
• Browser watch page: discover and play live MoQ broadcasts, sub-second glass-to-glass
• A live relay stats dashboard page (broadcasts, subscribers, traffic)
• The reference kixelated/moq-relay bundled in, terminating WebTransport/QUIC on a UDP media port and fanning broadcasts out to subscribers
• A self-signed TLS certificate generated at first boot so the stack runs immediately
• Fail-closed self-check: the web demo is served only after a first-boot relay-health check (a valid certificate fingerprint plus a running relay), so the management page is proof the relay is up

Use cases

• Evaluate and demo Media over QUIC end to end on your own edge, today
• A publish/watch reference deployment for developers building on the @moq/* components
• Place a relay in a PoP close to your audience and see the latency for yourself

Why run it on the NetActuate edge MoQ's whole value is low latency at scale, and that is a placement problem: a relay in a PoP near your viewers shortens the path from glass to glass. On the NetActuate anycast edge you can put MoQ relays close to audiences everywhere, the foundation for an anycast MoQ relay mesh with encode-once, serve-sub-second delivery.

Browser playback needs a trusted certificate (important) The appliance boots with a self-signed certificate so it runs and serves the demo pages out of the box, and a local publish->relay->subscribe loopback proves the dataplane. Browsers will not open a WebTransport session to a self-signed certificate unless its hash is pinned (which also requires a short-lived certificate), so full publish/playback across the internet requires you to point a real domain and a trusted TLS certificate at the instance (set mkt_announce_host and front the relay with your certificate). The UDP media port must be reachable (UDP passthrough). This is an open demo relay with no login.