Streamtools is the platform that keeps remote hosts, co-hosts, panelists, guests, and producers in sync during live streams and recorded shows. One shared page that follows the host in real time. Every voice on the show, in the same place, at the same time -- across cities, countries, and time zones.
Before the show goes live, the host, the guests, and anyone with the link can see the same page. Mics get checked, intros get rehearsed, last-minute changes get made. Nothing is broadcasting yet.
Guests can send the host questions, topics, and notes ahead of time. The host sees them collected on the episode page and can fold any of them into the run order with a click.
When the show starts, the page becomes a broadcast. As the host -- or an off-air producer -- moves from one act to the next, every viewer's page smooth-scrolls with them, automatically. No clicking, no scrolling, no trying to find where the conversation is.
The host can edit the script while the show is live, drop in an intermission for an ad read or a breath, send a banner across the page, or quick-mark a great moment for the post-show timestamp file.
When the host ends the show, viewers stop auto-scrolling and the page settles. Anyone can scroll back through the script to find what they want.
The host gets a downloadable timestamp file of every moment they marked during the run — ready to hand to an editor for clip selection or to use as a chapter index on the published episode.
During a live show, every viewer's page is a mirror of where the host's attention is. When the host advances through the script, every viewer's page smooth-scrolls to the same spot, automatically. No clicking, no "wait, what page are we on?" -- the audience stays in lockstep with whatever's being talked about.
A live show isn't a recital -- the host marks questions off as they're asked, refines a line of script when something better comes to mind mid-conversation, glances at context notes on the right without ever reading them aloud. The page is a working surface, not a static document. Watch the checkboxes tick, the script get a small inline edit, and the show breathe in real time.
So let's set up the question. There are three reasonable answers, and each one comes with a serious tradeoff.
I want to come at this from the user's perspective firstthe user's view, then the regulatory frame, then we can talk about the engineering.
Three positions worth distinguishing: silicon-level, OS-level, operator-level. They're not mutually exclusive.
If guest brings up the regulatory angle, swing back to the consent-cost framing from last week.
Live shows have texture: ad reads, audio checks, "we'll come back to this in act four." The platform handles those moments without breaking the rhythm. A break drops in with a visible countdown, banners broadcast across the page, the host can drop a note for the audience without interrupting the conversation, and when the break ends -- or the host calls it early -- the next act starts automatically, scrolling everyone forward together.
Studios are bright, late-night reading is dim, some people like a clean cool palette, some want the page to feel like a book. The platform ships five themes that the host and every viewer can switch between independently. Watch the same episode page render in each, one after the other -- nothing about the content changes, only the light it's shown in.
There are three reasonable answers, and each one comes with a serious tradeoff. We'll look at silicon-level, OS-level, and operator-level positions in turn.
If you've ever wondered why the device in your pocket is doing math you didn't ask it to do, this is the place to start.
Good shows get sharper right up to the moment they start — and sometimes during. A question gets reworded. A hook reads better with one phrase swapped. The host turns on Edit mode and refines the script directly on the page, before the show or while it's running. Every guest, panelist, and viewer sees the change appear on their screen the instant it saves — no refresh, no "let me re-share the doc," no version drift. The same page is the script, the editor, and the running reading guide.
There are three reasonable answers, and each one comes with a serious tradeoff.
There are three reasonable answers, and each one comes with a serious tradeoff.
On a solo show the host drives everything. But assign a producer -- someone running the show from off-air -- and the roles split cleanly. The producer's progress becomes the broadcast: the guest and audience follow the producer, and only the producer. Meanwhile the host runs a step ahead, ticking through the script at their own pace, with progress that's private to their screen. Nobody bounces between two positions. One driver, one broadcast.
Every show runs on a live pace widget: the current act's clock, the whole show's running time against its plan, and a progress bar that shifts color as you go — green when you're on pace, red when an act runs long. When the show ends, that pacing data doesn't disappear. It becomes a report that feeds the next episode's brief, so the acts that always run long get re-timed before you're ever on air again.
Think of the show as having someone pointing at exhibits — the host, or a producer working alongside them. The platform's job is to make sure when they point at something, every visitor sees it — without the visitors having to do anything. The same page is the host's script, the producer's control surface, the guests' shared document, and the audience's broadcast. One source of truth, every role in sync, zero context-switching.
Streamtools is being made available to a small number of partner shows. If you run a live stream, a podcast with remote guests, a panel show, or any kind of multi-person production where the team isn't in the same room, get in touch about pricing and timing.
Inquire about access