Open-source alternatives to Okta

authentik is a free, open-source Okta alternative: one sign-in for all your team’s apps, with two-step verification, users and groups and an app dashboard, on your own server. Okta charges per user each month; authentik’s open-source edition has no user fee, though it has fewer ready-made app connections and some business features need its paid Enterprise licence.

8 alternatives Free apps Our pick: authentik

At a glance

App Good for Code Import from Okta Ease of use
authentik Teams with several apps who want one login and two-step sign-in for all of them Code Open source Import from Okta No Some setup
Authelia Small teams and home labs that want one login with two-step sign-in for self-hosted apps that support OpenID Connect Code Open source Import from Okta No Some setup
Keycloak Organisations with several apps that want their own single sign-on, with someone technical to run it Code Open source Import from Okta No Some setup
Pocket ID Small teams who want one passkey sign-in for their own apps, with no passwords Code Open source Import from Okta No Some setup
VoidAuth Small teams and families who want one simple login, with passkeys and invitations, for their self-hosted apps Code Open source Import from Okta No Some setup
Casdoor Small teams and developers who want one login, with social and two-step sign-in, for several apps Code Open source Import from Okta Partly Some setup
Logto Businesses adding customer sign-in, single sign-on and roles to their own website, app or customer portal Code Open source Import from Okta No Some setup
ZITADEL Companies building their own apps that want sign-in for customers and staff, with organisations for business customers Code Open source Import from Okta No Some setup

Why look for an alternative to Okta?

Okta is a cloud identity service for companies: one sign-in for the apps your staff use, with two-step verification and a large catalogue of ready-made app connections.

Teams look for an alternative because Okta charges per user each month, which adds up quickly for a small team. Others want the accounts that unlock every app kept on their own server. authentik covers single sign-on, two-step verification and user management for your apps on a server you control, with no user fee in its open-source edition. Authelia is a lighter option for apps that support OpenID Connect, free with no paid edition, set up in text files rather than an admin screen. Pocket ID is another light choice for small teams: one passkey sign-in for apps that support OpenID Connect, with no passwords. VoidAuth is a similar small option, with invitations by link and every feature free. Keycloak is the long-established, larger option, with realms for separate user bases, for teams with someone technical to run it, and ZITADEL suits companies that also need sign-in for the apps they build. Casdoor can bring your Okta users across with its Okta syncer and sets up sign-in for common apps from its Marketplace. For customer sign-in in your own apps, Logto does the same job on your own server.

The alternatives, compared

authentik

Our pick

One login, with two-step sign-in, for all your team's apps.

Gives your team one sign-in for its apps through OpenID Connect, SAML, LDAP, SCIM and RADIUS, with two-step verification by authenticator app, passkey or security key, self-service password reset and an app dashboard. Its proxy puts a login in front of apps that have none. Okta is a managed service with far more ready-made app connections; in authentik each app takes a few steps to connect, and Google Workspace and Entra ID sync need the paid Enterprise licence.

What you gain
  • No per-user fee for single sign-on and two-step sign-in in the free edition
  • Your user accounts and sign-in records stay on your own server
  • Works with self-hosted apps and with apps that have no login support of their own
What is different
  • You connect each app yourself, with a guide for many common apps rather than a one-click catalogue
  • Google Workspace and Microsoft Entra ID sync, detailed audit logs and device login need the paid Enterprise licence
  • If authentik is down, nobody can sign in to the connected apps, so keep it backed up
Some setup Open source

One sign-in with two-step login for the apps you host yourself.

Gives your self-hosted apps one sign-in with two-step login through OpenID Connect, with passkeys, security keys, authenticator apps and Duo push, and it is very light on memory. It has no admin screen, no SAML and no catalogue of cloud app connections: users, apps and rules are edited in text files on the server.

What you gain
  • No fee per user; Authelia is free, with no paid edition
  • Your users' sign-ins and two-step devices stay on your own server
  • Passkeys, security keys and authenticator apps included
What is different
  • No admin screen; users, apps and email settings are edited in text files on the server
  • No SAML and no ready-made catalogue of connections to cloud apps
  • Each app takes a few steps to connect, in Authelia's settings file and in the app
Some setup Open source

Single sign-on for all your apps, with realms for staff and customers.

Gives your team single sign-on and single sign-out for apps that use OpenID Connect, OAuth 2.0 or SAML, with two-step sign-in by authenticator app, security key or passkey, LDAP and Active Directory, and social and company logins, with every feature in the free project. Like the others here it has no catalogue of ready-made app connections, its admin console uses technical terms such as realms and clients, and it has no proxy for apps without their own sign-in.

