Simulcast destinations

A destination is somewhere we forward your stream. Connect once, re-use across streams.

Adding a destination

/tools/cloud-streaming → Destinations → Add destination.

OAuth-supported (one click)

For the platforms we have OAuth integration with:

• YouTube — picks the channel + the live broadcast
• Twitch — picks the channel
• Kick — picks the channel

Click the platform, authorize Suzko, pick the channel + stream settings. Done.

Manual RTMP (everything else)

For platforms without OAuth (Facebook, X, others, custom RTMP endpoints):

• RTMP URL + Stream key from the platform
• Optional: friendly name
• Save

Most platforms expose RTMP creds in their streaming/broadcasting settings.

Per-stream destination selection

When you create a stream input, you pick which destinations it fans out to. Useful for streams that go to a subset (gaming stream to Twitch only; conference to YouTube only).

Change destinations mid-stream by toggling them on/off in the Live view.

YouTube live notes

• Scheduled vs auto-start: you can either schedule a stream in YouTube and have Suzko push to it, or use YouTube's "auto-start" feature so a stream is created on the fly when you start pushing.
• Stream key validity: YouTube stream keys are tied to a specific broadcast. Re-authorize Suzko if you want to use a new broadcast slot.

Twitch notes

• One stream per channel at a time (Twitch rule).
• Categories + titles set on Twitch side, not Suzko.

Facebook notes

• Manual RTMP only (no OAuth integration). Get the RTMP creds from Facebook's Creator Studio.
• Stream keys expire after each stream — get a fresh one per session unless you've enabled persistent keys.

X (Twitter) notes

• Manual RTMP. Stream key from X's media studio.
• 720p/30fps maximum bitrate as of writing (X-side limit).

Custom RTMP destinations

Anything that accepts RTMP can be a destination — your own server, a corporate CDN, another livestreaming service. Just supply the RTMP URL + key.