Learn how Cerbos and Keycloak differ in their key features, development activity, technology stack and community adoption, so you can decide which of these authorization & permissions tools is best for you.

Keycloak appears to have several advantages over Cerbos, particularly in popularity, growth and maturity. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
Keycloak significantly outpaces Cerbos in community adoption with 36,125 stars compared to 4,532 stars on GitHub. This 8.0x difference suggests Keycloak has a much larger and more active community. In terms of developer contributions, Keycloak has 8,766 forks, indicating strong developer engagement.
Keycloak is growing faster, adding 509 stars in the last 30 days (+1.4%) against adding 42 stars for Cerbos (+0.9%). Keycloak is both larger and pulling further ahead.
Both projects show recent activity, with Cerbos last updated 3 hours ago and Keycloak 1 hour ago.
Both tools share common technology foundations, being built with JavaScript, CSS, Bash, Python, Java. However, they differ in their additional technology choices: Cerbos uses Golang, Rust, PHP, Ruby, C# while Keycloak leverages Typescript, JSX, C.
Keycloak has been in development longer, starting 13 years ago, compared to Cerbos which began 5 years ago. This 7.8-year head start suggests Keycloak may have more mature features and established processes.
Both projects use the Apache-2.0 license, providing identical terms for usage and distribution.
Both tools serve similar use cases in Authorization & Permissions. However, they also have distinct specializations: Cerbos also focuses on Application Security while Keycloak extends into Authentication & SSO.

vs
Last 30 days
Last commit
Repository age
Version
License
Repository
Last 30 days
Last commit
Repository age
License
Repository