MoQ CLI Publisher
Media over QUIC contribution ingest: publish a file, TS, FLV or HLS as a MoQ broadcast.
MoQ CLI Publisher is the reference command-line publisher for Media over QUIC (MoQ), an emerging IETF standard for live media transport. 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. This appliance is the contribution-ingest side of that pipeline: the moq-cli publisher imports your media and publishes it as a MoQ broadcast to a relay.
Key features
- Contribution ingest: import fragmented MP4 / CMAF, MPEG-TS, FLV, or pull an HLS / LL-HLS playlist, and publish it as a MoQ broadcast
- Bundled co-located relay so the box works standalone out of the box; or publish to an external relay by seeding its URL
- Publishes a bundled sample clip on first boot, so the appliance is a live feed immediately
- Sub-second live latency over QUIC / WebTransport, not segmented HTTP
- Standards-track: implements the emerging IETF Media over QUIC (moq) transport
- Self-signed TLS certificate generated at first boot so the co-located relay runs immediately; the certificate fingerprint is published for browser cert pinning
- Ships the unmodified upstream moq-cli / moq-relay (Apache-2.0 OR MIT)
- Open demo: no login to manage
Use cases
- Feed existing content (a file, an MPEG-TS/FLV feed, or an HLS origin) into a MoQ delivery path without writing any code
- A contribution front door that ingests at the edge and rides MoQ upstream toward a relay mesh near your audience
- Experimenting with and building on the emerging Media over QUIC standard
Why run it on the NetActuate edge MoQ is designed for a relay mesh that lives close to audiences, fed by contribution publishers at the edge. Running the publisher in a PoP near your source shortens the first mile into MoQ and keeps the live path on infrastructure you control.
Deployed from the NetActuate marketplace, the publisher boots pre-configured from your seeded values: the management/landing port, the co-located relay's UDP media port (QUIC/WebTransport), the broadcast name, and an optional external relay URL to publish to instead of the co-located one. The media transport is QUIC over UDP, so the deploy network must allow UDP passthrough to the relay port. This is a HEADLESS appliance: there is no web console. The co-located landing page documents the exact publish command, the broadcast name and the relay endpoint, and only serves once a first-boot self-check has confirmed a real pub->relay->sub loopback (the publisher publishes the sample to the co-located relay and a local subscriber reads it back).
Frequently asked questions
How do I deploy MoQ CLI Publisher on NetActuate?
Use the Deploy on NetActuate button to talk to our team. We provision MoQ CLI Publisher on a NetActuate virtual machine in the point of presence you choose, close to your audience. Each deployment runs in the single location you select.
What does it cost to run MoQ CLI Publisher?
MoQ CLI Publisher is open-source software and free to run on the marketplace - you pay only for the NetActuate compute (virtual-machine size and location) it runs on, at standard rates. There are no usage-based software fees.
Where can MoQ CLI Publisher run?
MoQ CLI Publisher can be deployed in any of NetActuate's 45+ points of presence across every continent, so you can place ingest, transcode, delivery and caching close to your contributors and viewers.
Who supports MoQ CLI Publisher?
NetActuate operates and supports the underlying infrastructure - the virtual machine, network and edge platform. The application itself is supported by its upstream open-source project.
.png){kind=icon}
.png)
