Learn how Cerbos and Ory 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
License
Auto-fetched .

Stars
Forks
Last commit
Repository age
License
Self-hosted
Auto-fetched .

Ory 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.
Ory significantly outpaces Cerbos in community adoption with 13,593 stars compared to 4,367 stars on GitHub. This 3.1x difference suggests Ory has a much larger and more active community. In terms of developer contributions, Ory has 1,127 forks, indicating strong developer engagement.
Both projects show recent activity, with Cerbos last updated 1 day ago and Ory 1 day ago.
Both tools share common technology foundations, being built with JavaScript, Bash, Golang. However, they differ in their additional technology choices: Cerbos uses CSS, Python, Rust, PHP, Java, Ruby, C#.
Ory has been in development longer, starting 8 years ago, compared to Cerbos which began 5 years ago. This 2.9-year head start suggests Ory 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 Ory extends into Authentication & SSO.
Ory provides self-hosting options for complete data control and customization, while Cerbos may be primarily cloud-based or require different deployment approaches.