Who it's for
Teams that run live video and audio without a software department of their own.
- Small production companies
- Venues and event spaces
- Houses of worship
- Schools and universities with AV teams
- Local TV and radio
- Streaming operations
If your crew is working around a gap with a spreadsheet, a whiteboard or a script someone wrote years ago, that's usually where an app belongs.
Things we can build
Every project is custom, so this is a starting point rather than a menu.
One screen that shows what's on air, what's healthy and what needs attention.
Custom layouts, labels and tally for the wall, the gallery or a browser.
Simple, labelled buttons for the routes your operators use every day.
Rundowns, timers and schedules that stay in step with what's actually happening.
Who's on, what's booked out, and where the spare batteries went.
Check the stream, the signals or the room from anywhere, with alerts when something drops.
They can run on iPhone, Android, the web, or a screen on the wall, and talk to the equipment and software you already have.
Why us
One of us has spent twenty-plus years in broadcast and IT systems engineering. The other has 25 years of iOS and mainstream software development. You won't need to explain what a multiviewer is, or why a dropped frame matters.
We're at home with SDI, IP video and SMPTE ST 2110, NMOS discovery and connection management, and PTP timing. That means we can talk to your engineers in their terms, and build tools that fit the systems you run rather than fighting them.
Atoll: an ST 2110 and NMOS rig we built ourselves
Atoll is a broadcast-grade IP video system built on the SMPTE ST 2110 and NMOS standards. It's open source, so you can read every line of it.
- IP video senders and receivers, timed by PTP
- A multiview wall and control panel
- Live TV ingest via HDHomeRun, with automatic discovery
- Make-before-break source switching, and multiple codecs
How it works and what it costs
The same fixed-price packages as every ClarityIP project. You see a working prototype before you commit to the build.
One week. A clickable prototype, a written scope and a fixed quote. Credited in full toward a Launch Build.
Four to six weeks. A weekly build you can test, two rounds of revisions, and 30 days of post-launch fixes.
Updates, monitoring and crash alerts, and up to 3 hours of small changes each month.
Want a rough number first? Try the one-minute cost estimator, or see the full package details.
Got a tool your crew keeps wishing for?
Tell us what you need. We reply within one business day.