Event operations, end to end
Doors openat nine.Nobody waits.
EventOS runs registration, ticketing, QR check-in, attendance and analytics off one shared record — so the day runs on something better than a group chat and three spreadsheets.
Attendees never make an account. Your team keeps working when the venue wifi gives out.
0
accounts for attendees
They fill in a form and get a ticket by email. No password, no app, no portal to forget.
1
record for the whole event
Registration, the door and the reports read and write the same rows. Nothing to reconcile afterwards.
4
roles, scoped tightly
Owner, admin, staff and scanner. A volunteer on the door sees the door and nothing else.
Take the sign-up, send the ticket, move on
Each event gets its own hosted form. Capacity is checked at the moment someone submits, the ticket goes out by email straight away, and nobody has to create an account to attend.
- Capacity is enforced when the row is written, not when the page loads — two people cannot take the last seat.
- Attendees pick their sessions during sign-up, so the fill numbers are real from day one.
- Ticket types, prices and limits stay yours to change up to the moment doors open.
eventos.app/register/northlight-25
Register for the summit
The public form. One link, no login, works on a phone.
The queue is the one thing nobody forgives
Scan with the camera your team already has in their pocket. Type the reference when a badge is creased. Keep going when the building's wifi does not.
- Scans made offline queue on the device and replay in order the moment the connection returns.
- Every check-in is attributed to a named station, so a disputed entry has an answer.
- A second scan of the same ticket is refused and recorded, rather than quietly counted twice.
Checked in · 09:06
Amina Rahman
Full conference · TKT-8F41-22C9 · first scan
312 / 480
65% arrived
- Priya NandakumarFull conference09:02
- Tom OkaforDay pass09:04
- Lena FischerSpeakerNot yet
What a door volunteer sees. Nothing else is reachable from here.
The worst moment at any event is a queue that should not exist. Everything in here is built backwards from that moment.
Numbers early enough to act on them
Fill rates, arrival curves and revenue come straight off the live rows — not a report that rebuilds overnight. You can still move a workshop to a bigger room at half past eight.
- Per-session fill, so you learn which rooms are wrong while there is still time to change them.
- Arrival timing across the door, to staff the next event properly.
- CSV and PDF exports for the finance team, who will only ever open a spreadsheet.
Session fill
Northlight Design Summit
- Opening keynote442/480
- Research ops workshop58/60
- Facilitation workshop31/60
- Evening social186/320
Busiest ten minutes
08:50
Exports
CSV, PDF
Read from the same rows the door is writing to, as it writes them.
One deployment, however many organisations
Every event, ticket and attendee belongs to a workspace. Invite the people you need for the weekend, give them exactly the access the job requires, and take it back on Monday.
- Records are scoped per organisation, so two teams on the same install never see each other.
- Invitations go out by email and expire; nobody is sharing one login round the team.
- Permissions are checked on the server for every request, including the API.
Workspace roles
Owner
Everything, including workspace settings, billing details and who else gets in.
Admin
Builds and publishes events, sets ticket types, invites the rest of the team.
Staff
Reads registrations, works the door, exports the lists they need on the day.
Scanner
One screen: scan a ticket, get a yes or a no. Nothing else is reachable.
Enforced on the server, on every request — not hidden in the interface.
Four roles, deliberately few. Most people only need two of them.
Set it up this afternoon. Run the door on Saturday.
Make a workspace, build the event, publish the form, and work the day from the same place that reports on it afterwards.