Workforce
People and credentials live in one place. Once enrolled, someone can be recognized across your terminals.
Neo is the cloud console behind the punches. It holds workforce data and site rules, pairs arrivals and departures into a clear day, and keeps records you can trust — wherever people check in.
What the console does
Neo keeps the workforce list, applies the rules that were active when someone punched, pairs entries and exits across gates, and keeps a history of changes — what HR and finance need when attendance becomes a payroll question.
Inside Neo
People and credentials live in one place. Once enrolled, someone can be recognized across your terminals.
Shift rules and grace periods use the policy that was in force when the punch happened — not today’s rewrite of yesterday.
Enter through one gate and leave through another; Neo resolves that centrally into one day.
Neo terminals and many existing third-party devices can report into the same console.
Terminals keep working when the network drops, then sync events in order when they reconnect.
Corrections leave a trail. Last month’s attendance stays last month’s attendance.
Software
Pairing, reporting, and policy live here. Start with how Neo works if you want the fuller explanation.
Read how Neo works →Hardware
Lobbies, remote sites, and field teams all create events. Neo hardware is built for those places, and existing devices can often join the same estate.
Look at the devices →In practice
Bring questions about gates, offline periods, or devices you already have.