Budgets, crew, advancing, settlement, credentials, and the show-day sheet — one command center for everyone on the road and everyone on the site. Two flavors, one platform.
Touring and festival ops run on 14 spreadsheets, three group chats, a shared Dropbox,
and a thread no one can find. GigOps replaces all of it with one command center.
A festival is just a tour whose stops are co-located in time and space. So both run on one engine — same database, same login, same real-time core. The difference is vocabulary, which modules are visible, and the accent color.
| Dimension | TourOps | FestivalOps |
|---|---|---|
| Shape | One act, many cities | Many acts, one site |
| Structure | Tour → shows (stops) | Edition → days → stages → set-times |
| Geography | Linear routing — drive-times central | Single site — map & zones central |
| Advancing | Per-venue | Per-artist — input list, stage plot, rider, set time |
| Credentials | Laminates & passes | RFID wristbands — day vs multi-day, per-zone |
| Box office | Will-call / guest list per show | Festival-wide gate scanning, multi-day passes |
| Weather | Nice-to-have | Mission-critical — wind holds, evac, outdoor stages |
| Settlement | Per-show with venue / promoter | Per-artist guarantees + festival-wide P&L |
Every role on the tour or the site gets the exact view they need — wired together by one financial model and one real-time core. ~80% of it is shared; the flavor decides what shows.
Every person on the road or the site gets a mobile web portal — no app store, no login dance. Their badge, their schedule, their travel, and a button to call a ride. The crew-facing half of the platform.
Drop in a rider or a flight confirmation and GigOps parses it into the right fields — advance lines, legs, set-times, ground transport. No copy-paste, no re-keying.
Changes propagate live across every open screen. No refresh, no “who has the latest version.”
JWT auth, granular roles, MFA, and strict company isolation. Built for many orgs on one platform.
Rider and flight parsing turn unstructured paperwork into clean, structured records.
~30 modules behind one login. Integrations are optional and degrade gracefully when off.
We’re finalizing plans built around how tours and festivals actually run — per show, not per seat. Talk to us about early access and design-partner terms.
We’re onboarding tours and festivals weekly. Drop your email — we’ll reply the same week with a private demo of whichever flavor fits.