Typing biometrics authentication service for advanced integrations
Starter
Free
100 users
No credit card needed
Pro
Starting from $1/user/month
Unlimited users
Standard SLA
Enterprise
Custom
Full SLA provided
Enterprise-level support
High standards
We strive to innovate and contribute to the biometrics industry while driving efforts to achieve the highest standards for our clients.
Frequently asked questions
What is the difference between Starter and Pro accounts?
The Starter account is free to use, but is limited to 100 users each month. It’s designed to get you familiar with the TypingDNA Authentication API technology. The Pro account is designed for applications that have more than 100 users and is billed monthly based on usage.
When should I opt for an Enterprise account?
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.
What are the deployment options?
Starter 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.
What about security and privacy?
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.
How is usage measured for billing?
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.
Do you offer a discount for External users/Customers that may log in fewer times than Internal users/Employees?
Yes. We can offer you a significant discount to authenticate External users/Customers, which normally authenticate fewer times a month than Internal users/Employees. Please send us an email with your use case, volume and number of authentications per user per month so that we can offer you a great discount.
Do you offer annual subscriptions? What about volume discounts?
Annual subscriptions, as well as volume discounts, are available for Enterprise accounts. Get in touch with us to learn more.
What SLA is provided?
For Starter 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.
What support does TypingDNA offer?
We know how important support is, so we always try to reply as quickly as possible.
Starter 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.
What is the difference between Authentication API and Verify 2FA?
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) among other things.
Verify 2FA is a product that uses the Authentication API as a core technology but has multiple other features and limitations. There is a standard/stand alone version and an OIDC version (for IAM platforms such as Okta, Ping, etc). The standard Verify 2FA solution is a managed OTP replacement product for companies that don’t use an external IAM platform but want to add a robust 2FA to their login systems. 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 4 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 2FA improves UX while drastically reducing the number of SMS or Email OTP codes required to be sent.
The Verify 2FA OIDC integration is a particular case of Verify 2FA that does not use OTPs as Root of Trust, but integrates with other platforms (such as Okta or Ping Identity) and allows the user to enroll and login from the integrated platform. In this case Verify 2FA is a 2FA/MFA method that can be used as an authenticator.
Is mobile authentication quality similar to the desktop version?
It depends. 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 app or browser, the accuracy of the solution will depend on the availability of access to this sensor (accelerometer and gyrometer) data. For the most consistently accurate results, users should verify from a desktop or if you really have to allow mobiles, we recommend the in-app integrations (not browser based).
Talk to us
Let us show you a demo and talk about your needs