The records were already there. The door could not hear them.
Baselivery started as the estate system operations teams actually run: custodians, serials, gate passes, a service desk. That graph was inert at the turnstile and at the lock screen. We built the session authority those records were waiting for.
A leaver with a working badge is not a helpdesk problem.
If the account is disabled, the laptop stays unlocked, and the turnstile still opens, you do not have zero trust. You have three separate systems and a ticket queue.
We specify one Presence Session. Physical presence at a portal, from an encrypted credential corroborated by gait and face scored at the edge. Logical presence at a managed endpoint. A policy a security lead can tighten in seconds without a firmware change. Revocation that ends both planes on the same epoch.
The service desk and the asset register stay. They are how you know who holds the laptop and who authorised carrying it out of the building. They are not a substitute for the strike relay, and they were never meant to be.
Commitments, not brochure copy.
Revoke before gallery
A biometric store without working global revocation is worse than a credential-only building. That is fixed as implementation order, not a preference.
No cloud video
Camera frames are not a product feature. Incident clips require a legal hold and a human decision, and are off by default.
Not the IdP
Your directory remains authoritative. We consume its state and never replace it.
Not city-scale ID
Face never unlocks anything alone. The credential is the index, and bystanders are never embedded.
Same house as Saaslivery. Separate product.
Saaslivery is our operational ERP product. Baselivery is sold and deployed entirely on its own, the way a complete access and estate platform has to be. Where a customer runs both, optional events can pass between them, so a new joiner in one can raise an equipment request in the other. It is never a hard dependency in either direction.
Deploy as a hosted multi-tenant service or as a dedicated single-tenant installation, from the same binary. Each edge node is pinned to exactly one workspace. Encryption key shares for biometric templates are held entirely by customer custodians, and Baselivery staff hold none.
