01
The decision in brief
Decide whether you want a part or a system. A liveness component changes one part of a stack you keep; an identity provider moves the sign-in itself. Put a number on the engineering that has to surround the component, because the license quote will not show it.
Choose FaceTec when
you want a specific liveness and matching engine inside an application you control, and you already run your own sessions, tokens and directory.
Choose SenseCrypt IdP when
you want the session, token, directory and protocol layer delivered with the face check, and an OIDC or SAML integration rather than an SDK project.
Side by side
| Dimension | SenseCrypt IdP | FaceTec |
|---|---|---|
| What you buy | An identity provider with the face check inside it | Face liveness and matching, licensed as a component |
| Session and token layer | Included | Built by the integrating vendor or customer |
| Where face verification runs | On the enrolled phone (both phone methods) | Depends on the integration |
| Liveness evidence | iBeta, ISO/IEC 30107-3 Levels 1 and 2 | Published testing and a public spoof bounty |
| Application protocols | OIDC, SAML 2.0, SCIM 2.0, CIBA | Not applicable to a component |
| List price | $1 per user per month; 20-seat minimum | Licensed; varies by agreement |
What you buy
- SenseCrypt IdP
- An identity provider with the face check inside it
- FaceTec
- Face liveness and matching, licensed as a component
Session and token layer
- SenseCrypt IdP
- Included
- FaceTec
- Built by the integrating vendor or customer
Where face verification runs
- SenseCrypt IdP
- On the enrolled phone (both phone methods)
- FaceTec
- Depends on the integration
Liveness evidence
- SenseCrypt IdP
- iBeta, ISO/IEC 30107-3 Levels 1 and 2
- FaceTec
- Published testing and a public spoof bounty
Application protocols
- SenseCrypt IdP
- OIDC, SAML 2.0, SCIM 2.0, CIBA
- FaceTec
- Not applicable to a component
List price
- SenseCrypt IdP
- $1 per user per month; 20-seat minimum
- FaceTec
- Licensed; varies by agreement
02
A liveness component or an identity provider?
What FaceTec licenses is the face check itself. A customer embeds it inside an application they own and then supplies everything around it: the session, the token internal services trust, the directory and the protocol the applications speak. That surrounding layer is what SenseCrypt IdP provides, with the face check as the way in.
Deepfakes have sharpened the question of what a face component actually covers. In early 2024 a finance employee at the engineering firm Arup authorized transfers of about US$25 million after a video call with deepfaked colleagues, as reported in February 2024. That attack targeted a human decision rather than a biometric sensor, but it is why buyers now ask exactly which attacks a liveness result covers.
Integrate a component into your system
An SDK license changes one part of a system that stays yours. Everything around that part also stays yours, including the pieces teams routinely underestimate.
An identity provider manages sign-in
SenseCrypt IdP issues the tokens, holds the enrolled users and runs the face check. That is less code for you to write and more of the flow outside your direct control.
A public spoof bounty
FaceTec opens its liveness technology to a spoof bounty anyone can attempt, a more confident posture than this market usually adopts.
03
What a liveness result covers
Presentation-attack detection in SenseCrypt IdP is tested by iBeta to ISO/IEC 30107-3 Levels 1 and 2. That standard governs testing of attacks presented at the sensor: a printed photograph, a screen replay or a mask.
It does not cover a virtual camera or an injected video stream, and no ISO/IEC 30107-3 result should be read as though it did. Injection is a separate threat and is assessed separately. On the controls side, sign-in runs inside the app on an enrolled phone, with app attestation and device authenticity checks at each ceremony, and the webcam method runs on secure terminals.
Face recognition, as opposed to liveness, is evaluated in NIST FRTE under Seventh Sense's own name since 2021. FRTE evaluates the algorithm; it does not certify the product.
04
SenseCrypt IdP at a glance
05
Frequently asked questions
Is SenseCrypt IdP an identity provider or a biometric SDK?
SenseCrypt IdP is an identity provider: OpenID Connect and OAuth 2.0, SAML 2.0, SCIM 2.0 and CIBA, with role-based access control and multi-tenant isolation. The face check is how a user proves presence inside that provider, not a component you embed in your own application.
Can we license Seventh Sense face technology on its own?
This comparison covers SenseCrypt IdP. Seventh Sense also offers biometric SDKs; if your requirement is a face component inside an application you own, say so directly at sales@seventhsense.ai.
Why does the page not quote accuracy numbers?
Because a false accept or false reject figure is meaningless without the dataset, the threshold and the operating point behind it. Seventh Sense face recognition is evaluated in the NIST FRTE under its own name, and the public report card is the honest place to look at measured performance.
How much engineering does an integration take?
An OIDC or SAML integration of the kind your team has probably done before. That is the practical difference from licensing a component: the session layer, the token service and the directory already exist, so the work is configuration and claim mapping rather than building the surrounding system.