What you gain
  • No per-user fee, with every feature in the free project
  • Your users' accounts and sign-in records stay on your own server
  • Works with self-hosted apps and with LDAP or Active Directory you already run
What is different
  • You connect each app yourself, without a catalogue of ready-made app connections
  • The admin console uses technical terms such as realms and clients, so it takes time to learn
  • If Keycloak is down, nobody can sign in to the connected apps, so keep it backed up
Some setup Open source

One passkey sign-in for all your team's apps, with no passwords.

A much smaller single sign-on service: people sign in once with a passkey, by fingerprint, face scan, PIN or security key, and are signed in to every app that supports OpenID Connect, with groups deciding who may open which app. It has no passwords at all, no SAML, LDAP server or RADIUS, and no proxy for apps without their own sign-in, so it suits a small team's apps rather than a company's whole Okta setup.

What you gain
  • No per-user fee for single sign-on, and no paid edition
  • No passwords for your team to reuse, forget or have stolen
  • User accounts and sign-in records stay on your own server
What is different
  • Only passkeys, so everyone needs a phone, computer or security key that supports them
  • Only OpenID Connect, so apps that need SAML or have no sign-in of their own need an extra sign-in proxy
  • You connect each app yourself, with a guide rather than a one-click catalogue, and there is no device management
Some setup Open source

Simple self-hosted single sign-on, with passkeys and invitations.

The simpler choice for a small team: one login for self-hosted apps through OpenID Connect or a reverse-proxy login, with passkeys, authenticator codes, groups and invitations by link, and every feature free. It has no SAML, no social logins and no catalogue of ready-made business app connections, so it cannot replace Okta for SaaS apps, and it is a young project that has not been security-audited.

What you gain
  • No per-user fee and no paid tier, so every feature is in the free app
  • Your user accounts and sign-ins stay on your own server
  • A short setup that fits a small team and a handful of self-hosted apps
What is different
  • Apps connect by OpenID Connect or through a reverse proxy; there is no SAML and no catalogue of ready-made app connections
  • No "sign in with Google or Microsoft" and no import from Okta or JumpCloud
  • A young project with one main developer, and not security-audited
Some setup Open source

Single sign-on and one user list for all your apps, on your server.

Gives your apps one sign-in over OpenID Connect, SAML, CAS and LDAP, with passkeys, two-step sign-in, social and Microsoft Entra ID logins, groups, and roles and permissions. It can sync users in from Okta, Active Directory or Google Workspace, and its Marketplace sets up sign-in for apps such as Grafana, GitLab and Nextcloud in one step. It has far fewer ready-made app connections than Okta and no proxy for apps without a login, and some advanced features need a paid licence key.

Some setup Open source

Sign-in, single sign-on and user roles for your own apps.

Fits Okta's Customer Identity side rather than staff sign-in: it adds sign-in, sign-up, social logins, two-step verification, organisations and roles to your own website or app, and can let business customers sign in with their own Okta, Entra ID or Google Workspace account. It has no app dashboard, LDAP or catalogue of ready-made connections for the apps your team uses, so for that authentik is the better fit.

Some setup Open source

Sign-in, passkeys and single sign-on for your apps and customers.

Gives staff single sign-on through OpenID Connect, OAuth 2.0 and SAML, with passkeys, authenticator apps, security keys and LDAP, and a full audit trail of every change. It is built mainly for adding sign-in to apps you make, with organisations for business customers, so it has no catalogue of ready-made workforce app connections and no login proxy.

Some setup Open source

Moving from Okta

Only Casdoor has an Okta importer. authentik, Authelia, Keycloak, ZITADEL, Pocket ID, Logto and VoidAuth have none. For authentik, create your groups, then bring people in from your existing directory: sync them from Active Directory or LDAP, or add Okta as a login source so they sign in with their Okta account during the switch. Connect one app at a time, using authentik's integration guides, and test each before you move the next. Set up two-step verification and keep an admin login that does not depend on authentik, then turn off each app's Okta connection once it works. For Authelia, add each person to its users file and each app as an OpenID Connect client in its settings file, using Authelia's per-app guides, then switch the app's sign-in over and test it before the next. For Keycloak, connect it to your Active Directory or LDAP, or add Okta as an identity provider so people can sign in with Okta during the switch, then add each app as a client and test it before the next. For ZITADEL, create a project, add each app to it, and bring people in through LDAP or its user import API. With Pocket ID, check first that every app you need supports OpenID Connect sign-in and that everyone has a device or security key that can hold a passkey; add people by hand, through signup links or by syncing from LDAP, send each one a one-time login code to create their first passkey, then connect one app at a time.

