Product
Start without replacing your hardware
This page has one job: to give a measurable answer to one question — does it work with the hardware you already have. We also say what we cannot measure, on the same page; no row we have not measured is shown in green.
Protocol comparison
This table compares technologies. Where a row says not measured, the feature is not bad — it does not exist in that protocol and we do not pretend otherwise.
| Protocol | Direction | Encryption | Tamper reporting | Command to reader | Distance |
|---|---|---|---|---|---|
| Wiegand | One way | None | Not measured | Not measured | Short |
| OSDP v2 secure channel | Two way | Present when the channel is on | Available | Available | Long |
| Vendor interface | Depends on the vendor | Depends on the vendor | Depends on the vendor | Depends on the vendor | Over the network |
| File pull | Whatever the record holds | At the transport layer | Not measured | Not measured | Over the network |
- Direction: can the protocol itself tell whether the pass was an entry or an exit.
- Encryption: whether the line between reader and panel is protected.
- Tamper reporting: does the panel learn when the reader housing is opened.
- Command to reader: whether the panel can tell the reader something, such as a light or a sound.
- Distance: the cable distance the link can carry between reader and panel.
What we cannot measure on Wiegand
- No tamper report arrives when the reader housing is opened.
- The panel cannot send a command to the reader; light and sound cannot be driven.
- The line is open to listening; the card number is not protected on the wire.
- The reader's own health is unknown; we only learn it went silent because events stopped arriving.
Measurement is limited to what the protocol carries. On a Wiegand line only the card number and the moment of reading travel; no other field is ever produced. Compensating for that in software would be invention.
Panel and reader families
A connector path is defined for the families below. Even when the family is familiar, nothing is called compatible before the model and version are measured.
Card events can be read. The device clock often drifts from the server clock; the event is stored with both timestamps.
Card events can be read. In installations that also emit biometric events those fields are dropped in the adapter and never stored in any version.
Card events can be read. Gate and reader numbering differs between installations; the gate map is written once during commissioning.
Card events can be read. The rule engine sits in the panel itself; our rules do not replace it, they sit alongside it.
Card events can be read. On gates with a biometric reader only the card event is taken; the biometric field is neither requested nor accepted.
Profiles by gate and turnstile type
- Tripod turnstile: one-way counting, direction comes from the reader.
- Full-height turnstile: each face may have its own reader, so direction is clear.
- Speed gate: queue measurement matters most here during peak hours.
- Accessible gate: the same person record, a separate gate identity.
- Swing gate: when it is driven by a dry contact, direction usually cannot be measured.
Edge cases
If the gate only opens through a relay, who passed comes from the reader, not the gate. In that case the direction field is left empty.
When entry and exit sit on separate readers the direction is certain and the presence list is at its most accurate.
During a fire alarm the arm free-wheels and produces no record. The presence list meets that moment with the frozen roster; it never silently fills the missing record.
If the capacity rule can be pushed to the panel, entry can be closed. If it cannot, the screen warns but we do not close the gate; we never show something we cannot do as done.
Connector developer gate
The device schema is shared once a partner application is approved; the schema file is not published at a public address today.
The dry-run endpoint validates the sample event you send and writes nothing: it tells you which field is missing or which field has the wrong shape.
Every connector has its own device identity and secret; the secret can be rotated by the institution and the old one becomes invalid immediately.
See the technical gateSix things to tell us before installation
- The panel brand and model, exactly as written on the label.
- The reader protocol; it is fine if you do not know it.
- The number of gates and which building each one is in.
- Whether the panel can reach the network.
- The name and contact of the company that installed the turnstile.
- The card type and who holds the cards.
Writing these six lines into the form is enough; you do not need to prepare a document.
I do not know my protocol
Not knowing is not a blocker. Write what you know and leave the rest as I do not know; the result comes out as a possibility and the screen says it is one.
First choose your panel brand; if you do not know it there is still a path — the four-question branch opens it.
Are you the company installing the turnstile
Installation companies are not our competitors, they are our channel. The hardware stays yours.