Learn how Authentik and Cerbos 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.
Stars
Forks
Last commit
Repository age
Self-hosted
Auto-fetched .

Stars
Forks
Last commit
Repository age
License
Auto-fetched .

Authentik appears to have several advantages over Cerbos, particularly in popularity, maturity and features. Consider your specific needs regarding popularity, activity, technology, maturity, licensing and features when making your decision.
Authentik significantly outpaces Cerbos in community adoption with 21,151 stars compared to 4,368 stars on GitHub. This 4.8x difference suggests Authentik has a much larger and more active community. In terms of developer contributions, Authentik has 1,560 forks, indicating strong developer engagement.
Both projects show recent activity, with Authentik last updated 32 minutes ago and Cerbos 1 day ago.
Both tools share common technology foundations, being built with JavaScript, CSS, Bash, Python, Golang, Rust. However, they differ in their additional technology choices: Authentik uses Typescript, JSX, Django while Cerbos leverages PHP, Java, Ruby, C#.
Authentik has been in development longer, starting 6 years ago, compared to Cerbos which began 5 years ago. This 1.2-year head start suggests Authentik may have more mature features and established processes.
Cerbos is licensed under Apache-2.0, while Authentik's license terms are not publicly specified.
Both tools serve similar use cases in Authorization & Permissions. However, they also have distinct specializations: Authentik also focuses on Authentication & SSO while Cerbos extends into Application Security.
Authentik provides self-hosting options for complete data control and customization, while Cerbos may be primarily cloud-based or require different deployment approaches.