Keycloak vs Vaultwarden
Keycloak, Vaultwarden compared on license, free-edition limits, deployment and project health. Change a project below to compare something else.
| Keycloak | Vaultwarden | |
|---|---|---|
| Category | Security | Security |
| License | Apache License 2.0Open source (OSI) | GNU Affero General Public License v3.0Open source (OSI) |
| Free edition | Not confirmed | Not confirmed |
| Deployment | Self-hosted | Self-hosted |
| Self-hosting setup | Needs a database | Single container |
| SSO / SAML | Free | Not confirmed |
| Role-based access control | Free | Free |
| Audit logs | Free | Free |
| Multi-user / teams | Free | Free |
| Backups and restore | Not confirmed | Not confirmed |
| API access | Free | Free |
| Support SLA | Not confirmed | Not confirmed |
| GitHub stars | 37k | 69k |
| Last release | Oct 1, 2026 | Oct 5, 2026 |
| Alternative to | Auth0, Okta | 1Password, Bitwarden |
In short
- Keycloak is licensed Apache License 2.0 (open source (osi)). Free edition: not confirmed.
- Vaultwarden is licensed GNU Affero General Public License v3.0 (open source (osi)). Free edition: not confirmed.
Each project page lists the official sources behind these answers. Where the official pages do not say, the table shows “Not confirmed”.