SenseCrypt vs Daon

A customer buying Daon already operates an identity stack and is fitting biometrics into it, along with the front half of the lifecycle: a new person proved against a document, onboarded, then recognized on every subsequent visit. SenseCrypt is the stack itself, built for the last of those jobs, and a face is how it opens.

Keep that shape in mind through the rest of the page, because the feature lists converge while the products do not. Here, one service runs the ceremony and mints the token an application reads, which deletes an integration seam and a choice in the same stroke.

None of that weakens the case for treating sign-in as a product in its own right. The 2026 Verizon Data Breach Investigations Report found credentials present in 28 percent of breaches, and however rigorous the proofing at account opening, it does nothing for the thousandth sign-in.

Regulated buyers ask this question with a compliance framework open on the desk, which is the right way to ask it. IdP retains quantum-safe, sealed, biometric-free, disposable face tokens and their verifier challenges. Standard OIDC/SAML account records, device public keys, sessions, logs and encrypted tenant signing keys also persist. No face images or templates are retained in the documented phone flow. Licensed on-premises Webcam processes captures inside the customer deployment.

The retained face token is quantum-safe, sealed, biometric-free and disposable. No face images or templates are retained in the documented phone flow. Tokens are tenant-bound and stored alongside the required account records. ISO/IEC 24745:2022 is the reference for those properties, and ISO/IEC 30136:2018 for measuring the protection.

The result is a shorter biometric section in a risk register. There is no gallery to exfiltrate, biometric-free face tokens and account records to assess in a data subject request, and sealed, biometric-free, disposable face tokens and account records to assess on exit, which is why we describe the platform as biometric-blind.

More of the identity lifecycle sits inside Daon's scope than ours, across several modalities, backed by a long record in sectors that audit their suppliers rigorously. Establishing that a new customer is genuine and recognizing a returning one are two jobs, and a supplier holding both can price both in a single quote.

What follows is an account of what we traded away to build something narrow, not a complaint about anyone who built something wide.

One method, hardened, with no password path in reserve. The absence of anything gentler to retreat to is precisely what makes the front door hard, and precisely what makes it rigid. Both of those hold simultaneously.

Any grid, the one further down included, will award identical ticks to products that earned them for unrelated reasons. Four questions do the separating that a table cannot.

Put them to us too. Each answer below is what we would say in a meeting, written out here so the two versions can be held against each other.

Seats cost a dollar a month against a floor of twenty, which opens an estimate rather than closing it. Non-exportable signing keys in a managed key service add twenty dollars per key per month, and the key cannot be copied out by anyone, including us. Tenants and custom domains beyond the three an account already carries cost ten dollars a month each, and customer identity deployments meter monthly active users, so a month with no sign-in produces no charge for that account.

The trial runs thirty days and asks for no card. Two boundaries a regulated buyer should know before the security questionnaire arrives: end-user authentication keeps no operator-side single sign-on session, so each application sign-in is its own ceremony and the only browser session in the product belongs to the admin console; and the hash-chained tamper-evident log covers console and administrative actions, while end-user sign-ins are recorded in a separate read-only activity stream that is not hash-chained and has no customer-facing verification endpoint.

• OpenID Connect and OAuth 2.0 (RFC 6749), with PKCE (RFC 7636) and pushed authorization requests (RFC 9126)
• SAML 2.0 identity provider, and SCIM 2.0 (RFC 7644) provisioning for users and groups
• FAPI-CIBA / CIBA: a backchannel push starts a face check on the enrolled phone.
• Roles and permissions in the token, a default-closed group gate at sign-in, capability checks on console routes
• Liveness detection tested by iBeta to ISO/IEC 30107-3 Levels 1 and 2
• Tenant isolation, with three tenants or custom domains per account included.