Hanko is authentication built for the passwordless era: passkeys (WebAuthn) are the default, not an add-on, with email passcodes, OAuth logins and passwords available where you still need them.
It ships as a compact Go backend plus polished, framework-agnostic web components — drop `<hanko-auth>` into your app and you have modern login, sessions and user management. Self-host it and your user database answers to no third party.
AGPL-3.0 licensed (with a hosted cloud available), Hanko is the clean open alternative to renting your auth from Clerk or Auth0 — especially for teams that care where credentials live.
WebAuthn passkeys by default, plus passcodes, OAuth providers and optional passwords.
Prebuilt, themeable web components for login and profile — minutes to integrate.
Sessions, JWTs, user admin and audit logs handled by the backend.
Own your user data outright — a Go binary and Postgres is all it takes.
Yes — Hanko is open source under AGPL-3.0 and free to self-host. Hanko Cloud offers a managed option with a free tier.
Passkeys are phishing-resistant WebAuthn credentials that replace passwords with device biometrics — Face ID, Touch ID, security keys. Hanko makes them the default login.
Clerk is a polished closed SaaS; Hanko gives you comparable modern auth UX, open source and self-hostable, so credentials live on your infrastructure.
Yes — passwords, email passcodes and OAuth providers are all supported alongside passkeys.
Docker with the Hanko backend and PostgreSQL — a small VPS is plenty for most apps.
Open-source notification infrastructure.
Open scheduling infrastructure.
Open-source web + product analytics.
Claim Hanko to add screenshots, respond to reviews and reach founders comparing tools — free to start.