The app for a multi-stage festival
A festival is a programme problem wearing a production budget. Six stages, ninety acts, and an audience whose only question is what is on next and where.
A planning figure for a mid-sized regional festival. The field makes the point: everything past 1,000 activated attendees is free.
A programme problem wearing a production budget
A festival app carries the full programme across every stage, lets each attendee build their own line-up, and pushes an alert when a set time changes. event67 provides that under the festival's own brand, along with sponsor pages and a shared photo album. It does not sell tickets, scan gate entry at festival scale, or provide a site map, so it sits alongside a ticketing platform rather than replacing one.
Ninety acts and one person's evening
The whole festival programme is unusable as a single list. Filtered by stage and by day, with each attendee starring the sets they want so their own line-up pins to the top, it becomes the thing people open forty times a day. That personal agenda is the feature festival audiences actually use.
Set times that move, and an audience that has to know
An act is delayed, a stage closes for weather, a surprise guest is added. Push notifications deep-link to the affected set. On a site where signage cannot be changed and the public-address system reaches one field, this is the only channel that works.
Sponsors who paid for visibility
Tier-ordered sponsor pages with logos, descriptions and websites, and sponsors attached to specific stages or sets. For a festival this is a contractual deliverable and worth checking against the signed agreements.
A cost that does not scale with the crowd
Most festival software prices on attendance, which is exactly the wrong shape for an event whose audience is its risk. Here the per-event price stops at a thousand activated attendees. A festival of five thousand and a festival of fifty thousand pay the same.
Line-up announcement to load-out
Line-up announcement
Publish the programme
Stages as rooms, days as the schedule, acts as sessions with their times. Attendees browse before they buy, which is why publishing the programme early is worth more than any other single action.
Uses the programme.
After ticket sales
Invite the ticket holders
Tickets are sold in your ticketing platform, because event67 does not sell them. Export ticket holders, import as CSV, and send branded invites with delivery tracked per recipient.
Uses the branded app and branded invites with delivery tracking.
Gates open
The programme in every pocket
Attendees build their line-up on the way in. Wallet passes hold whatever pass you issue. Note the boundary: event67's check-in is a QR scan suited to a registration desk, not a high-throughput festival gate, so gate scanning stays with your ticketing operation.
Uses Wallet passes.
During
One channel that reaches the site
Set changes, weather calls, last entry warnings. Each as a push announcement that opens on the post. Scheduled announcements handle the ones you already know about, so the site team only writes the ones they did not expect.
Uses push announcements.
After
The album and the sponsor report
The shared album gathers the audience's photography with moderation. Engagement analytics tell you which stages actually held people, which is a better programming input than ticket scans and a genuinely useful number for next year's sponsors.
Uses the shared album and analytics.
Preparing a festival app
Five steps. The first one is a scope conversation with your ticketing and production teams.
Agree the boundary with ticketing and production
Tickets, gates, wristbands, cashless and maps stay with the systems that already do them. event67 owns the programme and the communications.
Create the event and build the stages
Each stage as a room, each day laid out in the schedule.
Load the line-up with real set times
Acts as sessions with artists as speakers. Attendees star their picks from here.
Load sponsors against the signed agreements
Tier order is commercially meaningful. Verify it.
Pre-write the announcements you can predict
Gates open, last entry, weather protocol, curfew. Schedule them; leave the console free for the ones you cannot predict.
What a 5,000-attendee festival costs
This is the clearest illustration of the ceiling on the whole site. Whether five thousand or fifty thousand attendees open the app, the per-event price is the same, because it stops moving at a thousand activated attendees.
- activated attendees
- 5,000activated attendees
- billable, after the first 50 are free
- 950billable, after the first 50 are free
- for the whole event, at $5.00 each
- $4,750for the whole event, at $5.00 each
For a festival, the app is one of very few line items that does not grow with the crowd.
What a festival needs that event67 does not have
This list is longer than most on this site, and a festival organiser should read all of it before committing.
- No ticketing, no box office, no payments and no wristband fulfilment.
- No site map, no interactive festival map and no wayfinding. For a large site this is a significant gap.
- No high-throughput gate scanning. Check-in is a desk-speed QR scan, not a turnstile system.
- No cashless payments, no vendor tokens and no bar top-ups.
- No artist or production scheduling, no stage plots and no crew rostering.
- No streaming.
- No gamification, no points and no scavenger hunts.
Last updated
What it costs
- Free up to 50
- activated attendees, on one live event
- $5
- per activated attendee beyond 50
- $4,750
- the most one event can ever cost, whatever happens past 1,000
Activated means the person claimed their invite and opened the app. Not when you import them, not when the invite is delivered, and not if they register and stay home.
Questions people actually ask
Can we sell tickets through the app?
No. There is no ticketing, no box office and no payments. Sell through your ticketing platform and import the ticket holders as CSV so they receive a branded invite.
Is there a site map?
No. There is no interactive map, site plan or wayfinding of any kind. For a large festival site this is a real gap and you should plan for printed maps or a separate mapping tool.
What does it cost for a festival of 30,000?
The same as one with 1,000 activated attendees. The per-event price stops rising there, so every attendee beyond that is free. For a festival this ceiling is usually the deciding fact.
Can we use it for gate entry?
Not at festival scale. Check-in is a QR scan designed for a registration desk, where a repeat scan returns already checked in rather than an error. A festival gate needs throughput and hardware that event67 does not provide.
Do attendees need to be online?
The app fetches the schedule and announcements over the network, so a site with no signal is a problem. Plan for it the way you would plan for any connected system on a field, and keep printed programme boards at the stages.
Keep reading
Other kinds of event
The features this leans on
Give every attendee their own line-up
The whole programme, personal picks, and a push when a set moves. The price stops at a thousand.