Blockcast MoQCAST

Low-Latency Multicast over the Internet. Finally.

MoQCAST targets under 100 ms from Blockcast ingress to rendered frame, upstream encoding excluded, for live sports, esports, and interactive events. The live demo shows the measured figure when one is available. It plays in browsers and client-side players over existing infrastructure. For operators, there’s no new equipment to purchase. For content providers, there’s no more duplicative bits to deliver.

Lab and Demo Results

Lab Result on Multicast: 97% Less Frozen Picture from Network Loss

An optional repair track protects keyframes and their timing packets. On multicast in Blockcast’s lab, it cut frozen-picture time from network loss by 97%. That’s at keyframes that ordinary repair couldn’t rebuild, across three loss patterns.

52% Fewer Bits on Multicast than on Unicast, in the Recorded Demo

In Blockcast’s recorded demo, three players on one machine received 52% fewer bits on multicast than on unicast, repair included.

Multicast Streaming

Say Hello to MoQCAST

All the Benefits of Multicast, None of the Baggage

MoQCAST leverages Media-over-QUIC (MoQ) and TreeDN to enable multicast over the internet without any of the baggage. With just a Chrome extension (for multicast in the browser) or an SDK (for client-side players), you can spread your multicast signal around the globe via the Blockcast RELAY. No more specialized multicast operator equipment needed. Deliver live video over multicast to web browsers and client-side players.

One Source, Multiple Delivery Paths

Whether viewers are watching in a web browser or in an app built on the SDK, your content reaches them without you having to do anything extra. By placing a MoQCAST Packager downstream from your live encoder, you can package everything into MPEG Media Transport (MMT) and deliver via the Blockcast RELAY to MoQCAST-enabled players.

Broadcast Resiliency, Streaming Costs

With MoQCAST, you get the benefits of broadcast (multicast) with streaming economics. That’s because MoQCAST is deployed via the Blockcast MAHP, a software-based reverse proxy which can be deployed on common, off-the-shelf hardware in containers or standalone servers. You get geographic redundancy by leveraging existing cloud providers (or your own datacenters) without the hardware footprint of traditional unicast delivery.

Your Infrastructure
MoQ Relay (Blockcast RELAY)
AMT Relay / TreeDN (Blockcast RELAY)
Content SourceYour live / VOD feedMoQ Relaydraft-ietf-moq-transportBlockcast RELAY · QUICAMT Relay / TreeDNBlockcast RELAY · PIM-SSMBrowser · AppCan switch paths mid-streamBlockcast Gateway · Native · Browser

Single encode, two delivery paths: Your content feeds into the MoQCAST Packager (built on FFmpeg), which packages to MMT. The Blockcast RELAY delivers via two paths: the MoQ Relay (QUIC) and the AMT Relay / TreeDN (PIM-SSM multicast over the internet).

How It Works

MoQCAST Playback: Browser and App

It Begins with the MoQCAST Packager

Place a MoQCAST Packager downstream from your current live encoding infrastructure to package your streaming content into an MPEG Media Transport (MMT) stream. Built on the industry-standard FFmpeg, it simply repackages your stream into MMT for multicast transport. Nothing else in your workflow needs to change.

From Encoder to Relay to Player

Once you have an MMT container, MoQCAST distributes it via the Blockcast RELAY (MoQ relay and AMT relay) to web browsers and client players in applications.

Multicast Playback in the Browser

Deploy the MoQCAST Player for an out-of-the-box solution for multicast playback in web browsers. Or integrate the MoQCAST Playback SDK into your own player to enable multicast receiver capabilities. Either way, you send a multicast stream straight to the player — no intermediary equipment needed.

Switch Paths Mid-Stream

Unicast and multicast carry the same media packets, so a viewer can switch delivery paths without restarting the stream. In Blockcast’s recorded demo, moving each of three players from unicast to multicast cost at most one pause.

Browser & Mobile

Multicast, Straight to the Browser

The Blockcast Gateway brings native and tunneled multicast directly into web browsers and mobile apps. Subscribers receive live multicast streams over direct socket APIs or WASM-based AMT tunnels, with real-time status, packet counters, and bitrate monitoring built in.

Blockcast Gateway showing active multicast subscriptions in a web browser

Why Multicast?

The economics of unicast don’t scale. Multicast changes the equation.

Reducing Delivery Costs

Streaming content is delivered via unicast. Every user gets a dedicated bandwidth resource to receive the same stream of bits, even if they are sitting next to each other. 1 million viewers at 5 Mbps consumes 5 Tbps of backbone bandwidth. But like broadcast, with multicast a single stream of content is delivered to a given geographic area. Any users who want to watch just connect to the stream, significantly reducing delivery costs through commercial networks like ISPs and CDNs.

Less Infrastructure Needed

Streaming relies on tens of thousands of servers (reverse proxies like Varnish and NGINX) at the edge of ISP networks. No matter how powerful, each server supports a finite number of individual connections. Combined with the need for redundancy and geographic spread for fast connection times and low RTTs, the hardware footprint for a large live streaming event is significant. Multicast does away with all that. Players “subscribe” to the stream instead of connecting to a server — less infrastructure, less cost, less to manage.

Platform Features

Real-Time Delivery

Built on QUIC, the Blockcast RELAY’s MoQ path is designed for low latency — ideal for real-time use cases like live sports, esports, and interactive experiences.

Built-In Security

Optional packet authentication (TESLA on ROUTE streams, ALTA on browser streams) lets receivers detect injected or tampered packets.

Integrated Discovery

DNS-based discovery finds the topologically nearest Blockcast RELAY automatically. No separate signaling infrastructure needed — discovery is built into the delivery path.

Streaming Analytics

Built-in logging and support for player analytics like CMCD provide detailed stream-level and session-level data for monitoring quality of experience at scale.

Technical Details

TreeDN

Find out more about TreeDN and how it enables MoQCAST to deliver your streaming content multicast over the internet.

MoQCAST Architecture

Get technical details and diagrams showing how MoQCAST goes from single MMT encode to multi-path multicast delivery.

MPEG Media Transport

Learn about the MMT Unified Container and how it makes multicast streaming content possible to browsers and apps.

FAQs

Yes. You can use the MoQCAST Player, which already includes the SDK needed for multicast playback. Blockcast’s TypeScript receiver library, shared by three browser players, is public on npm as @blockcast/mmt-* under Apache-2.0.

Not for QUIC playback, which runs in a Chromium-based browser. AMT and native multicast require a verified local Blockcast bridge, such as our Chrome extension. The live demo guides you through availability and setup.

The initial format is not important. So long as it’s a format that FFmpeg can ingest, the MoQCAST Packager can package it as MMT for multicast delivery.

The MoQCAST Player or a MoQ player with the MoQCAST extensions always starts as a unicast player. It will “upgrade” to multicast with AMT fallback if native multicast is not available.

MoQ is an initiative of the Internet Engineering Task Force (IETF). There are open-source implementations like MoQ Tail (moqtail.dev) and moq.dev where you can get detailed technical information about this QUIC-based streaming approach.

The ideal use cases for any QUIC-based streaming are those that require real-time content delivery such as betting and interactive experiences. MoQ is also ideal for live sports where low latency makes a meaningful difference.

The Blockcast RELAY supports Juniper for hardware AMT relays and Linux 5.16+ for soft relays.

WebRTC requires specialized servers. MoQ can be delivered from standard HTTP reverse proxies, making it scale much better and cheaper than WebRTC. In addition, the media functions being developed as part of the MoQ effort improve the delivery of video using QUIC.

Ready to deliver low-latency live streams at scale?