Stream
The multistream cockpit for going live once and reaching every connected platform at once — scenes, overlays, and the destinations that receive the signal.
Stream is the multistream cockpit for going live once and reaching every platform at once. A creator points one encoder — a phone app, OBS, or just the browser camera — at a single address; Stream receives that one feed, lets the creator build a composed on-air picture (inset cameras, crops, captions, a live viewer count, even landing-page promo content baked into the frame), and fans it out byte-for-byte to every connected platform: OnlyFans Live, Chaturbate, Stripchat, CAM4, BongaCams, Twitch, Kick, TikTok, Instagram Live, Telegram. Every platform's chat merges into one feed the creator watches from the panel or a private second-screen overlay, and where a platform has an automation surface (Chaturbate's official API, or a captured browser session for the webcam sites), Stream can also send welcome and timer messages and reply as the creator. If your team's day involves going on air, building the on-screen frame, or reading merged chat from more than one platform, you're in the right product.
What you can do in Stream
- Go live once, reach every platform. One RTMP/WHIP address in, byte-for-byte fan-out to as many platforms as are armed — the cost of composing the frame is paid once, not once per platform.
- Build the on-air picture. A scene is an ordered list of layers — camera insets, cropped sources, images, looping video, a live caption/timer, a live viewer count, and even landing-page promo content — composed in real time or copied through untouched when the scene is empty.
- Watch every platform's chat in one place. A merged feed across every connected platform, viewable in the panel or on a private second-screen overlay device.
- Automate what each platform allows. Welcome and timer messages, and replying as the creator, for platforms with an automation surface — Chaturbate's official Events API today, and the webcam sites once a captured browser session is live.
- Record what came in. Start and stop a recording of the incoming signal, and list or delete recordings on the receiving box.
One feed, many platforms — and one bill
The receiving box treats every encoder identically: RTMP or WHIP in, one address, one key. What happens next is decided by the scene, not by how many platforms are armed. An empty scene (the default) is a byte-for-byte copy — no re-encoding cost no matter how many platforms receive it. The moment a scene does anything (an inset, a crop, a caption), the frame is composed once on the server and fanned out as that same copy to every armed platform — five platforms cost the same as one. A platform scene (an override layered on top, just for one platform) is the one case that re-encodes per platform, and only for the platform it's set on.
Signal and on-air are two different states
Receiving a feed and broadcasting it to platforms are deliberately separate: the panel shows signal the moment a feed arrives, and only shows on-air once the cockpit's "go live" action has fanned it out. A creator can fix their light, angle, or caption after signal arrives and before anyone but them sees it.
What's next
Who needs it — the roles Stream is built for, and what each one can actually do here.