Oso is a batteries-included library for building authorization in your application.
Oso gives you a mental model and an authorization system – a set of APIs built on top of a declarative policy language called Polar, plus a debugger and REPL – to define who can do what in your application. You can express common concepts from “users can see their own data” and role-based access control, to others like multi-tenancy, organizations and teams, hierarchies and relationships.
Oso alternatives and similar gems
Based on the "Authorization" category.
Alternatively, view oso alternatives based on common mentions on social networks and blogs.
5.2 5.0 L5 Oso VS AccessGrantedMulti-role and whitelist based authorization gem for Rails (and not only Rails!)
3.4 4.9 Oso VS RoleCore🔐A Rails engine providing essential industry of Role-based access control.
2.6 4.2 Oso VS RedisWebManagerManage your Redis instance (see keys, memory used, connected client, etc...)
1.6 0.0 Oso VS Yabeda::Puma::PluginCollects Puma web-server metrics from puma control panel
Find if a given user agent string satisfies a Browserslist browsers.
1.0 0.0 Oso VS Kno RubyDID is an Identity Provider, that authenticates users by verifying access to either an email address or securely stored private key.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Oso or a related project?
What is Oso?
Oso is a batteries-included framework for building authorization in your application.
With Oso, you can:
- Model: Set up common permissions patterns like role-based access control (RBAC) and relationships using Oso’s built-in primitives. Extend them however you need with Oso’s declarative policy language, Polar.
- Filter: Go beyond yes/no authorization questions. Implement authorization over collections too - e.g., “Show me only the records that Juno can see.”
- Test: Write unit tests over your authorization logic now that you have a single interface for it. Use the Oso debugger or REPL to track down unexpected behavior.
Our latest creation Oso Cloud (Preview) makes authorization across services as easy as oso.authorize(user, action, resource). Learn about it.
- To get up and running with Oso, try the Getting Started guide.
- Full documentation is available at docs.osohq.com.
- Check out Use Cases to learn more about how teams are using Oso in production.
- To learn about authorization best practices (not specific to Oso), read the Authorization Academy guides.
Community & Support
If you have any questions on Oso or authorization more generally, you can join our engineering team & hundreds of other developers using Oso in our community Slack:
Share your story
Oso's language libraries can be developed without touching the Rust core, but you will still need the Rust stable toolchain installed in order to build the core.
To build the WebAssembly core for the Node.js library, you will need to have
wasm-pack installed and available on your system PATH.
To work on a language library, you will need to meet the following version requirements:
- Java: 10+
- Maven: 3.6+
- Node.js: 12.20.0+
- Yarn 1.22+
- Python: 3.7+
- Ruby: 2.4+
- Bundler 2.1.4+
- Rust: 1.46+
- Go: 1.14+
Contributing & Jobs
If you want to work on the Oso codebase full-time, visit our jobs page.
*Note that all licence references and agreements mentioned in the Oso README section above are relevant to that project's source code only.