With VoidAuth, invite each person by link so they set their own password or passkey, then connect your OpenID Connect apps one at a time with the project's setup guides. Apps that support only SAML have to stay on Okta or move to authentik or Casdoor.

With Casdoor, add an Okta syncer to bring your users across through Okta's API; passwords do not come with them, so plan a reset or a social login. Connect each app from Casdoor's Marketplace or by hand with its OpenID Connect or SAML details, and test it before switching off Okta for that app.

If you use Okta for your customers' sign-in rather than your staff's, Logto is the closer fit. Add your app in Logto's admin console, follow the guide for your framework to swap Okta's sign-in library for Logto's SDK or any OpenID Connect library, connect an email service for sign-in codes, and brand the sign-in pages. A developer creates existing users through Logto's Management API.

Questions

What is the best open-source alternative to Okta?

Start with authentik. All 8 are free and open source.

Does authentik support SAML and OpenID Connect like Okta?

Yes. The free edition supports OpenID Connect, SAML, LDAP, SCIM, RADIUS, Kerberos and a proxy for apps without their own sign-in.

Can I bring my Okta users into Casdoor?

Yes, partly. Casdoor's Okta syncer reads your users through the Okta API and adds them to Casdoor. Their passwords and app connections do not come across.

Which authentik and Casdoor features are paid?

authentik's and Casdoor's free editions cover single sign-on, two-step verification and user management. authentik's paid Enterprise licence adds Google Workspace and Entra ID sync, enhanced audit logging, device login and ticket support. A paid Casdoor licence key adds features such as security policies, push sign-in approval, more than one user sync and access reviews. Authelia, Pocket ID and VoidAuth have no paid edition, and Keycloak and ZITADEL have every feature in their free projects.

Should I choose authentik, Authelia, Keycloak, ZITADEL, Casdoor, Pocket ID or VoidAuth?

Choose authentik if you want an admin screen, SAML, LDAP or a login in front of apps that have none. Choose Keycloak if you need several separate user bases on one server and have someone technical to run it. Choose ZITADEL if you also build your own apps and need sign-in for customers. Choose Casdoor if you want to bring your Okta users across with its Okta syncer, or set up sign-in for common apps in one step from its Marketplace. Choose Authelia if your apps support OpenID Connect and you want something very light that you set up in text files. Choose Pocket ID if your apps support OpenID Connect and you want passkey sign-in with no passwords, managed from a simple admin screen. Choose VoidAuth if your apps support OpenID Connect and you want a smaller app with an admin screen, invitations by link and a quick setup.

Should I choose authentik or Logto?

authentik if you want one sign-in for the apps your team uses, as with Okta Workforce Identity. Logto if you are adding customer sign-in to your own website, app or SaaS product, as with Okta Customer Identity.

What happens if my sign-in server goes down?

Nobody can sign in to the connected apps until it is back, whichever of these apps you use. Keep backups and a fallback admin login for each important app.

Are these Okta alternatives really free?

Authelia is free under the Apache-2.0 licence, with no paid edition, and so are Pocket ID under the BSD-2-Clause licence and VoidAuth under the AGPL-3.0 licence. Keycloak is free under the Apache-2.0 licence, with every feature in the free project; Red Hat sells a supported build. ZITADEL is free under the AGPL-3.0 licence, with the same code as ZITADEL Cloud; its makers sell support and a commercial licence. authentik's open-source edition is free under the MIT licence, Logto's under the MPL-2.0 licence and Casdoor under the Apache-2.0 licence, with no fee per user. authentik's makers sell an Enterprise licence that adds features such as Google Workspace and Entra ID sync, enhanced audit logging and ticket support, Logto's sell a licence that adds extras such as hiding its branding, and Casdoor's sell licence keys that unlock advanced features such as security policies and access reviews. To run any of them you need Cloudgate and a server: use hosted Cloudgate, which can also provide the server, or install Cloudgate on a server of your own for free. Cloudgate's plans and prices are at cloudgate.octabyte.io/pricing.

Do I need a developer to replace Okta?

No. Cloudgate installs the app you choose on your server and gives it a secure web address, and you use it in your browser instead of Okta.