Example builds
Systems we build.
Patterns from real production work. The mix changes by project; the logic stays consistent. Problem, system built, result — no inflated metrics.
Selected builds
Projects.
01 / 04
Who it is for
Built for teams with recurring technical work.
01
Creative studios
Teams producing interviews, documentaries, campaigns, podcasts, events, and internal content.
02
Production departments
Teams with rooms, gear, operators, and recurring workflows that need standardization.
03
Venues & event teams
Spaces that need reliable routing, control, playback, recording, and operator handoff.
04
Technical founders
People building internal tools around media, production, automation, or operations.
Technical stack
The tools change. The logic does not.
Control
- Q-SYS
- QLab
- Companion
- OSC
- MIDI
- TCP/IP
- Serial
- HTTP APIs
Video
- ATEM
- SDI / HDMI
- PTZ control
- Multiview
- ISO records
- Monitoring
Audio
- Dante
- Q-LAN
- USB audio
- Mix routing
- Intercom
- Playback
Post
- DaVinci Resolve
- Premiere
- Review workflows
- Proxy & archive
- Delivery specs
Tools
- Node.js
- React / Astro
- Python
- Data models
- Cloudflare
- LLM workflows
Not a logo wall — the working vocabulary. The protocols, platforms, and languages a Labs build actually moves through.