oso is an open source policy engine for authorization that’s embedded in your application. It provides a declarative policy language for expressing authorization logic. You define this logic separately from the rest of your application code, but it executes inside the application and can call directly into it. oso ships as a library with a built-in debugger and REPL.

oso is ideal for building permissions into user-facing applications, but you can check out Use Cases to learn about other applications for oso.

Using oso consists of two parts:

1. Writing oso policies in a declarative policy language called Polar.
2. Embedding oso in your application using the appropriate language-specific authorization library.

oso currently offers libraries for Java, Node.js, Python, Ruby, and Rust.

To get up and running with oso, check out the Getting Started guides in the oso documentation.

oso's Rust core is developed against Rust's latest stable release.

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: 10.14.2+
  • Yarn 1.22+
• Python: 3.6+
• Ruby: 2.4+
  • Bundler 2.1.4+
• Rust: 1.46+

See: CONTRIBUTING.md.

See: LICENSE.