The Open-Source Stack That Gives Small Studios Big Production Control

# The Open-Source Stack That Gives Small Studios Big Production Control

Large broadcast networks run their shows on sophisticated control systems that cost hundreds of thousands of dollars. Stage timers synced to graphics. Rundowns that cascade across screens in the control room, the stage, and backstage. Every cue planned, every transition automated.

For most small studios, that infrastructure feels out of reach. But in 2026, two open-source and low-cost tools have quietly eliminated that gap: Ontime for rundown management and Bitfocus Buttons for smart production control. Together, they give a two-person crew the same operational backbone that used to require a full broadcast team.

The Problem: Running a Live Show Is a Memory Sport

Without proper tooling, live production is held together by spreadsheets, tribal knowledge, and whoever has the best memory in the room. The director knows the show order. The technical director knows the graphics queue. The stage manager knows when talent is ready. These mental models never fully sync.

When they don’t sync, you get dead air. You get missed cues. You get a presenter still mid-sentence when the countdown timer hits zero.

The solution isn’t hiring more people—it’s building shared visibility so everyone sees the same state at the same time.

Ontime: Your Free Stage Clock and Rundown Engine

Ontime is a free, open-source production timer that runs locally on any machine and serves its interface over the local network. Once it’s running, every device on the network—tablets, phones, monitors, the director’s laptop—can pull up a live production view.

What makes it powerful for E4-style productions:

The Rundown Editor lives at `/editor`. Your producer builds the show here: events with titles, durations, and notes. Add a delay when the speaker runs long. Insert a milestone (“Standby for break”). Reorder on the fly without breaking everything downstream.

Stage Views that actually work: The `/timer` view shows a big countdown for on-screen talent. The `/backstage` view keeps the green room informed. The `/cuesheet` gives the show caller a clean list of what’s coming. These run on any browser—no software to install on the display device.

Automation that connects to your stack: Ontime has lifecycle triggers (on start, on finish, every second, on update) that can fire OSC or HTTP calls. That means when event 4 starts, you can automatically trigger a lower-third in vMix, cue a graphic in your graphics engine, or log the start time to a spreadsheet. The rundown becomes the authoritative source of truth for the whole technical system.

Companion integration baked in: There’s a native Bitfocus Companion module, so your Stream Deck can control Ontime directly—advance cues, start/stop timers, send messages to talent displays.

For a tool that costs nothing, Ontime competes with dedicated production timer systems that charge thousands per seat.

Bitfocus Buttons: QLab-Style Cue Lists for Any Show

Bitfocus Companion (free) is widely used in broadcast studios for Stream Deck integration. Buttons is the commercial tier that adds production-grade capabilities worth understanding for E4’s two-studio setup.

The headline feature is Cue Lists—QLab-style sequential planning for live shows. Instead of pressing individual buttons and hoping you remember which one is next, you build a cue list before the show and advance through it step by step. Each cue can fire multiple actions simultaneously: start a timer, trigger a graphic, switch a camera, send an OSC message to Ontime.

This is transformative for recurring shows. Build the cue list once. Run it every week. The operator doesn’t need to remember the sequence—the tool holds the sequence.

Conditional Actions add intelligence. If the timer variable is under 60 seconds, show the warning light. If the current scene is “break,” disable the camera cut buttons. If the presenter clicks their clicker, advance both the slide deck and the Ontime cue. Logic that used to require a dedicated operator with tribal knowledge gets encoded into the button configuration.

Dynamic Connection Variables matter most in a multi-studio environment. One Stream Deck page can control Studio 1 or Studio 2 based on a variable—which room is active today. The operator doesn’t need different device configurations for different rooms. The routing adapts.

The Integrated Workflow

Put them together and you have a real production control stack:

1. Producer builds the rundown in Ontime the morning of the show
2. Buttons loads the pre-built cue list for that show type
3. Show starts: Operator advances through cue list on Stream Deck
4. Each cue advances Ontime, fires graphics, switches cameras
5. Stage talent watches the Ontime timer on their monitor
6. Green room sees Ontime backstage view on a wall display
7. Director sees the full rundown on their laptop
8. Everything stays synced because Ontime is the single clock

This is the kind of system that makes shows feel tight. Not because someone’s working harder—because information is flowing better.

What E4 Gets from This Stack

For a two-studio operation running multiple shows per week:

Consistent show execution regardless of which crew is on
Talent confidence from always having a visible countdown
Reduced director cognitive load from automated cue sequencing
Show templates that can be reused and refined over time
Zero per-seat licensing on Ontime (completely free)
Single-surface Buttons free tier works for simpler setups

The production quality ceiling for small studios used to be limited by the cost of infrastructure. That ceiling has been effectively removed. The floor is now about how well you use the tools—not whether you can afford them.

—