Tickets to teardown — running a music festival on one operations stack

A multi-day music festival is a small city assembled and disassembled twice a year — tickets, artists, stages, transport, lodging, food, registrations, and through the pandemic years, contact-tracing records on top of all of it. The festival team used to coordinate the whole thing across spreadsheets, shared inboxes, and group chats. Every year more events, more artists, more attendees, and more places where the spreadsheets quietly disagreed.

What we built

One operations stack covering every moving part of the festival. Tickets sell from the public site and land in the database with the attendee profile attached. Artist gigs are scheduled with stage, slot, and prep dependencies tracked. Crew timesheets, transport bookings, and lodging assignments all hang off the same artist and event records. Workshop and event registrations open and close from one dashboard. During the pandemic years, contact-tracing records integrated cleanly without bolting on a separate system.

How we built it

A Next.js dashboard on Vercel, Supabase as the source of truth for tickets, artists, gigs, crew, transport, lodging, and registrations. n8n runs the workflows — confirmations, schedule changes, transport pickups, lodging check-ins, registration waitlists. Stripe handles ticketing and merch payments. The on-site staff sees the same data on their phones the office sees on their dashboards.

The outcome

A festival that scales without a proportional pile of admin. The team coordinates more artists, more events, and more attendees from one shared view, and the public-facing experience stays smooth even as the operation behind it gets bigger every year.