Features
Everything a door needs to work properly
No add-ons, no tiers. The following is inside the platform.
01Tickets and issuing
Tickets and issuing
What leaves your hands before anyone reaches the venue. A batch is the unit you work in, and it keeps its own history so a reprint is never mistaken for a second issue.
- Ticket batches per event, each with its own name and history
- Bulk ticket issuing in a single action
- Per-ticket price override, for the times you need an exception
- Server-side PDF export — the same output on every machine
- Thermal printing for a box office at the door
- Printed marking, so the same batch is never reprinted
02Door and control
Door and control
The part that has to work with cold hands in a doorway. Devices pair from a printed sheet, and access ends when the shift does.
- Scanner app for iOS and Android
- Device slots paired with a single-use QR
- Browser gates for staff with no app installed
- Assign devices per event
- Activate or deactivate every scanner at once
- Revoke a lost device without touching the others
- Printable device sheets carrying the pairing details
03Online sales
Online sales
Selling online without handing your customer relationship to a marketplace. The network can be the legal seller where that is how the money should flow.
- Public organiser page and a page per event
- Orders with customer-side lookup
- Card payments on the public event page
- Merchant-of-record model for the network
- Payment confirmation by webhook with polling as a fallback
04Ticket delivery
Ticket delivery
Getting the ticket to the person. Delivery runs through your own email and SMS accounts, so the sender is you and nothing routes through a third party you did not choose.
- Email through your own provider, whichever one you already pay for
- SMS through your own gateway
- Test the gateway before the first real event
- Delivery history per event
05Live and analytics
Live and analytics
What the production team stares at between 20:30 and 22:00, updating while the door is still running.
- Live check-in by gate and by ticket type
- Continuous data stream, no page refresh
- Public event dashboard for the production team
- Activity history per event
06Security and organisations
Security and organisations
The boring part that decides whether you can run other people’s events at all: isolation the server enforces, and a record of who did what.
- Per-organisation data isolation, enforced on the server
- Network hierarchy with sub-organisers
- Sign-in with JWT and rotated refresh tokens
- A list of active sessions you can sign out
- Rate limits on the critical paths
- A separate sign-in history
Bring us your next door.
Tell us the date, the room and how many people are coming through it. We will show you the same thing you just used, running against your own event.
Book a demoThirty minutes, and you can bring whoever works the door.