Side by side
| Cloud-only check-in | Offline-first (EventAxis) | |
|---|---|---|
| Where passes are validated | On a remote server | On the device |
| When the network drops | Scans slow down or stop | Scanning continues at normal speed |
| Badge printing offline | Usually blocked | Continues from local data |
| What staff see | Errors or a spinning screen | "Working offline" and a pending count |
| After reconnecting | Retry failed scans by hand | Queued check-ins sync automatically |
| Data freshness | Always live when online | Live when online, refreshed on reconnect |
What the difference means on event day
A cloud-only kiosk asks a server whether each pass is valid before printing. That works well on a strong connection. When hundreds of phones join the venue network at doors open, each request takes longer, and the queue slows down.
An offline-first kiosk holds the attendee list on the device. It validates and prints locally, marks each check-in as pending, and uploads them in order when the connection is back.
The offline-first check-in playbook
Kiosk ratios, a venue connectivity checklist and a staffing plan for the first 90 minutes.
Common questions
Is offline-first less accurate?
No. Each check-in is time-stamped on the device and synced in order. Duplicate scans from two kiosks are resolved on sync.
What if someone registers after the list downloaded?
Lists refresh whenever a connection is available, and staff can add late registrations at the desk.
Can we test it?
Yes. In every EventAxis demo, we disconnect the network and keep scanning.
Test it on
your own event.
A 30-minute demo on your event's numbers. We'll cut the WiFi live and let the kiosks keep printing.