Watched, not just installed
Most interactive installations are looked after by people whose job is something else: a curator, a front-of-house manager, a facilities team. When an exhibit freezes at two in the afternoon, the question is not whether someone could fix it but whether anyone notices before a visitor does.
An installation that works at opening and one that still works in year twelve can run the same software. The difference is whether that software is watched. Galaxy puts a technician’s checklist on every computer and runs it all day, watching the program as closely as the machine.
What it does on each computer
- Watches the application. Whether the exhibit is running, responding and logging cleanly. Exhibits built in Unreal Engine, TouchDesigner, Unity or JavaScript report their own state to the client.
- Watches the machine and the screens. Processor, graphics, memory and disk, and whether each display is set up as it should be. In a public gallery, a screen at the wrong resolution is a failure the same as a crash.
- Recovers on its own. A crashed application is restarted, and one that freezes is caught when its heartbeat stops and restarted too. Every restart is recorded, so the default outcome is a running exhibit, not a dark screen waiting for someone to notice.
- Reaches the devices around it. Displays, LED processors, players, media servers, audio and power are spoken to in their own protocols from the computer beside them.
- Updates without risk to opening hours. Every update is backed up first and can be undone in one step, and new content can reach a running application live, without a reinstall.
- Reports up. Health, logs and events flow to Galaxy’s dashboard, where staff see every installation at once and can restart or update any of them, and to its MCP server, where an AI assistant can ask what went wrong. Every restart, failure and update lands in the record Galaxy reports from, so the monthly uptime figure is the building’s own log.
Built in any engine, by any team
The client works with an exhibit as it was built, whichever studio made it and whatever engine it runs on. Applications report through Photon, take control and new content through Electron, Galaxy’s control protocol, or speak MCP, in any language. More on how Galaxy connects →
What it answers
How to restart a crashed or frozen Unreal Engine, TouchDesigner, Unity or browser-based exhibit automatically. How to monitor an unattended museum installation, kiosk or visitor-center display with no technician on site. How to update an exhibit computer safely during opening hours. Each is handled by the client on that computer and visible on Galaxy’s dashboard.
Where it runs
It runs on Windows and Linux. It’s how a nine-week exhibition ran daily with no technical staff on site, and the same client sits beneath installations designed for a 12+ year operational life.