Fuse speaks your venue's languages.
A game show is more than a screen: it's lights that change when an answer lands, audio that hits on the reveal, a lamp on the winning podium. Fuse coordinates all of it through open protocols — no proprietary hardware lock-in.
Fuse runs its own authenticated MQTT broker on the venue LAN. Podium buttons, switches, lamps and custom props connect as capability-based devices — define once, bind to any game.
Light states are cues. Blackouts, chases and reveals fire over Art-Net and sACN with the moment they belong to.
Doors, drop-boxes, motors, sensors. Modbus TCP puts the set on the same cue stack as the sound and the lights.
Fuse reads the QLC+ function inventory and fires functions as typed cue actions, so an existing rig keeps its programming.
Lights, groups, scenes, effects and fades — house lighting joins the show without a lighting desk.
OSC, Raspberry Pi GPIO and Node-RED integrations are planned. The device model is protocol-neutral by design.
Scenes keep everything in step
Connections don't fire on their own — cues fire them. One press can change the DMX state, start the sting and reveal the answer on the board, because a single runtime owns the timeline. That's the difference between show control and a folder of apps. See how Fuse works for the whole picture.
Hardware, today and later
Today Fuse targets standard, openly available hardware over the protocols above. Curated hardware kits — podium buttons, lamps, wiring — may follow after public release.
Platforms
Fuse runs on Windows or Mac, on one machine at the venue, serving displays over the local network.
Get Fuse before public release.
Fuse is running at a small number of venues today. Public release is expected winter 2026.