Sign In. Without a password.

Add Fingerprint, Face ID and Security keys to your existing web app

Built on modern browser standards and open source

A simple API for passwordless sign in to your web app

TouchID — FaceID — Windows Hello and more. Use our API to add passwordless sign in to your app in minutes instead of weeks.

Built on standards that makes sign in fast and unphisable. Protect your users and make "Forgot password" a thing of the past.

Passwordless demo

This is how passwordless sign in can look like on your web app, enabled by our api.


More examples

WebAuthn and FIDO2 made easy

Get started with just a few lines of code

Hit the ground running with our Passwordless API. It's the fastest and easiest way to get started and try passwordless in your app.

When you need more control and customization, you can move to our self-hosted API (coming later) or utilize the .net core fido2 library to build it straight into your applications/server.

Features of the API

  • Simple API with little code required
  • Passwordless signup and signin
  • Easy to integrate to your existing user system
  • Secure storage, data is encrypted at rest
  • Extensible with APIs for managing credentials
  • EU GDPR Compliance



$0 / month

Perfect for experiments and non serious side projects

  • 10 accounts limit
  • 10 sign ins/day
  • 2 different domains allowed (RP IDs)
  • No backups

Independent developer

$9 / month

For non businesses and projects

  • 1000 accounts limit
  • 1000 sign ins/day*
  • 10 different domains allowed (RP IDs)
  • Monthy backups

Business - recommended

$249 / month

For businesses and SaaS apps.

  • 500 000 accounts limit
  • 1 000 000 sign ins/day*
  • 10 different domains allowed (RP IDs)
  • Weekly backups
  • Self hosting available
  • Email support


$2499 / month

For professional businesses

  • 500 000+ accounts limit
  • 1 000 000+ sign ins/day*
  • Unlimited different domains allowed (RP IDs)
  • Daily backups
  • Self hosting available
  • Isolated deployment

What is FIDO2 / WebAuthn?

FIDO2 / WebAuthn is a modern open authentication standard, supported by browsers and many large tech companies such as Microsoft, Google etc. The main driver is to allow a user to login without passwords, creating passwordless flows or strong MFA for user signup/login on websites. The standard is not limited to web applications with support coming to Active Directory and native apps. The technology builds on public/private keys, allowing authentication to happen without sharing a secret between the user & platform. This brings many benefits, such as easier and safer logins and makes phishing attempts extremely hard.


The following chapter will explain some of the concepts mentioned in the 3 scenarios

Fido2 vs WebAuthn?

Fido2 is the umbrella term and branding of two new w3c standards: WebAuthn and CTAP2. WebAuthn is the JS API that allows browser to talk to the operating system to generate assertions and CTAP2 is the API that allows the operating system to talk to Authenticators (usb security keys etc)

Relying Party (RP)

The Relying Party - often called RP - is the server that the browser communicates with. If you are a developer reading this, the Relying Party ID is probably your domain.

User Verification

A FIDO2 server (a.k.a the Relying Party, RP) can ask the authenticator to verify the user. This can be done either via PIN code, biometrics or other factors that securely verifies that it's the expected human in front of the device, not just any human.

Resident Credentials (RK)

The resident credential is a credential that can be accessed simply with RP ID. When not using RK you will have to provide a list of the credentials (array of ID's) you want the authenticator to use. With RK you don’t need it because the authentication will locate all RK's (only RK credentials), and for each of them generate the assertion over the challenge and return all of them to the client. The client then will display all of the credentials to the user and user will pick one, thus returning selected credential to the relying party.