Built for the long ones

Your subathon. Under control.

Timer, Twitch events, milestones and your crew. One place.

Less tab juggling. Fewer 3am disasters.

No cardYour Twitch stays yoursNo spreadsheet archaeology
LIVE CONTROL ROOM72-hour subathon
Twitch connected
Time remainingServer authoritative
18:42:16
Pause+5 minFix timer
Total subs1,248
Bits84.2K
Next milestone52 subs
Live event feedReceipts included
50 gifted subsCounted once. As they should be.
Milestone getting closeHot chip challenge · 52 to go
Timer fixed by producerChange logged. No mystery edits.
Twitch-connectedReplay-safe eventsServer-authoritative timerRole-based staff accessOBS ready

Six tools. One tired mod. Bad idea.

Twitch, OBS, a timer, a spreadsheet, Discord and a bot can work. Until something goes wrong and nobody knows which one is telling the truth.

The usual wayScattered state
TwitchOBSTimerSpreadsheetDiscordBot
  • Who changed the timer?
  • Did that gift batch count twice?
  • Which milestone are we actually on?
  • What happened while everyone was asleep?
The SubathonOS wayOne source of truth
One event.One control room.Timer · Twitch · Milestones · Team · OBS · Public page
  • Contributions land against the right event.
  • Timer changes stay in event history.
  • Staff get controlled access.
  • The stream and public page stay in sync.

The demo explains this better than another paragraph ever will.

Open it, click around and see what a live event actually feels like.

Open the demo

Stuff gets weird at 3am. The system should not.

Duplicate events, timer fixes, sleepy mods and crew changes happen. SubathonOS keeps a proper record so nobody has to rely on memory.

01

Replay-safe Twitch events

Duplicate delivery is deduplicated before it can change the event twice.

02

Server-authoritative timer

The timer lives on the server, not in one browser tab somebody forgot about.

03

Corrections with history

Fix a mistake without turning the rest of the night into a guessing game.

04

Controlled staff access

Give the crew what they need without handing over the creator's Twitch identity.

“Twitch sent that twice. Did we just add the time twice too?”

“Who fixed the timer at 3:42am?”

“Can the crew help without logging into my Twitch?”

Twitch comes in. SubathonOS works out what should happen.

One event record powers the timer, milestones, staff controls, OBS and public page. That is the bit that keeps everything sane.

One event from setup to “we actually survived that”.

Set it up properly, run it from one place and still know what happened when it is finally over.

01

Before

Set the rules, milestones, schedule, OBS, public page and crew access before chat starts causing problems.

Set rulesBuild milestonesConfigure OBSInvite the crew
02

Live

Run the timer, watch contributions and keep the whole team on the same page.

Run the timerProcess contributionsFix mistakesCoordinate staff
03

After

See what happened without reconstructing the night from Discord messages and half-updated spreadsheets.

Review activityCheck totalsAudit changesBuild the recap

One creator or a whole crew. Same event.

SubathonOS works whether you are doing everything yourself or have a team keeping the stream alive while you sleep.

Running it yourself

One place to operate the event without becoming a professional tab juggler.

Creator + mods

Let trusted people help without making the creator's Twitch account a shared login.

Production teams

Prep and run the event together with clear roles and one shared event state.

The properly long ones

When the stream runs for days, memory and vibes are not a reliable system.

Your Twitch account is not a team password.

The creator stays the Twitch ownerManagers and producers stay collaboratorsPublishing stays creator-controlledStaff actions stay auditable

Run the real thing for free.

The live operational core is not a teaser. Use it for the actual event. Supporting SubathonOS adds presentation, collaboration and recognition extras.

See the extrasCore event operation stays free

Make the chaos look organised.

One place for the event. Far fewer “who changed that?” messages.

Create your eventTry the demo