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.

Authentik appears to have several advantages over Cerbos, particularly in popularity, growth, maturity, licensing and features. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
Authentik significantly outpaces Cerbos in community adoption with 24,595 stars compared to 4,532 stars on GitHub. This 5.4x difference suggests Authentik has a much larger and more active community. In terms of developer contributions, Authentik has 1,886 forks, indicating strong developer engagement.
Authentik is growing faster, adding 2,293 stars in the last 30 days (+10%) against adding 42 stars for Cerbos (+0.9%). Authentik is both larger and pulling further ahead.
Both projects show recent activity, with Authentik last updated 1 hour ago and Cerbos 3 hours 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 7 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.
Authentik uses the MIT license, which is more permissive than Cerbos's Apache-2.0 license, potentially offering greater flexibility for commercial use and integration.
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.

vs
Last 30 days
Last commit
Repository age
Version
License
Repository
Last 30 days
Last commit
Repository age
License
Self-hosted
Repository