Streamtools is the platform behind a small family of live shows. Hosts run episodes here. Guests join through it. Viewers watch their pages move in lockstep with the host as the show unfolds. Read the room from one screen; broadcast from another.
Streamtools is a live production platform for podcasts and panel shows. Every show on it works the same way: hosts run a live episode, guests join through invite links, and viewers watch a broadcast that follows the host in real time.
This install is the home of Hide & Speak and any other shows the operator has added. Each one stays editorially independent; the platform is the shared chrome underneath.
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 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.
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.
Think of the host as a tour guide pointing at exhibits. The platform's job is to make sure when the guide points at something, every visitor sees it — without the visitors having to do anything. The same page is the host's script, the guests' shared document, and the audience's broadcast. One source of truth, three audiences, zero context-switching.
Streamtools is being made available to a small number of partner shows. If you run a podcast or panel and want to take it live the same way, get in touch about pricing and timing.
Inquire about access