Server access rules
Person, group, facility, entry point, time, required security level, anti-passback, and two-person rules.
MesaiGo Access
Verify the phone, gateway, and proximity before unlocking the door.
For every attempt, the server records the enrolled phone, correct gateway, decision, single-use door command, and sensor result together. Each step can then be reviewed separately.
2Verification levels
2RIndependent relays
4IProtected field inputs
OSDPSecure controller path
Decision, door, and sensor result
Access approval, door unlock, and observed passage are not the same event.
MesaiGo does not mix these outcomes. The server decision, command sent to the door controller, relay result, door contact, and turnstile sensor are linked to the same attempt and shown separately in the transaction history.
Signed door command
A time-bound, single-use unlock command that works only on the relevant door controller.
Physical passage result
Door contact, REX, turnstile direction, held-open, reverse passage, and tailgating events.
Clear transaction history
The rule and reason behind each allow or deny decision remain visible.
Resilience
Security does not change silently when the network fails.
The system denies the transaction when the clock is wrong, a key has expired, or the server is unavailable. A gateway cannot unlock a door on its own, reuse a previous result, or grant extra time without server approval. High Assurance does not fall back to Standard when a required check is missing.
Denied without the server
The gateway may preserve health and maintenance data, but it never activates a relay without signed server approval.
Life safety
Fire and emergency-egress circuits are managed independently of the MesaiGo cloud.
Fail-safe / fail-secure
Installation defines whether each door remains unlocked or locked in an emergency, and every change is recorded.
Let us evaluate your existing door and turnstile infrastructure.
Together we can define the door controller, input/output connections, network, security level, and emergency requirements.