On this page
The password is the part that breaks
A password is a secret that two parties share, and that is the whole problem. The user has to invent it, remember it, and type it into whatever page asks for it, including a page that only looks like yours.
Everything you layer on top, from complexity rules to rotation policies to breach monitoring, is work spent protecting a secret that should not need to exist. You are not fixing the design. You are paying rent on it.
Reuse turns one breach into many
People reuse passwords because they have to remember them. A credential list leaked from some other site gets replayed against yours, and it works often enough to be worth an attacker's time.
A copied login page collects a working secret
Phishing succeeds because the user, not the browser, decides where the password goes. One convincing screenshot of your sign-in screen is enough to get a credential that works.
The reset path is usually weaker than the login
Every forgotten password sends a user down a recovery route that trusts an inbox or a help desk. Attackers aim there first, because that is where the checks are softest.
How SenseCrypt removes it
SenseCrypt is a full identity provider that knows one way to sign a user in: the user looks at the camera on their own device. Enrollment starts from a photo you already hold, so there is no separate capture ceremony to design and no password email to send.
What travels back to your application is a standard token. What does not travel anywhere is the face.
Enrollment starts from a photo on file
You do not have to run a registration step for every user before they can sign in. An existing photo creates the enrollment, and the first sign-in is already a face login.
The match runs on the device
Capture and comparison happen on the phone or laptop in the user's hands. The server keeps no face image and no face template, so there is no gallery to breach, subpoena, or migrate later.
Each sign-in spends a single-use token
The face becomes a patent-pending single-use face token. A copy captured in transit is worth nothing, because the token it copied has already been spent.
The proof is bound to the device
The signature comes from the enrolled device, so a proof produced for your site cannot be relayed into a session somewhere else. That binding is what makes the sign-in phishing-resistant.
One integration for web and mobile
The face is the only part of this that is new to your engineers. Everything else is the protocol work your team has already done for some other provider: a redirect, a callback, a token you validate, a session you issue.
Mobile is the same story with a shorter path, because the device is already the place the ceremony runs. If your app can talk to any standards-based identity provider, it can talk to this one, and what changes is configuration rather than flow.
- OpenID Connect (OIDC) and OAuth 2.0 with PKCE and PAR
- SAML 2.0 for enterprise single sign-on (SSO)
- SCIM 2.0 for user provisioning
- CIBA for a backchannel sign-in
What changes after the switch
Security and convenience usually trade against each other, and a security team learns to expect the argument. Removing the shared secret is one of the rare moves that improves both, because the thing you deleted was simultaneously the hardest part for users and the most useful part for attackers.
There is nothing to phish
No password and no code is entered at sign-in, so a fake login page can render perfectly and still collect nothing usable.
The reset queue empties
Users cannot forget what they never set. Support volume moves from daily password resets to the far rarer case of a replaced device.
Sign-in gets shorter, not longer
The user looks at the camera and is through. No typing, no waiting on an inbox, no second app to open.
Who it fits
This suits any product where the sign-in is a chore for the user and a liability for you. The list price is one dollar per user per month with a 20-seat minimum, and customer identity bills as monthly active users, so an account that does not sign in that month costs you nothing.
That is the list price rather than the whole bill: KMS-custody signing keys add twenty dollars per key per month, and each tenant or custom domain past the first three costs ten dollars per month. The 30-day trial takes no card.
- Customer identity (CIAM) for web and mobile apps
- Workforce single sign-on (SSO) for staff
- B2B SaaS SSO for business customers
Frequently asked questions
What is passwordless login?
Passwordless login is a sign-in method that uses no password. A user proves identity with a stronger factor. SenseCrypt uses a face login on-device.
Does passwordless login work on web and mobile apps?
Yes. SenseCrypt supports web and mobile apps through open standards. It uses OIDC, OAuth 2.0 with PKCE and PAR, SAML 2.0, SCIM 2.0, and CIBA.
Where does SenseCrypt store the face data?
SenseCrypt stores no face image and no face template on the server. Face matching runs on-device. A face becomes a single-use face token.
How much does SenseCrypt cost?
SenseCrypt costs one dollar per user per month (20-seat minimum). A 30-day free trial needs no card.
Related