Part 1: A result you can read at arm's length
A gate at a festival is loud, bright or dark, and always moving. Accepted or refused fills the screen instead of whispering in a corner of it.
For festivals
Day tickets, weekend passes, camping, parking, and four gates that all need to scan at once.
Verimly handles a festival as one event with several ticket types — day tickets, weekend passes, tiered releases — plus add-ons for camping, parking and merchandise sold in the same checkout. On site, any number of paired phones scan QR tickets at any number of gates, all against the same live availability, with no per-device charge.
The numbers on the screen above mark the parts that do the work. Here is what each one is.
A gate at a festival is loud, bright or dark, and always moving. Accepted or refused fills the screen instead of whispering in a corner of it.
Day ticket, weekend pass, crew. The type comes back with the scan, so the person on the gate knows whether this wristband is for today or for three days.
A ticket scanned at the north gate is already used when it reaches the east gate a minute later. All devices read and write the same truth.
Groups arrive together and one code is always wrong. Seeing the last few scans turns an argument into a question with an answer.
Pair a phone per lane. There is no per-device charge, so a fifth lane on Saturday costs nothing to open.
Tier one, tier two, tier three: each is a ticket type with its own quantity and its own window. When one sells out the next takes over. Buyers see what is actually available rather than a list of things they cannot have, and the price rise happens on schedule rather than when someone remembers.
Add-ons appear in the ticket flow, so somebody buying a weekend pass adds a camping pitch and a parking space without a second checkout, a second confirmation email or a second reconciliation for you. Each add-on carries its own stock, so a field that holds four hundred pitches stops selling at four hundred.
Pair as many devices as you have entrances, and group them by location so a multi-gate site stays legible. They all read and write the same availability, which is what makes a scanned ticket useless at the next gate.
Sales, check-ins and door takings arrive on the same dashboard as they happen. You can see how many people are actually inside rather than how many tickets were sold, which is a different number and the one that matters on site.
What you actually do, in order, the first time.
Day tickets and weekend passes as separate types, each with its release window.
Add-ons with their own stock, bought in the same order as the ticket.
Group them by gate, and give the crew PINs rather than accounts.
Every lane scans against the same availability, all weekend.
| Ticket types | Day tickets, weekend passes, tiered releases |
|---|---|
| Add-ons | Camping, parking, merchandise, in the same order |
| Releases | Each tier opens and closes on its own schedule |
| Gates | Unlimited paired devices scanning simultaneously |
| Locations | POS devices grouped by gate or bar |
| Duplicates | Caught on the second scan, at the gate |
| Crew | Personnel sign in with PINs; no workspace account needed |
| Live view | Sales and check-ins streaming to one dashboard |
Yes. They are separate ticket types on the same event, each with its own price, quantity and sales window.
As many as you pair. There is no per-device charge and no limit imposed on the number of gates.
Add-ons are bought alongside tickets in the same order. A camping-only purchase would be modelled as its own ticket type instead.
No. Event-night personnel sign in to a paired device with a PIN, which is faster at a gate and does not give a weekend volunteer access to the business.
Check-ins arrive live on the dashboard, so you can see admissions rather than only sales.
Unpair it from workspace settings. It stops being able to sell or scan immediately, and nobody else has to change anything.
Get started
No subscription, no setup fee, nothing to cancel. Build the whole thing, and decide at the end whether to publish it.