Smarter, user-friendly authentication that replaces 2FA codes

Start now for free.

Typing biometrics authentication service for advanced integrations

Start now for free. Upgrade as needed.

Starter

Free

Free for first year, for up to 100,000 users, selected customers only.
No credit card required.

Pro

$ 0.01

Per active user, billed monthly

For any number of users.

No credit card required.

USD
EUR

Do you want to learn more?

Frequently asked questions

Mobile support is not available yet. Although we have technology that works on mobile devices, we decided to add this support at a later time. Mobile traffic is currently being solved with traditional SMS codes.

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.

Our solution doesn’t cover any channel costs. In our client dashboard you’ll be able to plug in your own provider (such as Twilio, Nexmo, Telesign, AWS).

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).

Once you sign up you’ll be able to check out the demos.

The Authentication API is a flexible interface that allows clients to verify user identity by their typing through requests to a 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. The Authentication API is limited to enrolling and verifying typing patterns, and does not include managed OTP features (One Time Passwords/also known as 2FA codes).

Verify is a managed OTP replacement product. Designed with frictionless, cost-effective authentication in mind, Verify combines typing behavior verification with intelligent OTP features in one solution. In Verify, 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.

Developer

Free

Build with TypingDNA for free with
unlimited authentications and users.
No credit card required.

Pro

$

1

Per user, billed monthly

4¢ each extra authentication

External Users Internal Users
  • Advanced API access.
    Up to 50 monthly authn./user
  • High frequency, usually for employees, students

Enterprise

For mission-critical applications, TypingDNA provides a full SLA, as well as options for private infrastructure and enterprise-level support.

USD
EUR

We just launched TypingDNA Verify.

A significantly more affordable solution to replace SMS 2FA codes.

Starts at $0.01/active user/month.

Learn more

Features

Developer

Pro

Enterprise

Authentications

Users

Max rate

Desktop support

Mobile support

Recorders for all major platforms

Public infrastructure

Standard API endpoints

Advanced API endpoints

Plugins and integrations

Detailed reporting

Private infrastructure

SLA

Advanced administration tools

Custom services

Enterprise support

Custom pricing options

  • Unlimited 
  • Unlimited
  • 1 req/second
  • Limited
  • 2 days
Start now
  • Unlimited
  • Unlimited
  • Limited
  • 30 days
  • Unlimited
  • Unlimited
  • Custom
  • Unlimited
Talk to us

Pro | cost estimator

Monthly average number of:

External Users Internal Users
  • Up to 50 monthly authn./user
  • High frequency, usually for employees, students

$ 0

Billed monthly

4¢ each extra authentication

100 users

High standards

We strive to innovate and contribute to the biometrics industry while driving efforts to achieve the highest standards for our clients.

ps iso associations associations

Frequently asked questions

Developer plans are limited in API access to /user and /auto -- a universal API that offers equal functionality to our Advanced API’s with less customization options. Limitations of the Developer plan include historical log visibility of 2 days, a 30 authentications per end-user daily maximum, and a transaction limit of 1 request per second. While subscribers to the Developer plan may use TypingDNA for free, with unlimited account-level authentications and unlimited typing profiles (end-users), the Pro plan is designed for those who require more flexibility -- Advanced API’s and settings enable a more customized authentication flow, increased logs visibility (30 days) simplifies compliance, and the absence of a rate limit accommodates more dynamic traffic patterns.

Enterprise subscriptions make sense if you need a custom deployment (i.e., not on our public cloud), an enterprise-grade SLA with availability commitment, a higher level of support, or non-standard typing recorders. Check the comparison table above for more information.

Developer and Pro accounts have access to our public cloud infrastructure (shared). You can choose to run on our EU-based infrastructure (eu-api.typingdna.com) or on our U.S.-based infrastructure (us-api.typingdna.com).
Enterprise accounts also have private cloud (single-tenant) and on-premises options available.

Security and privacy are of the utmost importance for us.
TypingDNA is certified for ISO 27001, ISO 27017, and ISO 27018. Our API uses the HTTPS protocol (TLS 1.2 or higher) and basic authentication. Moreover, we encrypt all typing patterns and user IDs stored in our database.
In terms of privacy, please go over our privacy policy for details. TypingDNA is enrolled in the EU-U.S. Privacy Shield Framework. We also encourage customers to anonymize all user IDs by hashing them before sending them to TypingDNA for added privacy.

On a monthly basis, we count the users who have been stored 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.

For Pro accounts, we accept all major credit cards. For Enterprise customers, additional options are available.

Annual subscriptions, as well as volume discounts, are available for Enterprise accounts. Get in touch with us to learn more.

For Developer and Pro accounts, a limited SLA is offered. Read the Standard Service Terms for more details, and check our uptime and status here.
Enterprise accounts have access to a full SLA with availability commitments depending on the chosen deployment.

We know how important support is, so we always try to reply as quickly as possible.
Developer and Pro accounts have access to our support department via email (support@typingdna.com).
Enterprise accounts can opt for a higher level of support, including guaranteed resolution times and 24/7 phone support.

The Authentication API is a flexible interface that allows clients to verify user identity by their typing through requests to a 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. The Authentication API is limited to enrolling and verifying typing patterns, and does not include managed OTP features (One Time Passwords/also known as 2FA codes).

Verify is a managed OTP replacement product. Designed with frictionless, cost-effective authentication in mind, Verify combines typing behavior verification with intelligent OTP features in one solution. In Verify, users authenticate with their typing behavior (by typing assigned words). OTP codes for identity verification are only leveraged in necessary scenarios, such as a typing failure, suspected fraud or initial enrollment. By deferring to OTP codes as a secondary factor, Verify improves UX while drastically reducing the number of SMS or Email OTP codes required to be sent.

Mobile sensor data is one of the factors taken into account in the verification of a user’s typing behavior. While our recorders are capable of generating typing patterns from user input on a mobile browser, the accuracy of the solution will depend on the availability of access to this sensor (accelerometer and gyrometer) data. Access varies by mobile browser, and in some instances requires manual user enablement. For the most consistently accurate results, users should verify from a desktop.

For more information, visit this article in the Help Center.