One engine, three editions. TourOps runs the road, FestivalOps runs the grounds, VenueOps runs the house — and because they share one database, a tour, a festival and a venue can share one show.
Touring, festival and venue 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.
GigOps is the platform underneath: the account layer, the database, the notifications, the integrations. TourOps, FestivalOps and VenueOps are the same running system dressed for three kinds of customer — the vocabulary, the accent color and the visible modules change; the engine does not.
| Dimension | TourOps | FestivalOps | VenueOps |
|---|---|---|---|
| Who it’s for | Touring acts, tour managers, production companies | Festivals, promoters, site and production ops | Venues, rooms, holds and bookings |
| Shape | One act, many cities | Many acts, one site, weeks of build | One building, many bookings |
| Structure | Tour → shows (stops) | Edition → days → stages → set-times | Venue → spaces → calendar → holds → events |
| Advancing | Per-venue, with AI parser | Per-artist, keyed to a set time | Tech pack fills it — entered once |
| Calendar | Routing & iCal feed | Build / event / strike day types | Hold ladder H1–H3, challenges, expiry, dark days |
| Ticket counts | Entered, or reported by the venue | Per performance, festival-wide | Venue reports onto the tour’s show |
| Settlement | Per-show | Per-artist + festival-wide | Two-party ledger, dual signatures, hash lock |
| Pricing | Paid per tour or per company | Paid per edition | Free core · Pro · Group |
Every company’s data is private to it. The booking is the only record two companies share, and each side reads a fixed projection of the other. Wifi passwords and house notes open only when the date is confirmed. Nothing else crosses the line.
A tour’s show matches a registered venue. The tour sends a request; the venue accepts by placing a hold.
A hold on the venue calendar is linked to a tour by the promoter’s GigOps email.
A tour searches open dates and requests a hold, which places it, creates the show and opens the booking.
A tour advances an off-platform venue by email. The venue clicks “Claim your venue” and arrives with its profile built and a confirmed booking linked.
Every tour, festival and venue account has these on day one, on the same day sheet, with the same crew portal underneath. The edition decides what shows on top.
Every person on the road, the site or the house gets a mobile web portal — no app store, no login dance. Their badge, their schedule, their travel, and a button to call a ride. Crew seats are free in every edition.
Drop in a rider, a venue’s reply, an existing tech pack or a flight confirmation and GigOps parses it into the right fields — advance lines, legs, set-times, stage and power specs. No copy-paste, no re-keying.
Changes propagate live across every open screen. No refresh, no “who has the latest version.”
Roles from owner to viewer, two-factor auth, and strict company isolation — the booking is the only record two companies ever share.
Rider and flight parsing turn unstructured paperwork into clean, structured records.
A production manager who works for a venue and freelances for a tour switches companies without a second account.
Tours and festivals pay for the engine. Venues get the core free, because a venue on GigOps pulls every tour it books onto GigOps. Talk to us about early access and design-partner terms.
We’re onboarding tours, festivals and venues weekly. Drop your email — we’ll reply the same week with a private demo of whichever edition fits.