nanoStream Cloud

nanoStream Cloud is nanocosmos’s ultra-low-latency streaming platform, aimed at cases where a late frame costs money: iGaming, live auctions, sports betting, financial services, and interactive entertainment. It is one of the few MoQ deployments that has been carrying commercial traffic long enough to have data about it.

MoQ is on by default

Media over QUIC arrived in nanoStream H5Live Player version 5.0 and is enabled unless you turn it off:

'playback': {
  'enableMediaOverQuic': true,     // default: true
  'enableQuicConnectionProbe': true // default: true
}

The player probes WebTransport/QUIC connectivity during setup and falls back to WebSocket delivery if MoQ is unavailable or the probe fails, so enabling it is not a cliff. Browser support tracks WebTransport and WebCodecs: Chromium 110+, Firefox 130+ on Windows and macOS, and Safari from OS version 26.4.

The performance data

In July 2026 nanocosmos published what appears to be the first public benchmark of MoQ measured from real paying-customer traffic rather than a lab. The dataset covers a sustained twelve-month period across Europe, Asia, North America, South America, Africa, and Oceania, comparing WebTransport-based MoQ against the WebSocket path on the same CDN.

WebTransport outperformed WebSocket on both player connection time and end-to-end latency in all six regions, with reported latency improvements of 25% to 50% and end-to-end latency held at around 500 ms with fewer outliers.

The methodology matters as much as the numbers. This is a same-platform, same-customer A/B across a year, which is a far stronger claim than a staged comparison against someone else’s stack — and it is the kind of evidence that has been conspicuously missing from MoQ vendor marketing. Read it alongside our own account of where the latency actually goes.

Notes

The MoQ path here is a transport upgrade inside an existing product rather than a rebuild around it — the same platform, players, and workflows, with QUIC underneath where the browser allows. For teams already on nanoStream, that makes adoption close to a configuration change.