← Templates · Identity & Access
HA
Hanko
CommunityOpen-source authentication infrastructure built around passkeys, with passwords and social login as fallbacks.
| Runs | ghcr.io/teamhanko/hanko:v3.1.0 |
|---|---|
| Stack | go |
| Provisioned for it | postgres |
| Verified | Not yet |
Why deploy on Railyard
Railyard provisions postgres alongside it automatically — zero-downtime deploys, automatic backups and scaling come from the same platform, on a server you already pay for.
Deploying Hanko is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.
Good for
- Passkey-first login for a custom app without building WebAuthn yourself
- An auth backend for a Next.js/React app via Hanko Elements
- Replacing a bespoke password + 2FA flow with passkeys
Good to know
- Postgres is wired up automatically; the release phase runs migrations before boot
- If the image insists on a base config.yaml even with DATABASE_URL set, mount one onto a config volume — env vars are documented to override it either way