oso VS cerbos

Compare oso vs cerbos and see what are their differences.


Cerbos is the open core, language-agnostic, scalable authorization solution that makes user permissions and authorization simple to implement and manage by writing context-aware access control policies for your application resources. (by cerbos)
Our great sponsors
  • InfluxDB - Build time-series-based applications quickly and at scale.
  • Scout APM - Truly a developer’s best friend
  • Zigi - Close all those tabs. Zigi will handle your updates.
  • SonarLint - Clean code begins in your IDE with SonarLint
oso cerbos
15 7
2,791 854
1.3% 19.1%
8.9 9.7
11 days ago 2 days ago
Rust Go
Apache License 2.0 Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of oso. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-11-19.
  • Show HN: ILLA is an Open-source alternative to Retool
    6 projects | news.ycombinator.com | 19 Nov 2022
    Not OP but Authentication is easy, authorization is a cross-cutting concern that often requires custom code. E.g., there are people and teams, both of which can have different kinds of access to something (read/write). Sometimes teams have sub-teams. Do the sub-teams have access to the parent teams' resources and/or vice versa? Also what kind of sharing are you going to support? Do people have to have an account to view stuff shared to them or can you just send a link? There are some efforts to make custom DSLs for describing authorization policies, to avoid cross-cutting code[1].

    Computed fields require different treatment at every level of the stack. This isn't inherently hard, but it is an extra feature these low-code/no-code platforms need. Where things get difficult is inn migrations. It's common for a field that is computed at the beginning to become customizable, or for the computation to change. When that happens, what should the value be for old columns? Computed fields also often pull data from multiple other tables, which may require some combination of custom queries and database optimization.

    [1] https://github.com/osohq/oso

  • Resource-based authentication
    5 projects | reddit.com/r/ExperiencedDevs | 15 Aug 2022
    Oso and OpenFGA are two alternatives that implement Zanzibar-style authorisation.
  • Decoupling Authorization Logic from Code in NodeJS
    4 projects | reddit.com/r/node | 29 Mar 2022
    There's Oso as well
  • Is Datalog a good language for authorization?
    4 projects | news.ycombinator.com | 19 Feb 2022
    Well this was fun to see! I'm the CTO of Oso, where we're building Polar (the second of the links mentioned https://docs.osohq.com/).

    I have a few really minor nitpicks, so will try and make up for it by adding to the discussion :)

    First of all, it doesn't really make sense to talk about Datalog as a good language for authorization, because much like with Prolog there doesn't really exist a single implementation of it. OPA's language Rego is a datalog variant, and Polar started out as a Prolog variant (although it's not really recognisable as one any more).

    And that's an important point because otherwise it would be pretty reasonable to decide that: logic programming is good for authorization => you should go find the most battle-tested language out there and use that. For example, there's SWI Prolog [1] and Scryer Prolog [2] as two of my favourites.

    To me, the thing that is mind-blowing about logic programming, is (a) how powerful the paradigm is, and (b) how concisely you can implement a logic programming language. Take miniKanren [3] which is a full-blown logic language in a few hundred lines of code.

    In my mind, the original article makes a decent case that logic programming is a good fit for authorization. And just generally I love anyone bringing attention to that :)

    But to me, the reason logic programming is such a solid foundation for authorization logic is the pieces you can build on top of it. For Polar, we've added:

    - Types! So you can write authorization logic over your data types and help structure your logic. We've implemented this by simply adding an additional operator into the language that can check types

  • Hey Rustaceans! Got an easy question? Ask here (52/2021)!
    11 projects | reddit.com/r/rust | 27 Dec 2021
    First time hearing about rhai, but there's a project in that space called Oso that's authored in Rust and uses a different DSL than Rego. You may or may not find it appealing.
  • Hey Rustaceans! Got an easy question? Ask here (44/2021)!
    5 projects | reddit.com/r/rust | 2 Nov 2021
    Authentication is probably the aspect of it that's the weakest. Authorization has a few nice libs, with Oso probably being the nicest, but authentication is mostly roll your own from what I've seen.
  • We Built a Cross-Platform Library with Rust
    3 projects | news.ycombinator.com | 27 Oct 2021
    > Hopefully Oso open source their library.

    https://github.com/osohq/oso seems to have the core, C FFI, and language bindings.

  • How to manage multi tenant in fast-api
    2 projects | reddit.com/r/FastAPI | 17 Sep 2021
  • Why Authorization Is Hard
    9 projects | news.ycombinator.com | 15 Sep 2021
    Hey, Oso engineer here. Good question.

    The rust core is indeed called from the ruby library (as it is with all of our 5 other host libraries). The core itself is pretty complex (there's a whole parser/interpreter in there), so maintaining it in a bunch of languages would be a bit hectic.

    There are some files inside `lib/oso/polar/ffi` that define the C bindings used by the rest of the library. Here's an example: https://github.com/osohq/oso/blob/main/languages/ruby/lib/os...

    We use the ffi gem to make that work: https://github.com/ffi/ffi

    9 projects | news.ycombinator.com | 15 Sep 2021
    It is a wrapper around the Rust code:

    - It triggers the rust build in the Makefile: https://github.com/osohq/oso/blob/1d3bf5a4a997a574c2b19084a0...

    - There is a bunch of FFI code (also in the ffi directory): https://github.com/osohq/oso/blob/1d3bf5a4a997a574c2b19084a0...


Posts with mentions or reviews of cerbos. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-11-11.
  • AWS IAM Roles, a tale of unnecessary complexity
    3 projects | news.ycombinator.com | 11 Nov 2022
    One potential solution: https://github.com/cerbos/cerbos. It's a standalone service (deployed alongside your app) which evaluates access decisions at runtime against contextual/arbitrary data on the principal and resources.

    In your case, your resource could be a "record" for more global yes/no decisions, or perhaps as a "field" for more granular cases. Things like "can only get last 4 digits of phone number" could be achieved through attribute-based conditions set within the policies.

    > I really liked the policy approach of IAM so my plan was to let data owners define policies that are then applied to users, groups, and roles

    An advantage of Cerbos is that policies are defined and deployed separately from business logic in (yaml/json) config files, so no changes are required in code when policies need updating.

    > At run time our coordinator engine will check levels of access to each query

    Can't wrap my head around this particular part - is this checking if an entity can or cannot run a particular query, or specifically based on the "things" the query is returning?

    (as a disclaimer I should mention that I work there, although Cerbos itself is Apache 2 licensed and completely free to use)

  • OWASP top change visualization from 2004 to now
    2 projects | news.ycombinator.com | 20 Oct 2021
    Here [0] is a link to the license file on their main repo, and Here [1] is a screenshot of the link in my previous comment highlighting the license on all of the repos.

    [0] - https://github.com/cerbos/cerbos/blob/main/LICENSE

  • The never-ending product requirements of user authorization
    2 projects | reddit.com/r/programming | 16 Sep 2021
    Hey there - yup Cerbos is a decision engine that enables ABAC and in fact uses OPA underneath currently for the policy execution (we are building in the open https://github.com/cerbos/cerbos)
  • Why Authorization Is Hard
    9 projects | news.ycombinator.com | 15 Sep 2021

What are some alternatives?

When comparing oso and cerbos you can also consider the following projects:

CASL - CASL is an isomorphic authorization JavaScript library which restricts what resources a given user is allowed to access

node-casbin - An authorization library that supports access control models like ACL, RBAC, ABAC in Node.js and Browser

OPA (Open Policy Agent) - An open source, general-purpose policy engine.

Ory Keto - Open Source (Go) implementation of "Zanzibar: Google's Consistent, Global Authorization System". Ships gRPC, REST APIs, newSQL, and an easy and granular permission language. Supports ACL, RBAC, and other access models.

django-guardian - Per object permissions for Django

django-rules - Awesome Django authorization, without the database

casbin-server - Casbin as a Service (CaaS)

Pundit - Minimal authorization through OO design and pure Ruby classes


Spoodle - A mass subdomain (Subbrute) + poodle vulnerability scanner