head to head · open source

Keycloak vs Logto

Keycloak has 36,832 GitHub stars, 8,941 forks, 3,292 open issues and last shipped yesterday. Logto has 14,580 stars, 1,206 forks, 183 open issues and last shipped yesterday. Keycloak leads on adoption by 153% (36,832 vs 14,580 stars). Keycloak is written in Java under Apache-2.0; Logto is written in TypeScript under MPL-2.0. Keycloak has attracted 24% as many forks as stars, Logto 8%. Keycloak was the more recently maintained of the two, and both are self-hostable with no licence fee.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

Keycloak ★ 37K Logto ★ 15K category Security & Privacy

← all 8884 open source comparisons

Side by side

Keycloak Logto
GitHub stars ★ 37K ★ 15K
License Apache-2.0 MPL-2.0
Written in Java TypeScript
Last push 2026-09-17 2026-09-17
Forks ⑂ 8.9K ⑂ 1.2K
Self-hosting Yes Yes
Data ownership Your server Your server

pick Keycloak if

  • You weight community size — 37K stars and counting
  • You want the Apache-2.0 license terms
  • Your stack matches Java
  • You value the larger contributor base for long-term maintenance

full Keycloak profile →

pick Logto if

  • You want the Logto feature set and don't need the biggest community
  • You prefer the MPL-2.0 license terms
  • Your stack matches TypeScript
  • You evaluated both and Logto fits your workflow better

full Logto profile →

About Keycloak

Keycloak is an open source identity and access management server, written in Java and licensed under Apache 2.0, that adds authentication and access control to applications and services, and it is intended for teams and organisations that want to own their user store rather than rent one.

read the full Keycloak overview →

About Logto

Logto is an open source authentication and authorization infrastructure for SaaS and AI applications. It is written in TypeScript, licensed under MPL 2.0, and positioned as an open alternative to Auth0. The project sits in the identity and access management ecosystem, where it provides a central service for login, consent, tokens, user directories, and access control.

read the full Logto overview →

More in Security & Privacy

Puter ★ 44K Mattermost ★ 39K Tailscale ★ 37K HashiCorp Vault ★ 36K JumpServer ★ 32K ProjectDiscovery ★ 31K

Related comparisons

keycloak vs jumpserver keycloak vs better-auth keycloak vs authentik keycloak vs supertokens keycloak vs zitadel keycloak vs projectdiscovery keycloak vs tracecat keycloak vs tirreno keycloak vs marble jumpserver vs better-auth jumpserver vs authentik better-auth vs authentik puter vs mattermost puter vs signal puter vs ente mattermost vs signal mattermost vs ente signal vs ente puter vs element puter vs fluxer puter vs vault mattermost vs vault puter vs unkey mattermost vs unkey

More Identity & Access Management (IAM) projects

Compare either of these against the rest of the Identity & Access Management (IAM) field.

Keycloak vs JumpServer Keycloak vs Better Auth Keycloak vs Authentik Keycloak vs SuperTokens Keycloak vs Zitadel Keycloak vs Ory Keycloak vs Hexclave Keycloak vs Permify Keycloak vs Authgear

Frequently asked questions

Is Keycloak or Logto more popular?

Keycloak has 36,832 GitHub stars and Logto has 14,580. Keycloak has the larger community by that measure.

Are Keycloak and Logto free?

Both are open source. Keycloak is licensed under Apache-2.0 and Logto under MPL-2.0. Neither carries a licence fee.

What is the difference between Keycloak and Logto?

Keycloak is written in Java and Logto in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, Keycloak or Logto?

Choose Keycloak if you want the larger community (36,832 stars) or its Apache-2.0 licence terms. Choose Logto if its feature set, stack or MPL-2.0 licence fits better. Both are self-hostable.