head to head · open source

Keycloak vs pocket-id

Keycloak has 36,855 GitHub stars, 8,942 forks, 3,292 open issues and last shipped yesterday. pocket-id has 9,222 stars, 310 forks, 98 open issues and last shipped yesterday. Keycloak leads on adoption by 300% (36,855 vs 9,222 stars). Keycloak is written in Java under Apache-2.0; pocket-id is written in Go under BSD-2-Clause. Keycloak has attracted 24% as many forks as stars, pocket-id 3%. Keycloak was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (oidc), so they are genuine substitutes rather than adjacent tools.

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 pocket-id ★ 9.2K category Security & Privacy

← all 15422 open source comparisons

Side by side

Keycloak pocket-id
GitHub stars ★ 37K ★ 9.2K
License Apache-2.0 BSD-2-Clause
Written in Java Go
Last push 2026-09-18 2026-09-18
Forks ⑂ 8.9K ⑂ 310
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 pocket-id if

  • You want the pocket-id feature set and don't need the biggest community
  • You prefer the BSD-2-Clause license terms
  • Your stack matches Go
  • You evaluated both and pocket-id fits your workflow better

full pocket-id 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 pocket-id

Pocket ID is a self hosted, OpenID Connect Certified™ and OAuth 2.0 provider, written in Go, that authenticates users with passkeys and passwords never, aimed at anyone who wants single sign on for their own applications without standing up a heavyweight identity platform.

read the full pocket-id overview →

More in Security & Privacy

PayloadsAllTheThings ★ 81K Puter ★ 44K Mattermost ★ 39K Tailscale ★ 37K HashiCorp Vault ★ 36K Anthropic-Cybersecurity-Skills ★ 33K

Related comparisons

keycloak vs jumpserver keycloak vs better-auth keycloak vs authentik keycloak vs vault keycloak vs projectdiscovery keycloak vs tracecat keycloak vs tirreno keycloak vs marble supabase vs better-auth jumpserver vs better-auth jumpserver vs authentik better-auth vs authentik jumpserver vs teleport puter vs mattermost mattermost vs nextcloud puter vs signal puter vs ente mattermost vs signal mattermost vs ente mattermost vs zulip signal vs ente puter vs vault mattermost vs vault vault vs infisical

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 authelia Keycloak vs Authentik Keycloak vs casbin Keycloak vs Sa-Token Keycloak vs hydra Keycloak vs SuperTokens Keycloak vs Zitadel Keycloak vs Logto Keycloak vs Ory Keycloak vs cas

Frequently asked questions

Is Keycloak or pocket-id more popular?

Keycloak has 36,855 GitHub stars and pocket-id has 9,222. Keycloak has the larger community by that measure.

Are Keycloak and pocket-id free?

Both are open source. Keycloak is licensed under Apache-2.0 and pocket-id under BSD-2-Clause. Neither carries a licence fee.

What is the difference between Keycloak and pocket-id?

Keycloak is written in Java and pocket-id in Go. 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 pocket-id?

Choose Keycloak if you want the larger community (36,855 stars) or its Apache-2.0 licence terms. Choose pocket-id if its feature set, stack or BSD-2-Clause licence fits better. Both are self-hostable.