TourOps and FestivalOps aren’t two apps. They’re one running system — same database, same backend, same login — presented two ways. GigOps is the account layer, the security, the data, the real-time engine. The trust layer everything stands on.
The difference between TourOps and FestivalOps is vocabulary, which modules are visible, and the accent color — not a fork. Switch the flavor and the same data wears a different face.
Everyone signs into the same system — they just land in the surface built for their job.
Companies, users, roles, billing posture, and org-wide security policy. The control plane for the whole tenant.
Where the work happens — budgets, advancing, settlement, the lineup grid, the site map. TourOps or FestivalOps, your flavor.
The crew-facing half: badge, timecard, schedule, travel, tickets, ride requests, and a guard scanner — on any phone, no app store.
Changes propagate live across every open screen — admin laptop, ops desk, and crew phone — with no refresh.
JWT auth, MFA (authenticator-app TOTP) with an org policy, and strict company isolation between tenants.
Owner, admin, manager, finance, legal, ops, coordinator, viewer — each sees exactly the surface they should.
Rider & flight parsing built in. Email, SMS, maps, flights, weather, and multi-currency are each optional — and degrade cleanly when off.
TourOps and FestivalOps — both powered by GigOps, both on one account.