Bespoke software for theatre & live events. Built by a small technical team.
Greyframe writes show control, cue logic, scheduling, and ops software for productions that need something the off-the-shelf stack can't do. Typed APIs, versioned schemas, runbooks committed to the repo.
Software written for the show, not the deck.
- 01
CueCtrl.
Deterministic cue execution across lighting, sound, projection. One writer, one event log, replayable bit-for-bit.
- 02
Cuelist.dev
Nested cue stacks, conditional branches, fallbacks, dress-run replay. The runtime your stage manager actually trusts.
- 03
Ops & scheduling.
The systems the SM and producer actually use — call sheets, fixture schedules, on-call rotation, run reports.
- 04
Ticketing & front-of-house.
Custom flows when the venue’s system can’t handle the show. Holds, comps, walk-ups, exchanges, on-the-door.
We write what your productions needs. Nothing more.
Four principles. The rest is taste.
- 01
Self-hosted by default.
We ship the infra plan with the code. Bespoke software requires control.
- 02
Typed APIs. Versioned schemas.
Every contract is in the repo. Breaking changes go to a new version; deprecations live one full season.
- 03
Runbooks committed.
Documentation is a tagged release. If it isn’t in the repo, it doesn’t exist.
- 04
Replay-deterministic.
Single-writer engine. Every action can be replayed bit-for-bit from the event log.
2026-05-07T19:32:01.045Z INFO show.start preset=main-stage 2026-05-07T19:32:01.072Z CUE cue.fire q=001 ms=+27 2026-05-07T19:32:11.840Z CUE cue.fire q=002 ms=+10768 2026-05-07T22:08:14.001Z OK show.replay.match hash=4f8a92
Andreas Braa.
Greyframe started in 2017 building unique solutions to large. Most of the work has stayed close to that original brief — bespoke systems for productions that need something specific, written by someone who reads the score.
Before Greyframe, I spent years writing and maintaining systems and software at the boring, deterministic end of the industry — netowrking, telemetry, deployment infrastructure. Theatre is a system with a hard deadline of 19:30, no failover, and a live audience. The constraints sharpen the work.
Engagements run from one-week consults to season-long builds. The shop is small on purpose.
If your show needs something the stack can't do, write.