MoQ Is the Standards-Based Path Off Satellite. The Network Under It Decides Whether Distribution Can Use It.

Primary distribution runs on transport streams, and adaptive bitrate streaming was never built to carry that workflow. Media over QUIC (MoQ) is the credible standards-based successor, but it has one problem it does not solve on its own: it makes no latency guarantee and it tolerates dropped frames. Distribution tolerates neither. That is a network problem, not a protocol problem, and the network is the layer NetActuate operates.

What Is NetActuate MoQ Relay?

Teams leaving satellite are not shopping for a new video format. They want something that carries the workflow they already run, and that workflow is transport-stream based for nearly all of them. NetActuate MoQ Relay is a managed service. A tenant provisions relay capacity across NetActuate locations, chosen from more than 45 worldwide, receives credentials scoped to its own namespaces, and publishes tracks into the nearest relay. Subscribers pull from the relay closest to them. You publish once; your audience is served from that single copy no matter how large it grows.

Why MoQ, and Why Not ABR?

Adaptive bitrate streaming solves reaching millions of heterogeneous viewers over unmanaged networks. Distribution is a different problem: a defined set of professional endpoints, a transport-stream workflow, contractual quality, and no tolerance for adaptation artifacts on the way to air. The mismatch is a workflow mismatch. MoQ, by contrast, is standards-based and open rather than a single vendor's stack. It keeps a transport-stream workflow intact, and it scales through relays in a way point-to-point contribution protocols cannot without heavy operational effort. For a team replacing a transponder with something defensible to a rights holder for the next decade, that combination is what's on the table.

Why Does the Delivery Record Matter More Than Edge Count?

The differentiator is the record a customer can actually read: delivery accounted for per hop and per track, drawn from the same store NetActuate's own network operations reads. When a path degrades, the record says so rather than reporting a clean zero. Much of the managed MoQ market ships no comparable metrics surface at all. That is the axis NetActuate competes on. Edge count is not.

What Problem Does MoQ Not Solve by Itself?

MoQ makes no latency guarantee, and it tolerates dropped objects under pressure. That is a reasonable design position for a protocol meant to span the open internet. It is not workable for distribution, where everything has to arrive, every time, inside a delivery window that is a commitment rather than a target. This is the objection every MoQ distribution conversation runs into.

"Every conversation about MoQ ends up at the same question, which is who runs the relays," said Mark Mahle, CEO at NetActuate. "We already run the network underneath them, so that is our lane."

MoQ cannot promise what the path underneath it will not deliver. Put MoQ on a network measured hop by hop, steered in real time, and redundant beneath the session, and the properties distribution needs come from where they were always going to come from: the network, not the protocol. What NetActuate measures and stands behind is ingress to egress across its own network, per leg, every hop. A customer's last mile at either end, and any protective buffer their own stack adds, stay separate from that number.

How Does MoQ Relay Actually Work?

MoQ Relay runs on three mechanisms: anycast rendezvous, where publishers and subscribers reach one address and land at the nearest relay ingress, so the network handles relay selection instead of a directory service the customer has to run; closed-loop steering beneath the relays, where NetActuate measures the paths between relay points continuously and steers around degradation underneath the QUIC session, so the relay mesh inherits path quality it didn't build itself; and session survival across path changes, where a QUIC session is pinned to the serving location's stable unicast address after rendezvous, so the route underneath can change without the session being torn down. In testing with four relays, a single relay delivered 16 times more video without increasing backbone usage.

Does MoQ Relay Require the Media Substrate, and How Do You Evaluate It?

No. MoQ Relay is a separate service that composes with the Media Substrate and does not require it. A customer already carrying contribution and primary distribution on the Substrate can run the fan-out layer and the protected transport layer on one network, under one measurement plane. A customer who only wants relays buys only relays.

There is also no open public relay to test against. Teams evaluating the service get a no-charge evaluation deployment of their own, in the locations they choose, with full observability, rather than shared access to a network carrying someone else's traffic. That absence of an open relay is the reason to trust the evaluation: what you test is what you'd run.

See our MoQ Relay page, and read the MoQ Relay press release.

Book an Exploratory Call With Our Experts to see what a MoQ Relay evaluation deployment looks like on a network built to carry it.

‍