Product
We don't sell turnstiles; we make the data they produce useful.
The panel at the gate creates a record for every pass. In most schools that record sits in a file and goes unused. This page explains the steps it goes through from the gate to the screen.
Flow diagram
The outcome appears in four places: the live presence list, parent notifications, the attendance record and the emergency list.
Three ways to connect
The panel sends events itself
The panel sends us an event for every pass. This gives the lowest latency, but the panel must be able to send outbound requests.
We poll the panel
If the panel can't connect out, a collector on the institution's network fetches records at regular intervals. The delay equals that interval and is shown on screen.
The panel's own interface
Some panel families share records only through their own interface. The connector talks to that interface, and its version is verified during installation.
All three methods produce the same standard event. Which one is possible depends on your panel, and we measure that rather than guess.
The standard event format
Whichever panel it comes from, every event is converted into a single standard format. Its fields are:
- Person: the identity within the institution; the raw card number is never transmitted.
- Gate: the gate and reader ID.
- Direction: was it an entry or an exit? If it can't be measured, this field stays empty.
- Time: both the device clock and the moment the server received the event.
- Source: the connector ID and connection method.
- Replay protection: if the same event arrives twice, the second one isn't counted.
Who makes the gate decision?
While connected, the panel makes the gate decision and we record the decision and its outcome. Rules such as appointments and banned-person lists are pushed to the panel.
When the connection drops, the gate keeps working with the panel's own local rules. Passes made in the meantime are collected once the connection is back and marked as “late-arriving records”.
Latency
Our target is for an event at the gate to appear on screen in under a second; with real-time push this is realistic.
No outage goes unnoticed
- Heartbeat: every connector regularly reports that it is running; if the heartbeat stops, the screen shows it.
- Rejected records ledger: every event that isn't accepted is logged with its reason; nothing is silently discarded.
- Missed event recovery: when the connection returns, the records from the gap are collected and put back in the right order.
For connector developers
Partners get access to the device schema and dry-run endpoint: the sample event you send is validated and nothing is saved.
Partner application