The day-of problems, handled.
Lineup and set times
Stages, artists and times, with favourites and reminders. Change a set time once and it changes everywhere.
Vendors people can find
Every truck and booth has a profile with a menu, and search knows which ones are vegan, gluten-free or open late.
Announcements that land
Gate changes, weather holds and a headliner running late reach every open guide.
The map that matches the site plan
Import the site plan as GeoJSON, CSV or KML. Draw what's missing. Preview on a phone at the gate.
Sponsor stages and activations
A 'Presented by' on the stage pin, a sponsored offer, a QR wall. All measured.
Vendor and sponsor recaps
Profile views, menu taps and route requests per vendor. Impressions and redemptions per sponsor.
Set times that update themselves.
When the schedule slips, your team edits one entry and publishes. The stage page, the attendee's saved list and the reminder all follow. No reprinting, no 'check our story for updates'.
- Artist pages with set times and stage
- Favourites and reminders
- One edit, every surface
A storefront, not a dot.
Vendors get a profile with their menu, hours, links and offers. Attendees search by craving, not by booth number. Vendors see what the fee bought them after the event.
- Bulk import from the vendor spreadsheet
- Search by dietary need or category
- Recap report per vendor
Questions festival teams ask.
How fast can we be live?
If you have a site plan and a vendor list, the first version of the map usually takes a working session. Polish and branding come after.
Does it work on a muddy field with no signal?
The guide installs on first visit and keeps the map and schedule available when the connection drops.
Multi-day and multi-site?
Yes. Days, stages and sites are separate activations under one event and one link.
Can we use our own domain?
Yes. A custom public URL carries the event's brand.