Multistreaming
Compose the show once and send it to Twitch, YouTube, Kick and any RTMP target together. The split happens in the desktop engine, on your hardware — which is why there is no per-destination fee attached to it.
Each output owns its own connection, retry and status.
Signal path
The expensive part of streaming is encoding, and it happens once. Everything after it is a connection.
Cameras, capture, overlays — composed once in the desktop studio.
The engine encodes a single program feed, not one per platform.
Each destination gets its own RTMP connection, with its own retry and its own status.
Twitch, YouTube, Kick, and any custom RTMP target.
What you get
Going to several platforms is not interesting if they can only be managed as a single block.
Twitch, YouTube, Facebook, Instagram, Kick and Restream come with their ingest URL filled in. Anything else — including TikTok, which publishes no public ingest URL — takes a server address and a key, which is all a custom RTMP target ever needs.
Destinations are not one switch. Bring a platform up mid-stream, or drop one that is misbehaving, without touching the others.
Each output reconnects on its own backoff, with its own attempt limit and delay. A platform that refuses your key or drops your connection does not take the rest of the broadcast with it.
Route a destination to the vertical canvas and send a 9:16 cut to the platforms that want one, from the same session. The engine refuses the route unless the vertical canvas is actually running, rather than quietly sending 16:9 to a 9:16 platform.
Kick now requires RTMPS. A destination still saved against the old address is corrected when it loads, so a stream key you entered months ago does not fail the night you need it.
Idle, starting, active, reconnecting, stopping, error — each destination reports its own, so a platform that is struggling is visible as itself rather than as a broadcast that feels wrong.
The trade
Local fan-out is cheaper for you in one dimension and more expensive in another. Both halves are worth stating, so here is the second one with your numbers in it.
The engine encodes once and pushes that same program to each destination in turn, so the copies cost exactly what the original did. Every platform you arm here is another full stream leaving your building.
Your machine sends the same encoded program 4 times. Nothing about that number is billed by us. 2 at once on the free plan, unlimited on every paid plan.
A cloud multistreaming service pays egress for every destination you add, and prices accordingly. StreamLumo splits the stream on your machine, so a fourth platform costs us nothing and costs you nothing.
Local fan-out spends your bandwidth: four destinations at 6 Mbps is roughly 24 Mbps leaving your connection. That is the honest trade, and it is the reason a cloud relay exists as a separate, paid path rather than the default.
Stream keys are handed to the engine and never held in the app's own storage. Nothing about going live to four platforms requires us to hold four credentials.
Early access · By invitation
Multistreaming ships in the desktop studio, on Mac. Join the early-access list and we will email you the moment a seat opens.