Ops Tools & CMS
Built by someone who has worked the gate.
The CMS is organised the way a festival is run: Live, Content, Promotion, People, Analytics, Admin. Staff get an Ops tab on their own phones for the things that happen standing up. Every write says who did it.
Why it works
Six groups, no eleventh heading
Live status and broadcast at the top, then the content, the sponsors and popups, the people and reports, the analytics, the admin. A new page has to fit one of those six, so the sidebar never sprawls.
Roles that match your org chart
Director, ops, marketing, sponsor sales, moderator. Each permission is a checkbox. A moderator can close a report and cannot send a push. Every change lands in the audit log with a name and a time.
Ops on a phone
Grant an operator the Ops tab in the CMS and their app grows a section: live status, broadcast, lost and found, visibility. Nothing to install and nothing for an attendee to find.
What you can expect
What ships,
screen by screen.
Content editing that is live in 30 seconds
Artists, stages, set times, vendors, FAQ, map pins, quick actions, news, sponsors. Bulk edit set times. Import a spreadsheet. Changes are cached three deep and reach phones in about half a minute.
Visibility switches
Lineup, schedule, afterparty, vendors, map. Each is a switch that is off until you say so, enforced on the server. Flip it from the Ops tab on your phone at the lineup drop.
App update gate
Ask phones to update, or require it, from the CMS. A forced update always has a way past it, because a wall nobody can dismiss is how you brick a phone with no bars.
Backups and a health check
Nightly database backups, a health endpoint your monitor can watch, and a server load widget on the dashboard. Hosted for you, or handed over to self-host on Pro.
Included
On every plan, from Core up.
Works with
Ready to put your festival
in every pocket?
- No development team on your side
- Content in hand to the store in about six weeks
- You own the app, the data and the sponsor revenue