Skip to content

FAST channel distribution

FAST Channel SRT Distribution: One Live Feed, Independent Takers

A FAST channel can have playout, ad insertion and platform delivery handled elsewhere — and still need a reliable way to move its live contribution feed to more than one destination. SRT Cloud receives one live SRT feed and delivers separately configured bit-exact outputs to independent takers. No transcoding. No local distribution hardware.

Diagram of one FAST channel SRT feed entering SRT Cloud and copying to multiple independent takers

The distribution problem

The viewer-facing stream is only one layer.

Teams often need the same live contribution feed delivered separately to a platform, an affiliate, a distribution partner or a monitoring endpoint. Those destinations may be independently operated, so one shared network multicast is rarely the operating model. The practical question is how to give each taker its own reliable copy.

The handoff

One input. A separate output for every taker.

  1. 1

    Send the live contribution feed

    Send one live SRT contribution feed to SRT Cloud.

  2. 2

    Configure each taker

    Create an output for each independently addressed destination.

  3. 3

    Deliver a bit-exact copy

    The input is copied, not transcoded, for every configured output.

Where it fits

A copy layer, not a replacement stack.

SRT Cloud fits when the job is clean one-to-many SRT distribution. It does not replace playout, ad insertion, scheduling, consumer playback or a broad OTT workflow; keep those jobs with the systems that own them.

One live SRT feed to multiple independent takers
SRT Cloud is designed for this.
Bit-exact copies without transcoding
SRT Cloud is designed for this.
FAST playout, ad decisioning or scheduling
Use the relevant playout or ad-tech system.

Why SRT for the handoff

Transport is one job. Distribution is another.

SRT is a transport protocol used to move low-latency live video between endpoints across less predictable networks. It solves the transport leg; distribution still requires a way to produce and manage the copies each downstream taker receives. For protocol context, see SRT transport protocol background.

Start with one destination

Add outputs when another endpoint needs its own copy.

Start the trial with the live feed and the first real taker. Review current per-output terms as requirements change.

Start a free trial

FAQ

FAST channel distribution, explained

Is SRT Cloud a FAST channel playout platform?

No. This page describes SRT Cloud’s role in copying a live SRT feed to multiple distribution takers. Playout, scheduling, advertising and consumer playback remain separate layers.

Does each destination get its own copy?

Yes. Each configured output delivers a bit-exact 1:1 copy of the incoming SRT feed to one taker.

Does SRT Cloud transcode the feed?

No. SRT Cloud copies the feed without transcoding.

Can we begin with one taker?

Yes. Start with the destination you need now and review current per-output terms on the pricing page as requirements change.