A reasonable question from anyone evaluating Showcaller — the AI co-pilot for live production — for a real show: is this just an API wrapper running somewhere in the cloud, hoping the network cooperates? No — and the reason is the Bridge App.
What the Bridge App actually does
It runs on your show network, not in the cloud. The Bridge App is a small piece of software you install on a machine that’s already on the same network as your gear. It’s the thing that actually captures your voice and executes commands against your hardware directly — over the protocols your devices already speak (HTTP, OSC, UDP, TCP, whatever a given device uses). Showcaller’s cloud backend handles the AI side of the conversation; the Bridge App handles the part that touches your rack.
Why local execution matters. Two reasons, both practical. First, latency: a command that has to round-trip through a distant server before reaching your switcher is slower than one that doesn’t. Second, and more important: your show network doesn’t need to expose your gear to the open internet for any of this to work. The Bridge App talks to your devices locally; only the conversation with the AI goes out.
Pairing is deliberately simple. Connecting a Bridge App to a show is a short-lived code, entered once, that establishes the link. No static credentials sitting around, no manual network exposure to configure.
What this means in practice. When Showcaller tells you a command was confirmed, that confirmation came from your actual hardware, reported back through a connection that never left your own network until it needed to talk to the AI. That’s also the foundation everything else — Pulse’s awareness, Tally’s verification, Air Check’s record — is built on. None of it is guesswork about what should be happening on your gear. It’s built on a direct line to what’s actually happening.
If you’re the kind of person who wants to know how a tool works before you trust it near a live show, that’s the honest answer.