Access control plane

The door and the laptop are the same session.

When someone leaves, the badge stops working and the laptop locks, on site, in the same half-second. One Presence Session governs both planes, and one epoch ends them together.

Presence Sessions
≤ 80 msCredential to strike, asynchronous portal
≤ 500 msOn-site badge and laptop revocation
1:1Face and gait corroborate the credential, never search a population
ZeroBiometric templates stored in the hosted service
How a portal decides

The strike does not wait on a neural net.

Asynchronous turnstiles release on the credential. Corroboration attaches to the session and can escalate the laptop, the next door, or the security team, rather than attempting a physically impossible retract.

A handheld device tethered to a laptop, being read
01 · CLAIMED

OSDP Secure Channel

Encrypted secure channel, local access list, epoch check. Under 80 ms. A legacy cleartext reader is a defect, not a fallback.

A face with binary digits projected across it
02 · CORROBORATING

Gait and face, 1:1

The credential named the person. Templates are compared only against that person's own enrollment, and the frames are dropped.

A team meeting seen from above, laptops and tablets across the table
03 · ADMIT or HOLD

Then the rest of the building

A tailgated entry marks the session. A presentation attack holds. A revocation ends the badge and the screen together.

Privacy

Raw video dies at the edge.

A three-second buffer in memory. Keypoints live about 1.6 seconds. Plaintext templates are encrypted under a key sealed to the node's own hardware, then explicitly overwritten. The hosted service sees scores and metadata. It never sees a face.

European data protection law treats these templates as special-category data even when they only corroborate a claim. A policy carrying gait or face weight will not compile without a recorded lawful basis. Customer templates never train a shared model.

Security & privacy

A dark server aisle lit by blue indicator lights
Against the suite

What the ticket suite cannot do on Monday morning.

Capability Baselivery Ticket-first suites
Badge and laptop as one session One Presence Session, shared epochs Separate access control, device management, and helpdesk
On-site revoke, both planes p99 ≤ 500 ms A ticket, then a wait for a human
Encrypted reader channel Mandatory at every portal Usually a third-party access control system
Edge biometrics without a cloud gallery Site-local templates, gated on lawful basis Vendor warehouse or nothing
CISO modality floor Compiled policy, dual control to weaken Firmware change or professional services
Employment attestation, no personal data Signed attestation, no personal data HR letter
Gate pass bound to the portal Native, and readable by the policy engine Email chain
ITSM / ITAM Shipped, on the same identity graph The whole product

Bring the door onto the same epoch as the laptop.

We will walk you through a live portal, a compiled policy pack, and a revocation that closes the turnstile and locks the screen together. The asset register is already there when you need it.