Unlock your office door with your phone — on the system you already own.
GateStride reads your access-control system’s events and calls its own unlock. Your locks, wiring, egress and certifications don’t change. Two pieces make it work: a small node at each door and a GateStride center in your comms room. Both run on your premises. There is no GateStride cloud.
By Tom Jin · October 2026 · Early access


Illustrations, not photos of production hardware. The door node is an off-the-shelf small device that we configure.
The architecture, on one page
The phone holds a private key created inside its secure element (StrongBox on Android, the Secure Enclave on iOS); the key never leaves it. A watch or tablet can carry its own key too. The door node exchanges a one-time signed challenge with the phone over Bluetooth, checks the person is allowed through that door at that time, and unlocks through your existing system. The center is where you enrol people, push credentials to the nodes and see occupancy, attendance and the audit log. Your existing system keeps doing its job: locks, readers, panels, request-to-exit and fire release.
Why two pieces?
The door node is the part that actually opens the door, so it is built to run on its own: it holds a signed set of credentials and makes the decision locally. The center is where people are managed and records are kept. Splitting them means the busy, administrative side can be restarted, updated or briefly offline without anyone waiting at a door. It also keeps the moment of entry short: a phone, a node and your existing system, all within the same building.
From first call to live roll call
- Assess your system. We confirm which access-control software and version you run, how many doors you want covered and where the center will sit. During early access GateStride is verified on Kantech EntraPass; LenelS2 OnGuard and Brivo are in development and Honeywell, Software House and HID are planned. See the compatibility list.
- Your integrator installs a node per door. A small off-the-shelf device we configure is mounted at each covered door. Locks, readers, panels and request-to-exit are not re-wired.
- Connect to your existing software. The center links to your access-control software with a dedicated operator account that you create and own. Those credentials are stored encrypted at rest and are never shown again in the interface.
- Enrol phones. Staff get an invite; their phone generates its key in the secure element and binds it. Cards keep working for anyone who still uses them.
- Exit tracking and roll call go live. Entries and exits are both recorded, so the center keeps a live list of who is inside, first-in and last-out attendance with CSV export, and a one-tap roll call for an alarm. Read more in know who left.
What the integrator does — and what stays untouched
The integrator
- Confirms your system, version and doors
- Mounts and connects a door node at each covered door
- Sets up the center on your premises
- Connects it with your dedicated operator account
- Tests each door with an enrolled phone
What stays exactly as it is
- Locks, strikes and maglocks
- Readers, controllers and panels
- Request-to-exit and free egress
- Fire release and the certified life-safety path
- Cards and fobs already issued
GateStride never becomes your lock, your request-to-exit, your fire release or your certified controller. The install needs no re-wiring, no new panels and no re-certification of the life-safety path. Integrators: see the partner program.
Day to day
Once it is running, most of the work sits with whoever manages people: usually the office manager, HR or facilities. A new starter gets an invite and enrols their phone; there is no badge to print. When someone leaves, you remove them in the center. Because GateStride connects as one integration user rather than one seat per person, adding staff does not add per-user fees from GateStride. The live who’s-inside list helps the last person out before lock-up, and attendance exports give HR first-in and last-out times without anyone filling in a timesheet.
For property managers, each building runs its own center on its own premises, so one tenant’s or one building’s records stay where they were created.
When the network goes down
If GateStride itself goes down, your doors don’t. Your existing access control keeps working exactly as it did before GateStride was added: cards and fobs still open doors, request-to-exit and fire release are unchanged, and the system keeps its own event log. GateStride only adds to it; it is never in the existing system’s own unlock or egress path.
The door node is the part that opens the door, so it is built to work on its own. It keeps a cached, signed set of credentials and continues to verify phones if the network or the center is unavailable, refusing anything it cannot verify. When the connection returns, it resyncs with the center. Because the center is not in the real-time unlock path, a slowdown there does not hold up entry. Free egress doesn’t depend on GateStride at all.
Exit tracking supports accountability during an evacuation. It is not a substitute for free egress, your evacuation plan or your certified fire and life-safety systems. This is general information, not life-safety advice; confirm requirements with your authority having jurisdiction.
What we need from you
- The name and version of your access-control software, and who services it. (How to identify your system.)
- A list of the doors you want covered, and which ones are exits people use daily.
- A place for the center on your premises, usually your comms or server room.
- A dedicated operator account on your existing system for GateStride, created by you or your integrator, with only the permissions it needs.
- Your licence terms. GateStride connects as one integration user. We check your vendor’s licence with you before you commit, because some vendors license per cardholder or per connection.
- Someone to own it: usually the office manager, HR or facilities, who will enrol and remove people.
Early access: what that means
GateStride is in early access. We run it on our own office’s Kantech EntraPass installation, and early-access pilots with other sites are arranged one by one. Pricing is by quote: flat, with no per-user fees. If your system is in development or planned, tell us; demand decides what we verify next.
Questions
- Does GateStride replace my access control system?
- No. It overlays the system you already run. It reads that system’s events and calls its own unlock. Locks, readers, panels, request-to-exit and fire release stay as they are.
- Is GateStride a cloud service?
- No. The GateStride center and the door nodes run on your premises, connected to your access system with your own credentials. GateStride does not offer a hosted or cloud service.
- What happens if the network or the center goes down?
- Door nodes keep verifying phones from a cached, signed credential set and resync when the connection returns. Free egress is never affected, because it stays with your certified system.
- Do staff have to tap their phone to leave?
- No. People leave through the free-egress door as they do today. The door node notes an enrolled phone, watch or tablet going out, with no tap.
- Which systems does GateStride work with?
- GateStride is in early access. Kantech EntraPass is GateStride Verified; LenelS2 OnGuard and Brivo are in development; Honeywell, Software House and HID are planned.
See it on a real door
We will walk you through phone unlock and roll call, and check whether your system fits.
Kantech, EntraPass, LenelS2, OnGuard, Brivo, Honeywell, Software House and HID are trademarks of their respective owners. GateStride is independent and not affiliated with or endorsed by them.