Authentication and authorization
Authentication answers who a user is: passwords, passkeys, social login, MFA, OAuth, and SSO. Authorization answers what that user may do, such as edit a document or invite organization members. Auth0 covers both layers to some extent. Hanko, Keycloak, ZITADEL, Logto, SuperTokens, Authgear, and Better Auth primarily handle authentication and identity; Permify and Cerbos focus on authorization and must be combined with an identity provider.
Full IAM services and application frameworks
Keycloak, authentik, ZITADEL, Logto, and Authgear operate as identity services that applications connect to through protocols such as OIDC and SAML. Better Auth runs inside a TypeScript application and uses infrastructure the application controls. This avoids a separate identity server but puts more authentication responsibility inside the application stack.
Passkey-first authentication
Hanko supports passkeys alongside passwords, email codes, MFA, and social authentication. Pocket ID intentionally makes passkeys the only user authentication method, making it a lightweight fit for small self-hosted environments that want to avoid passwords.
Enterprise SSO and federation
For workforce SSO, compare support for SAML, OIDC, SCIM, LDAP, Active Directory, organizations, and multi-tenancy. Keycloak and authentik are strong for workforce and enterprise federation. ZITADEL and Logto are attractive for modern B2B SaaS applications.
Open-source core and commercial features
Check the exact license and feature boundaries before choosing. authentik has an MIT-licensed core alongside Enterprise functionality; SuperTokens has Apache-2.0 core with separately licensed ee components; Ory's Apache-2.0 core coexists with commercial enterprise features. ZITADEL uses AGPL-3.0 with limited directory exceptions, while the other projects have their own stated licenses and terms.