Building a Custom Broadcast Intercom
Updated: Jul 27

For our rowing broadcasts, where crew members can be spread out over a mile and a half, we've traditionally relied on Discord with a single partyline. I wanted to build something with features like point-to-point communication, IFBs, partylines, program return audio, crosspoint monitoring, audio bridges, and external control. I've been developing it using Claude Code and VS Code, which has been a great way to rapidly prototype and iterate on ideas. I still have some work to do on the cloud deployment side, but I currently have it running successfully across LAN and VPN environments.
It's a React + Vite + Tailwind frontend, a Node/Express + Postgres API, and a self-hosted LiveKit SFU carrying the audio. Audio goes browser to SFU over WebRTC and never touches the API server, while control (assignments, remote control, crosspoints) rides a Server-Sent Events push channel, so an API restart never drops live audio.
Operator Panel

Push-to-talk or latch talk
Partyline, IFB, and point-to-point tiles
Per-channel volume + listen with a dim feature
Point-to-point that appears when called if not already on panel
Talk indicator both ways
Optional video monitor with program return via MistServer
Admin — Manage

Create/deactivate users, reset passwords, and assign partyline/IFB/P2P channels
Manage can-talk, listen-only, talk mode (PTT vs latch), and position
Copy one operator's panel onto many by merge/replace
Admin — Remote Control

Control an operator's panel live, including master listen/volume, dim, and per-channel talk/listen/volume/dim
Shows online/offline status
Admin — Crosspoints
A live "who's talking to whom" matrix

Real-time state
Four states per cell: Talking (red mic), listening (green headphones), present but muted (amber), offline with a corner badge showing configured capability (mic / slashed-mic)
Separate matrices per channel type
Hardware bridge endpoints appear as extra columns ▲ sending into the channel, ▼ receiving it out so a Dante program feed or a talent earpiece.
Hardware Audio Bridge
A standalone app that joins a channel as a normal participant, so external audio sources can talk.

Options include tone (proves the path with no hardware), device (USB dock mic / headset / Dante Virtual Sound Card* untested), and aes67 (Dante-in-AES67-mode RTP L24 multicast* untested)
Add a return to a source and it becomes a real intercom endpoint
Revocable bridge keys
Admin — Bridge Routing Matrix

Dante-style crosspoints with ows/cols of each online bridge's devices × channels; click a cell to route
Independent routing so send and receive are separate routes, so one box can send its mic to PL A while monitoring IFB 1 simultaneously
Live indicators
External Control — Stream Deck & Bitfocus Companion


A token-authed HTTP API plus a real Companion module to key mics, toggle listen, set volume, and drive master/dim from physical buttons.
Two credential types with an operator generates a personal token from their own panel to control their own (no admin involved), or an admin creates a control key to drive any operator (director surface).
Live feedback by color indication
Revocable access
Mobile & iOS Challenges
iOS suspends WebRTC playback the moment Safari backgrounds or the screen locks, except for a media element in PiP. Raw WebRTC tracks are cloned straight into a PiP video element, bypassing the Web Audio graph (which freezes when backgrounded)
Mobile mics require HTTPS, necessitating a local certificate installed for LAN testing
Program return is too delayed currently
What's Not Done Yet
Cloud/AWS deployment with monitoring
Audio synchronization with AES67 against real Dante hardware
Native mobile packaging, VU meters, keyboard PTT, and priority overrides
LiveKit currently runs single-node dev mode





