Server policy
Person, group, facility, entry point, time, assurance, anti-passback, and two-person rules.
MesaiGo Access
Complete the evidence before unlocking the door.
Every link is verified independently, from the mobile credential and gateway witness to the server decision, signed actuation, and physical passage observation.
2Assurance profiles
2RIndependent relays
4IProtected field inputs
OSDPSecure controller path
End-to-end access
Access approval, door unlock, and observed passage are not the same event.
MesaiGo does not conflate these outcomes. The decision, controller command, relay result, door contact, and turnstile sensor are bound to the same attempt while each retains its own audit meaning.
Signed actuation
A time-bound, single-use final command bound to the relevant actuator.
Physical passage evidence
Door contact, REX, turnstile direction, held-open, reverse passage, and tailgating events.
Explainable audit
The policy and reason behind each allow or deny decision remain visible.
Resilience
Security does not change silently when the network fails.
Online and bounded-offline behavior, clock drift, key expiry, and server unavailability are defined per profile. High Assurance does not fall back to Standard when required evidence is missing.
Offline policy
A signed, time-bound local policy package tied to the entry point.
Life safety
Fire and emergency-egress circuits are managed independently of the MesaiGo cloud.
Fail-safe / fail-secure
An explicit installation decision and change audit for each door type.
Let us evaluate your existing door and turnstile infrastructure.
Together we can map controller, I/O, network, assurance, and life-safety boundaries.