The same engine. Six very different rooms.
A club resident and a stage manager want opposite things from automation — one needs the show to follow music nobody planned, the other needs it to hit the same frame every night. CueSync does both, but the workflow, the edition, and the honest trade-offs differ. Pick the room you work in.
- Club residents & weekly nights
Club & Residency DJs
Lights that follow the beat phase and phrase map of whatever you actually mixed — not a timeline you programmed last week.
DJ EditionRead more - Touring circuits & brand tours
Touring DJs
One show file that survives a different rig, a different network, and a different house LD in every city.
DJ EditionRead more - Stage managers, LDs & TDs
Theatre Operators
Timeline automation and frame-accurate timecode for a cue stack that stops being re-typed after every script revision.
Theatre EditionRead more - Tech directors & volunteer teams
Auditoriums
Presentation graphics, lighting, audio, and IMAG on one cue — so one volunteer runs the booth instead of chasing three apps.
Theatre EditionRead more - Festival production teams
Festival Stages
One instance per stage, sharing fire context across the production network so the stages stop double-firing at each other.
Production EditionRead more - AV companies & brand activations
Event Production
One operator driving the whole fanout — lighting, video, timecode — instead of one specialist per protocol.
Production EditionRead more
Work in more than one of these?
Most operators do. Every edition ships every protocol integration — the tiers differ on workflow, not on what you can talk to. Compare them side by side, or download and explore the full interface in read-only mode first.