One live feed to many platforms

Send one encoder feed to your own site and to YouTube, Twitch and others at once

Example design

01Set up outputsBefore the event the Worker adds an output for each destination, with the RTMP address and stream key each platform issued.
02One feed inThe encoder sends a single feed to the Stream live input.
03ForwardStream sends the feed on to every enabled output, and your own player streams it from Stream.
04Switch one offIf a platform misbehaves or the rights do not cover it, the Worker disables that output. The rest carry on.
05RecordingStream records the event, so it is on your site as video on demand shortly after the stream ends.
ifThe encoder dropsEvery output drops with it, since they all come from the one input. When the encoder reconnects, the outputs resume. The runbook says who restarts it and how quickly.

The problem

Streaming an event to your own site, YouTube, LinkedIn and Twitch at the same time usually means either one encoder per platform or a third-party restreaming service. Several encoders multiply the upload bandwidth and the points of failure at the venue. With Stream, the encoder sends one feed, and Stream forwards it to every destination and to the player on your own site.

What it uses

Stream: Live input, outputs to other platforms, playback and recording
Workers: Output management, with an admin page for the event team
Secrets: The stream key for each platform

The decisions, and why

DestinationsUp to 50 per live input: Stream's limit is far more than most events use, so a regional channel or a partner's account can be added without another encoder.
ControlEach output on or off: Rights often differ by platform. Turning off one destination leaves the others running.
Stream keysHeld as secrets: A leaked key lets anyone broadcast on your channel, so only the Worker can read them.
Your own sitePlayed from the same input: Your player gets the event from Stream at the same time, and the recording is ready for on-demand viewing afterwards.