# What are self-hosted alternatives to Okta or Auth0?

Canonical page: https://launchinyourcloud.com/questions/okta-auth0-alternatives/

[Keycloak](/directory/keycloak/), [ZITADEL](/directory/zitadel/) and [authentik](/directory/authentik/) have documented self-hosted identity deployments. Compare protocols, integrations, user lifecycle and edition scope. Plan high availability, recovery, administrator access and staged upgrades for this critical application dependency.

Answer page: https://launchinyourcloud.com/questions/okta-auth0-alternatives/
Answer reviewed: 2026-11-21

- [Identity and access management directory](/categories/identity-access-management/)
- [SSO and SCIM definitions](/glossary/#sso)


## Test identity as a production dependency

- Validate required federation protocols, application integrations, account lifecycle, group mapping and administrative roles.
- Exercise high availability, backups, restore, key rotation, emergency administrator access and upgrade rollback.
- Identify mail, SMS, social login, external directories and other connected services. A self-hosted identity server does not relocate these dependencies.

## Verify both entry and removal of access

Test browser and API authentication separately, including disabled users, revoked sessions and unavailable upstream services. Check provisioning direction and supported SCIM operations rather than assuming they follow from SSO. Stage identity changes with the applications that depend on them.

## Reviewed listing references

These are illustrative candidates, not a ranking or a feature-parity claim.

### authentik

Identity provider for centralized authentication and access policies across connected applications.

Operations: Customer manages identity data, database, keys, policies, outposts, backups, network exposure and security upgrades.
License: MIT for the upstream core and client JavaScript; authentik/enterprise code is separately licensed.
Scope: The reviewed Compose path targets tests and smaller production setups. The default worker configuration can mount the Docker socket; review the documented permissions and outpost architecture. External identity, email and application endpoints remain separate. The 2026.8.6 patch addresses outpost refresh, cleanup, SAML error handling and WebAuthn signature selection when FIPS is enabled. When moving from an older minor release to 2026.8, verify the reverse proxy's address is trusted and that it sends the required forwarding headers before upgrading.
Listing and sources: https://launchinyourcloud.com/directory/authentik/
Reviewed: 2026-11-20

### Keycloak Self-Hosted

Identity and access management for application sign-on, federation and authorization.

Operations: Customer manages identity-server availability, configuration, updates, database and backups.
License: Open-source project; commercial support/distribution arrangements are separate
Scope: The official guides cover physical/virtual servers, containers and Kubernetes. Development defaults are separate from the production configuration. Connections to external identity providers are customer-configured; hosting the server does not eliminate those dependencies. Keycloak 26.8.2 is a security release addressing authentication, token issuance and revocation, authorization, account takeover, admin API, stored XSS, denial-of-service, and bundled Brotli issues. Review the migration guide and upgrade to 26.8.2 or later.
Listing and sources: https://launchinyourcloud.com/directory/keycloak/
Reviewed: 2026-11-17

### ZITADEL Self-Hosted

Application identity platform that can run as a self-operated service with its own PostgreSQL database.

Operations: Customer manages identity storage, cryptographic keys, proxy/TLS, backups, email/SMS providers and updates.
License: GNU Affero General Public License version 3 for the reviewed upstream code; commercial products and agreements are separate.
Scope: The Compose guide is a starting point for a homelab or semi-production installation. The current contribution guide states that engineering focus on next-generation work limits community PR review capacity for this codebase; evaluate the supported release roadmap. External identity and message providers remain separate. ZITADEL v4.20.4 enables PKCE by default for Google, GitHub, GitLab, and Azure AD identity providers and hardens SMS OTP and password history. Revalidate external IdP callbacks and authentication policy after upgrading. ZITADEL v4.20.5 fixes a Login V2 MFA bypass in which a first-factor-only session could add a new authenticator even when a second factor was already configured. Upgrade and verify authenticator-enrolment policy.
Listing and sources: https://launchinyourcloud.com/directory/zitadel/
Reviewed: 2026-11-19

