Ollet Try the demo

End impersonation. Verify identities. Fully on-device.

Configure Ollet into Okta with a few clicks. Or use our SDK for a custom integration.

Try the Demo Download on the App Store

What this team built and shipped on before Ollet

  • Aadhaar
  • Samsung
  • Fujitsu
  • Microsoft
  • HP

The biometrics behind India’s national ID programme, and the iris unlock that shipped on these devices. Acquired for $120M. The team

One synthetic identity, three ways in
  1. Input Deepfake Spoofed
    • Gate Account enrollment Passed
    • Gate Account recovery Passed
    • Gate Sensitive workflows Passed
  3. Result Access granted Breach

The same identity gap is documented by

MFA checks credentials, not people.

Stolen factors can unlock accounts; synthetic identities can exploit enrollment, recovery and other high-risk workflows.

65%

of initial access is identity-based

Unit 42
35%

of AI-driven breaches used deepfake impersonation

IBM

The answer

IDVs check pictures of IDs, A picture can lie.

Ollet verifies the user statelessly against signed identity data, such as a passport chip, a mobile drivers license, or a corporate ID. Our neural-engine technology checks liveness and matches face fully on-device at 30 FPS.

A check, end to end

  1. Scan QR
  2. Match face
  3. Done

Why the check holds

Trusted Authority
The signed identity data cannot be faked or forged, like a picture can.
Matched live
Only the real identity holder can pass the check.
Completely stateless
No account state or preregistration to tamper-with or exploit.
Ollet

Verify your identity

Northwind
Continue

With Ollet

Reading chip

No images stored

Every other verifier

Capturing

Breachable

The guarantee

We never upload your ID or face.

Other verifiers send ID and face images to a server, where they can be stolen or poisoned in transit or in storage.

6 of 7

verifiers failed the Department of Homeland Security's security evaluation

DHS S&T
1B

IDs exposed in one identity-verification database breach

Cybernews

FAQ

Frequently asked questions.

What happens during a verification?

The user opens a QR code or link and completes a live face match on their phone. Ollet checks the holder against a supported, issuer-signed ID and returns a signed result in seconds.

What leaves the phone?

The ID image and live face stay on the device. The requesting service receives a scoped, signed result for that verification—not a document copy or biometric image. Ollet does not create a central store of those images.

How is this different from uploading an ID and selfie?

Upload-based checks send document and face images to a server and judge the images they receive. Ollet instead verifies cryptographically signed chip data and performs the live face match on the device, so those images do not need to be sent to Ollet.

Does Ollet replace MFA or passkeys?

No. Keep them for everyday access. Use Ollet when you must prove who is present—during account recovery, resets, privileged access, high-value transfers, or other irreversible approvals.

Which IDs can Ollet verify?

Ollet supports digitally signed, chip-enabled credentials such as ePassports, plus supported mobile, national, and enterprise-issued IDs. Coverage varies by issuer and platform, so confirm your intended population before rollout.

How do we add Ollet to our stack?

For workforce use, connect Ollet to Okta and apply it through access policies. For product flows, use the SDK to start verification and verify the signed assertion in your backend. No custom hardware or identity-image storage is required.

Require the person, not the password.

On reset, recovery, and anything irreversible. The holder has to be there.

See the product Talk to us