New technologies

Passkeys: signing in without passwords, explained

What passkeys are, why they resist phishing better than passwords and SMS codes, what changes for users, and a checklist to add them to your app or SaaS.

Your users forget their passwords, reuse them on other sites and sometimes type them into a page that only looks like yours. SMS codes help, but they can be intercepted or handed over to a convincing fake page too. Passkeys offer another way in: the user unlocks their phone or computer with a fingerprint, their face or a PIN, and they are signed in, with no password to remember or to steal.

In this article, we explain what a passkey is, why it resists phishing better than passwords and one-time codes, what changes for your users, and how to add passkeys to a business application or a SaaS (software as a service) without locking anyone out. A rollout checklist closes the article.

What is a passkey?

A passkey is a sign-in credential made of two linked keys. When a user creates one for your application, their device generates a private key, which stays with the user, and a public key, which your server stores. At each sign-in, your server sends a random challenge; the device signs it with the private key, and your server checks the signature with the public key. No secret travels over the network, and no secret sits in your database.

Before signing, the device asks the user to prove it is them: a fingerprint, a face scan or the screen-lock PIN. That check happens on the device. The fingerprint or face never reaches your server; you only receive the signed answer.

Passkeys rest on open standards rather than one vendor’s product: FIDO2, from the FIDO Alliance (Fast IDentity Online), an industry body that includes the main platform makers, and WebAuthn (Web Authentication), the W3C standard that lets a web application talk to the user’s device.

Synced passkeys and device-bound passkeys

Synced passkeys are stored by a password manager or the platform’s keychain and copied, encrypted, to the user’s other devices: a new phone gets them back. Device-bound passkeys live on one piece of hardware, typically a USB or NFC security key, and never leave it. They suit administrators and high-risk accounts, at the cost of more care when a key is lost.

Passkeys vs passwords and SMS codes: why phishing gets harder

The decisive feature is that a passkey is tied to your domain. The device will only use it on the site it was created for. If a user lands on a look-alike page at a slightly different address, there is simply no passkey to offer: they cannot hand it over, even by mistake. A password or a six-digit code, by contrast, can be typed anywhere.

Password Password + SMS code Password + authenticator app Passkey
Can be typed into a fake site Yes Yes, both Yes, both No: tied to the domain
Useful to an attacker if your database leaks Yes, if weakly protected The password part The password part No: only public keys are stored
Can be reused on other sites Often The password, yes The password, yes No: one passkey per site
Something to remember Yes Yes Yes No: the device unlock
Depends on the phone network No Yes No No

This does not make accounts “unhackable”. A compromised device, a weak recovery process or a session stolen after sign-in remain real risks. Passkeys remove the most common route, stolen or phished credentials, and leave the rest of your security work in place. Our guide to cybersecurity for SMEs covers the other basics. Machines are leaving passwords behind too: Microsoft 365 ends password-only SMTP sending by default at the end of December 2026, so printers and software that send email need another way to sign in.

What changes for your users: devices, sync and recovery

Signing in on another device

If the passkey is synced, it is already on the user’s other devices with the same account (the same Apple, Google or Microsoft account, or the same password manager). If not, the computer can show a QR code: the user scans it with their phone, the phone checks over Bluetooth that it is nearby, and the sign-in completes. It surprises people the first time, so a short help page pays off.

Switching ecosystems

Someone who changes phone brand or password manager may need to create new passkeys. Moving passkeys between providers is being standardised and already possible in some cases, but support varies. The simple answer: let each user register several passkeys, and make adding one easy once signed in.

Losing a phone

With synced passkeys, the user restores their account on a new device and the passkeys come back. With a device-bound key, they need a second key or another way in. Your recovery path is now your weakest point: if anyone can reset an account with an email link alone, a phisher will attack that link rather than the passkey.

As of October 2026, current versions of the main operating systems and browsers, and several password managers, support passkeys, but syncing and cross-device behaviour still differ from one platform to another. Check the current support for the devices your users actually have before you promise anything.

How to add passwordless authentication to a business app or SaaS

Adding passkeys is rarely a rebuild: it is a new sign-in method next to your existing ones, introduced in steps.

Start alongside existing logins

Keep passwords at first. After a normal sign-in, invite users to “create a passkey for faster sign-in”, and let the browser suggest passkeys in the username field (passkey autofill). Users who never adopt them lose nothing. Later, you can require passkeys for one group only, such as administrators.

Design the recovery path first

Before launch, decide what happens when someone has lost every device: a second registered passkey, one-time recovery codes given at set-up, or an administrator reset with identity checks for business accounts. Whatever you choose, alert the user by email each time a passkey is added or removed.

Business customers and single sign-on

If your customers are companies that sign in through their own identity provider (single sign-on), that provider may already handle passkeys. In that case, your job is to support single sign-on properly, not to duplicate it. Our SaaS security checklist covers what larger customers usually ask for.

Choose the domain carefully

A passkey is bound to a domain (in WebAuthn terms, the relying party ID). If you move your application from app.example.com to example.io later, existing passkeys stop working there. Settle the domain early, ideally while you launch your SaaS MVP, and use a well-maintained WebAuthn library for your language rather than writing the cryptography yourselves.

Rollout checklist

Use this list before you switch passkeys on for real users:

  • The domain (relying party ID) is final and documented.
  • A maintained WebAuthn library is used, and kept up to date.
  • Each user can register several passkeys, name them, see when each was last used and delete one.
  • Passkey autofill is offered in the sign-in field, with the password still available.
  • The recovery path is written down and is no weaker than the passkey for sensitive accounts.
  • Support staff have a short procedure for “I lost my phone” and “I changed phone brand”.
  • Sign-in has been tested on the browsers and devices your users actually have, including the QR-code route.
  • Administrators are the first group to require passkeys.
  • You track how many users have created a passkey and how often sign-in fails, and adjust the prompts.
  • Single sign-on customers can keep their own identity provider.

This article gives general, practical guidance as of October 2026. Platform support and recovery behaviour change often: check the current situation, and have your design reviewed by a security professional before you rely on it.

Frequently asked questions

Do passkeys store my fingerprint or face?

No. The fingerprint or face scan only unlocks the private key on your own device, like your screen lock. The website never receives your biometric data: it receives a signature it checks with the public key it holds. If your device has no biometric sensor, its PIN or password does the same job.

Do passkeys replace two-factor authentication?

In most cases, yes. A passkey already combines two factors: something you have (the device holding the private key) and something you are or know (the fingerprint, face or PIN that unlocks it). Many services therefore skip the extra code after a passkey sign-in. Keep two-factor authentication for password users.

Can a passkey be stolen?

It is much harder than stealing a password. The private key stays on the device or in the password manager’s encrypted sync, and it is never typed, so a phishing page cannot collect it. The realistic risks lie elsewhere: a takeover of the account that syncs the passkeys, malware on an unlocked device, or a weak recovery process.

In short

A passkey replaces a typed secret with a key pair kept by the user’s device and unlocked by a fingerprint, a face or a PIN. Because it only works on the right domain and leaves nothing useful in your database, it resists phishing far better than passwords and SMS codes. For users, the questions are devices, sync and recovery. For your product, the work is a careful rollout next to existing logins, with the recovery path designed first.

Thinking about passkeys for your application or your SaaS? Book a free 30-minute discovery call: together, we look at how your users sign in today and how to add passkeys without locking anyone out. You can also see how we approach SaaS development.

Related servicesSaaS productsCustom softwareWebsites and web apps

Have a project in mind?

Let’s talk about it on a 30-minute discovery call, free and with no obligation.

Book a discovery call

Further reading

All articles