Learn how Cerbos and Permify 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.

Cerbos appears to have several advantages over Permify, particularly in growth and maturity. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
Both tools have similar popularity levels, with Cerbos having 4,532 stars and Permify having 5,935 stars on GitHub. In terms of developer contributions, Permify has 323 forks, indicating moderate developer engagement.
Cerbos is growing faster, adding 42 stars in the last 30 days (+0.9%) against adding 19 stars for Permify (+0.3%). Cerbos is the smaller project of the two, so it is closing the gap rather than extending a lead.
Both projects show recent activity, with Cerbos last updated 3 hours ago and Permify 7 hours ago.
Both tools share common technology foundations, being built with JavaScript, Bash, Python, Golang, Java. However, they differ in their additional technology choices: Cerbos uses CSS, Rust, PHP, Ruby, C# while Permify leverages Typescript, JSX.
Cerbos has been in development longer, starting 5 years ago, compared to Permify which began 4 years ago. This 1.3-year head start suggests Cerbos may have more mature features and established processes.
The projects use different licenses: Cerbos is licensed under Apache-2.0 while Permify uses AGPL-3.0. Consider the licensing requirements when choosing for your project.
Both tools serve similar use cases in Authorization & Permissions. However, they also have distinct specializations: Cerbos also focuses on Application Security.

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