Ask the building.
Patch is on-prem AI for venue AV operations. It reads your signal-flow drawings, watches every device on the network, diagnoses faults with the evidence cited, and answers the phone. It works when the internet doesn’t.
A real number. Patch picks up.
The demo — live now
Two faults, root-caused and cited to the drawing sheet — one fix executing, one waiting for a human to approve. Open the live demo, pick your venue, and break something.
What it does
Your TDDs, schematics, signal-flow drawings, manuals, and runbooks. Patch builds its model of the venue from the documents you already have.
Every device on the network, no matter whose name is on it — Ross, Evertz, Daktronics, Q-SYS, Grass Valley, EVS, Sony, Biamp, Pixera, disguise.
Detection, evidence, root cause, plan — with the sheet number from your own drawings cited. Not a guess. Not a red tile on a dashboard.
Only what you whitelist. Everything else waits for a human: it texts the on-call, and one reply — Y — approves the fix. Every action is audited.
SMS, email, and webhooks into Slack, Teams, or ServiceNow. You hear about the fault before the fans do.
In chat, or on the phone. Ask what changed overnight. Ask what feeds the north videoboard. Ask how the building is.
The voice channel rides a cloud layer today; the brain answering you runs in the building.
Non-negotiables
It runs in the building
A box on your network, not a tenant in someone’s cloud. Air-gappable. Nothing leaves the building — including the logs.
Every answer is cited
Patch never invents an answer. When it isn’t sure, it says so and routes the question to a human instead of guessing.
No unguarded actions
It fixes what’s whitelisted. For anything else it asks first, and keeps the audit trail either way.
For vendors
Your product can ask the building anything.
Patch exposes its model of the venue as a REST API and MCP tools — device health, fault state, signal paths, guarded action requests. If you make gear or software for venues, Patch makes it look smarter.
get_device_health trace_signal_path get_incident request_action
# or plain REST
GET /api/devices/videoboard-north/health → 200, 14 ms, no internet required
See it live