Replace 2FA codes with faster, user-friendly authentication

The actual TypingDNA experience is identical in both versions, however, the Standard integration is a standalone integration that does not need any IAM to work, while the OIDC integration can be used in Okta (and other IAM platforms in the future).

Also the OIDC integration has no independent root of trust (RoT) and only comes with the Enterprise license. If you have any questions or doubts about the differences please contact us for more information.

The Starter plan for Verify 2FA is a great way to get started with typing biometrics authentication. It is free to use for 100 users each month and is ideal for small applications. No credit card is needed.

The Pro plan is designed for applications that have more than 100 users per month and can be billed directly to a credit card. The Pro plan does not include free users.

Please note that the OIDC integration is only available with the Enterprise license/plan.

Yes. On mobile devices authentication is automatically handled with traditional SMS codes for a better user experience. Standard integration only.

SLA commitments are available for enterprise customers. Contact us to find more.

Our solution still recognizes people even after some minor hand injuries, however, there are cases where you will not be recognized after such an event. In this case, a failed verification will occur and a code will be sent over SMS to the end-user's phone.

On a monthly basis, we count the users you have in our database during the previous month. A user is the end user of the technology, i.e., a person who is authenticated using TypingDNA.

Moreover, on a monthly basis, we count the number of authentications for each user and compare them to the plan you are on. Authentication is the process of comparing a user’s typing pattern to the user’s profile, consisting of one or more previously recorded typing patterns.

The billing period is always a calendar month. One month of a subscription is always measured from the first day of the month to the last day of the month.

Our solution doesn’t cover any channel costs, however, to get started, we do cover the first 200 SMS OTP codes in the Sandbox environment. Then you'll be able to plug in your own provider (such as Twilio or SendGrid). Standard integration only

We default to SMS if typing verification fails, there is no way around it. But if the phone is stolen, you should be able to still log in with your TypingDNA and perform desired actions in the client platform, at least until a RoT authentication with an SMS code is needed.

Yes. You can choose between either a phone number or an email address as a Root of Trust (RoT). Standard integration only

Sure, try our live demo.

Authentication API and Verify 2FA use the same core technology, but Authentication API was built to enable any kind of integration that requires typing biometrics based authentication in any platform through the use of our RESTful API. While 2FA is a common use-case for the Authentication API, it isn't a constraint, and the product can be leveraged within an application flow wherever a user's typing behavior requires confirmation. On the other hand Verify 2FA is designed to be used as a 2FA factor in existing IAM systems with minimal integration development on our client's end.

The Standard integration of Verify 2FA is a managed OTP replacement product. Designed with frictionless, cost-effective authentication in mind, Verify 2FA combines typing behavior verification with intelligent OTP features in one solution. In Verify 2FA, users authenticate with their typing behavior (by typing assigned words). OTP codes for identity verification are only leveraged in necessary scenarios, such as an initial enrollment or failed verification attempt. This solution is useful for companies that don't already use a major IAM, but have a basic 2FA in place, a simple SMS OTP service in addition to their internal user management system.

The newer, OIDC integration of Verify 2FA offers the ability to use the same Verify 2FA experience in platforms like Okta. Unlike the standard integration, it does not rely on an internal root of trust (RoT) such as SMS/Email OTP but it can be used as an authentication factor in platforms like Okta. Other factors need to be defined separately in Okta/do not depend on TypingDNA directly.