Built to the standard a door deserves.
GateStride touches the way people get in and the record of who left — so every design choice starts from security, not convenience.
Keys never leave the phone
Each device creates its credential key inside its hardware secure element — StrongBox on Android, the Secure Enclave on iOS. The private key cannot be exported or copied. The door only ever sees a signature, never the key.
Unlocking is decided at the door
When a phone approaches, the door node issues a single-use challenge; the phone signs it; the node verifies the signature against the person’s public key and the door’s own rules. The central server is never in the real-time unlock path, so a central slowdown or outage does not hold up the moment of entry.
It keeps working offline
Door nodes hold a signed, cached set of credentials. If the network or the center is unavailable, the door still verifies and opens from that cache — and refuses anything it can’t verify. A cloud outage does not stop verified credentials from opening the door. Free egress always stays with your certified system.
Links to your system are encrypted
The credentials GateStride uses to talk to your underlying access control are stored encrypted at rest and are never returned through the interface. Operators can set and test them; no one can read them back.
The record can’t be quietly changed
Every security-relevant event is written to a hash-chained audit log: each entry seals the one before it, so any edit, deletion or reordering of history is detectable on verification.
Privacy-first: no biometrics by default
By default GateStride identifies devices and credentials, and uses person detection — not facial recognition — for occupancy, so there is no biometric data to store or govern. Facial recognition is optional, off by default, and offered only where it is legally compliant and the customer chooses to enable it; that choice, and its compliance, stays with you.
Roles and accountability
The center uses role-based access — owner, manager, department and HR — with department-scoped visibility, so each operator sees and changes only what their role allows, and every change is attributed.