StreamLine
Set your schedule once. It shows up everywhere your community already is.
01 / The problem
Most streamers keep their schedule alive by hand, in three or four places at once — a pinned Discord message, a Twitch panel, a tweet, maybe a calendar link buried in a bio. Each one has to be edited separately every time something changes. In practice, something always changes: a stream gets pushed a day, a guest cancels, a time slot moves because of a day job.
The failure mode isn't dramatic — nobody's schedule vanishes. It's quieter than that. One surface gets updated and the other two don't, so a viewer shows up for a stream that already moved. It doesn't take many of those moments before a community stops trusting the schedule altogether and just waits to be told directly.
02 / The approach
StreamLine treats the schedule as a single object, not four separate announcements.
The core flow works the same way every time:
- You enter the week's stream schedule.
- It populates a visual preview so you can see exactly what your audience will see.
- You approve it.
- StreamLine renders that preview into a shareable image.
- The image is emailed to whatever addresses you've specified — yourself, a mod team, whoever needs it.
That email step is the one constant. Everything else is optional and stacks on top of it.
On top of that core flow, three integrations can be switched on independently:
- Discord — the generated schedule image is posted to a channel via webhook.
- Discord events — an event is created in discord automatically at each stream's scheduled time.
- Twitch — the schedule is pushed directly into your native Twitch schedule via the Twitch API.
Each one is a toggle, not a package deal. Turn on just Discord, just Twitch, all three, or none — the core "enter schedule, get an email" flow doesn't care which integrations are active.
A design choice worth calling out explicitly: integrations are additive, never load-bearing. If your Discord webhook is misconfigured, or Twitch's API times out, or an integration simply isn't turned on, that does not stop the email from going out. The email path is treated as the one thing that always has to work; everything else is allowed to fail in isolation without taking the core flow down with it. Credentials for each integration — your Discord webhook URL, your Twitch authorization, and so on — are stored per account, scoped to that account, and used only for that integration's own API call, so a problem with one connection stays contained to that connection.
03 / Under the hood
StreamLine is built on Next.js with Supabase/Postgres as the database layer. The schedule-to-image step uses html-to-image to render the visual preview into a shareable graphic. Discord delivery runs over standard webhooks, Twitch sync runs through the Twitch API, and email delivery runs over SMTP.
A YouTube integration — posting the generated schedule as a Community Post — is in active development. It isn't production-ready yet, so it isn't part of the current toggle set.
04 / Where things stand
StreamLine has been through extensive internal testing across the core flow and each integration. We're targeting a launch by the end of August 2026.