Hardware
You can keep hardware already on site
Neo terminals are designed to run alongside third-party devices you may already have installed. The goal is one attendance record across that mix, without a full rip-and-replace on day one.
How Neo works
Why Neo is built the way it is.
Attendance breaks down when people move between doors, sites go quiet on the network, rules change mid-month, or old terminals stay in place. These are the design choices Neo makes for those conditions.
Gate
Events at the door
Console
Rules and pairing
Site
Offline and remote
Enrolment
Enrol someone once and use that enrolment across doors
Faces and credentials sync across the device estate. Someone should not need a separate enrolment every time they use a different entrance or terminal.
Pairing
In and out pairing happens in the cloud
On multi-entrance sites, a person may enter through one gate and leave through another. Neo resolves that movement centrally instead of asking any single gate to decide the whole day.
Policy history
Late data still follows the rules from that time
When punches arrive late, Neo judges them using the policy that was in force when they happened, not today’s settings rewritten onto yesterday. Changes leave an audit trail.
Offline
Offline periods are expected, not treated as failures
Terminals keep working without a live network. When they reconnect, events sync in order so punches are not lost or duplicated. A terminal also checks clock integrity before it will record.
In one picture
Different gates. One attendance day.
Each gate captures an event. The console pairs those events for the person — even when entry and exit happened in different places.