Frequently asked questions

Stream Repeater is a multistreaming platform that receives one live stream from an encoder and relays it to multiple configured streaming destinations.

You publish one live stream to a workspace ingest URL. For every destination you have configured, a separate relay process picks that stream up from our media server and pushes a copy onward. A supervisor continuously compares what is running against what you configured, and restarts anything that has failed.

Adding destinations does not. The fan-out happens on our servers, not on your connection. What we cannot do is reduce your upload below one stream — that single inbound stream still has to leave your machine.

No. Relays stream-copy on every plan, so each destination gets the exact feed you sent — same resolution, same bitrate, no generation loss and no added latency from a re-encode. Transcoding is not offered. The one exception is audio for RTMP destinations, which is remuxed to AAC because the format requires it; the video is untouched.

Anything that can publish RTMP, RTSP or SRT. There are step-by-step guides for 8 encoders, including OBS Studio, Streamlabs, vMix, XSplit and FFmpeg — but nothing depends on your encoder being one of them.

Yes. The browser studio broadcasts your camera, microphone or screen over WebRTC with nothing to install — the browser does the encoding.

Yes. There are iOS and Android apps that broadcast from the handset's camera and microphone, and also act as a remote control for chat, destinations, recordings and alerts. Any mobile encoder that speaks RTMP or SRT will work too.

You can configure a backup ingest so a second encoder takes over. Failing that, viewers see a branded holding slate rather than a black screen, and the supervisor restarts failed relays with backoff rather than ending the broadcast.

There are setup pages for 90 destinations, including Twitch, YouTube, Kick and Facebook — and one of those pages covers custom endpoints, because anything that accepts RTMP, RTMPS, RTSP or SRT can be added by pasting its URL and key. The list is a convenience, not a limit.

That is a plan limit rather than a technical one — see the pricing page for the destinations-per-channel allowance on each plan.

No. Whether you may relay to any given platform depends on that platform's own terms, which they can change without notice.

Yes, on plans that include it. Streams can be recorded to a cloud VOD library and clipped, within your plan's storage allowance and retention window.

Twitch, YouTube and Kick messages arrive in a single feed you can read, reply to and moderate from, alongside chat from your own watch page. TikTok is read-only and arrives through the optional Local Agent, because there is no official API for it.

Yes. Overlays are built in the browser from ready-made templates and widgets — chat, viewer counts, alerts, goals, countdowns, polls and more — then added to your encoder as a single browser-source URL.

Per-destination health and throughput are reported to your dashboard in real time. When a relay fails we can notify you by email, by push to the mobile app, or by webhook — with Discord and Slack formatted natively. We do not send text messages.

Yes — a token-scoped REST API for managing channels and destinations, documented by an OpenAPI schema, plus signed outbound webhooks for stream and destination events.

Yes, and it does not ask for a card.

Your plan, which sets your channel, destination, outbound bandwidth and recording limits. Only outbound traffic is metered; the stream you send us and our internal relay traffic are not.

Yes. People can be invited to a workspace as owner, admin, member or viewer, each scoped to what they should be able to see.