MoQ Relay
MoQ Relay is the reference relay for Media over QUIC (MoQ), an emerging IETF standard for live media transport, available in the NetActuate Marketplace as a one-click appliance. Instead of the classic segmented-HTTP stack (HLS/DASH) that trades latency for scale, MoQ carries live video and audio as prioritized streams over QUIC and WebTransport, reaching sub-second glass-to-glass latency while still fanning out to many viewers. This appliance runs the reference relay from the quic.video ecosystem: a headless Rust service that terminates WebTransport and QUIC on a UDP media port and relays broadcasts from publishers to subscribers. It is free and open source, and is grouped under the Media & Streaming category.
What It Does
MoQ Relay fans out live media over QUIC and WebTransport. Common uses include:
- Sub-second live video and audio delivery over QUIC and WebTransport
- Relaying broadcasts from publishers to many subscribers
- Experimenting with the emerging Media over QUIC (MoQ) transport
- Running a demo relay for the quic.video web tools and the MoQ CLI
Deploying the relay near your publishers and viewers keeps the low-latency QUIC path short.
Vendor and Project
MoQ Relay is an open-source project (Apache-2.0 and MIT). This appliance runs the official reference relay from the quic.video ecosystem.
- Source: github.com/kixelated/moq
- Web tools: quic.video
NetActuate supports the underlying infrastructure. Application-level support follows the listing's SLA class (open-source, best effort).
Sizing
| vCPU | RAM | Disk | |
|---|---|---|---|
| Minimum | 1 | 2 GB | 20 GB |
| Recommended | 2 | 4 GB | 50 GB |
No VPU (hardware acceleration) is required for this appliance.
Configuration Fields
When you deploy, you provide these fields. They are written into the appliance at first boot.
| Field | Required | Default | Notes |
|---|---|---|---|
| MoQ media port (UDP) | No | 443 | The UDP port the relay listens on for MoQ and WebTransport (QUIC) media. The deploy network must allow UDP passthrough to this port |
| Management / landing port (TCP) | No | 8080 | TCP port for the co-located landing and instructions page. It returns HTTP 200 once the relay is up and shows the relay endpoint and certificate fingerprint |
| Announced hostname (optional) | No | instance IP | Optional FQDN you will point at this instance, used in the self-signed certificate SAN and shown as the relay endpoint. Browser playback needs a real domain and TLS certificate |
Using the Appliance
After the build completes:
- Confirm the relay is up by browsing to
http://YOUR_VM_IP:8080/. The landing page returns HTTP 200 only after a first-boot self-check runs a real MoQ publish loopback against the relay, so a 200 confirms the QUIC and WebTransport dataplane is serving. It prints the relay endpoint and the certificate fingerprint. - Open the UDP media port. The relay speaks QUIC and WebTransport over UDP on port
443by default. Make sure your network and firewall allow UDP passthrough to it; that is the endpoint publishers and players connect to. - Point clients at it. Use the open-source MoQ web tools at quic.video or the
kixelated/moqCLI, pointed athttps://YOUR_VM_IP:443.
Note: The relay boots with a self-signed certificate so it runs immediately, and publishes its sha256 fingerprint at
http://YOUR_VM_IP:4443/certificate.sha256for pinning. For real browser playback, set the announced hostname to a domain you control and front the relay with a trusted TLS certificate. The relay is an open demo relay with no authentication; put access control in front before exposing it broadly.
FAQ
Is there a software license fee? No. MoQ Relay is open source (Apache-2.0 and MIT). You pay only for the NetActuate infrastructure and bandwidth.
Why does the landing page matter? It returns HTTP 200 only after a first-boot self-check proves the relay's QUIC and WebTransport dataplane is serving, so a 200 is a real health signal.
Can browsers play from it directly? Only with a trusted certificate. The relay ships a self-signed certificate; set the announced hostname to a domain you control and front it with a real TLS certificate, or pin the published fingerprint.
Version and Changelog
| Version | Status | Released |
|---|---|---|
| 0.10.15 | Current (default) | 2026-07-14 |
Official kixelated/moq-relay 0.10.15 image (Apache-2.0 and MIT), built on Ubuntu 24.04 LTS.
Deploy
- Deploy in the portal: Deploy MoQ Relay
- View the listing: portal.netactuate.com/platform/marketplace/l/moq-relay
- Public listing: netactuate.com/marketplace/moq-relay
Need Help?
Contact support@netactuate.com or open a support ticket from the portal.