What is Gatekeep?
Hosted authentication built on passkeys. Gatekeep runs your sign-in page, enrolls and verifies your users' passkeys, and hands your app a signed OpenID Connect token. You don't store passwords, build reset flows or run an auth server.
What happens if a user loses their phone?
They choose "Lost your passkey?", get a one-time link by email and set up a passkey on their new device. Recovering revokes every old passkey, so the lost phone can't sign in any more. Synced passkeys (iCloud Keychain, Google Password Manager, 1Password) usually survive a lost device anyway.
Do I need your SDK?
No. Gatekeep speaks standard OpenID Connect with PKCE, so Auth.js, Passport, Spring Security, Authlib, ASP.NET Core and any other conformant library work out of the box. Give them your issuer URL and client ID.
Which browsers and devices work?
Every current browser supports passkeys: Chrome, Safari, Firefox and Edge on macOS, Windows, iOS, Android, ChromeOS and Linux. Users can also scan a QR code to use the passkey on their phone from someone else's computer.
What counts as a monthly active user?
Anyone who signs in to one of your apps at least once in a calendar month. Signing in many times still counts once, and silent single sign-on across your apps doesn't add more. Free covers up to 5,000.
Why should I use my own domain?
Passkeys are bound to the domain they were created on. If your users enroll on auth.yourapp.com, those passkeys keep working no matter what happens behind it. Custom domains start on Essentials, and we recommend setting one up before you launch.
Can I move off Gatekeep later?
Your apps only speak standard OIDC, so swapping providers is a config change in your app, not a rewrite. On a custom domain, your users' passkeys are tied to your domain, not ours.
Is it available now?
Gatekeep is in early access. Join the list and we'll set up your apps with you. Early-access accounts are free until general availability.