Use cases

Who the pipeline is built for

Four creator profiles, four ways the same automation pays off. The pipeline configures itself per streamer โ€” layout mode, language, thresholds, destination platforms โ€” so each profile gets the right defaults without manual tuning.

๐ŸŽฎ

Gaming streamers with a corner webcam

Layout: gameplay-only

You stream a game (FPS, MOBA, RPG, sim โ€” doesn't matter) with your webcam tucked into a corner of the layout. Most viral moments are gameplay reactions: a clutch kill, a map disaster, a punchline you delivered while the boss was loading. The viewer needs to see what's happening on the game screen, not your face zoom.

The pipeline center-crops the 16:9 source to 9:16 around the gameplay area, keeps the webcam visible inside the crop where it already was, and lets the karaoke subtitles carry the verbal punchline. The corner webcam stays in-frame because the crop is centered on the gameplay action, not the webcam region.

๐Ÿ’ฌ

Just-chatting / talk-show hosts

Layout: webcam-only

You stream into a chat โ€” opinions, news takes, story-time, debate. The webcam panel is the entire show. Gameplay is irrelevant; the moment is whatever you said when the camera was on your face.

The pipeline takes the largest possible 9:16 window centered on your face inside the webcam region. You set the face center once in the dashboard (normalized x, y, w, h coordinates), and every clip from then on uses those coordinates so your face stays vertically centered, never drifting to the top or bottom of the rendered output.

๐ŸŒ†

IRL streamers with both camera & gameplay/feed

Layout: webcam top-split

You're streaming a co-op session, a co-watch, or an IRL setup where the viewer needs to see both your face and the secondary feed (game, video, second cam, browser). A single 9:16 crop won't fit both โ€” you need a stack.

The pipeline puts the webcam panel on top (40% / 768px) with a face-zoom step that crops the panel toward your face, and the second feed on the bottom (60% / 1152px) cropped to fit. vstack in ffmpeg merges them in one render pass, so the karaoke subtitles still land at the right vertical position.

๐ŸŒ

Cross-platform creators

Multiple destinations ยท OAuth-only

You already publish to TikTok, YouTube Shorts, and Instagram Reels manually โ€” but you only have time for one platform a day. Half the audience you could reach never sees the clip because by the time you'd edited and uploaded it, you'd moved on to the next stream.

The pipeline solves the bottleneck on the rendering and publishing side. Each clip is cross-posted to all connected platforms in parallel, with platform-specific caption length, hashtag style, and privacy defaults. Quotas and rate limits are tracked per platform, so when one is throttled the others still go through. You stay in control: every integration uses an OAuth token tied to your own account, and you can revoke access from each platform's "manage connected apps" page at any time.

A note on what's not a use case

The pipeline is strictly first-party only. It does not โ€” and never will โ€” clip third-party Twitch streams, copyrighted broadcasts, or content the user does not have rights to redistribute. The OAuth boundary on every connected platform locks publishing to the same creator account that owns the source.

If you're looking for a tool to scrape someone else's stream and republish it, this is not that tool. The full first-party rule is in the terms of service (section 3).

One of these your setup?

Take a look at the changelog to see what shipped recently, or get in touch.

Read the changelog Contact support