Oso

Distributed authorization.

Visit website ↗

Profile updated

Console’s review

· Reviewed by David Mytton

What we like

Flexible approach to building authorization logic with a DSL. No need to rely on a single centralized service - centralize the logic, which can return “yes, if” for validation with local data. Makes it easier to reason about complex auth across microservices. SDKs for Node, Python, Go, Ruby, and .NET. Check in your auth .polar files to Git.

Tradeoffs

Default model uses Oso Cloud, but there are options for self-hosting and running a hybrid cache layer for HA.

Topics covered: Authorization

Is Oso a fit?

Based on Console’s review published on 2024-04-18. Summary updated .

Who it’s for

Developers of microservices-based systems should consider Oso

Why consider it

Oso makes it easier to reason about complex authorization across microservices

Keep in mind

The default model relies on Oso Cloud, which may not be desirable for all users

Console is a free weekly newsletter with short reviews of developer tools, covering strengths and tradeoffs. This review reflects Console’s assessment at publication on 2024-04-18. Features and limitations may have changed since the review date. Read our selection criteria and learn about Console.

Discover your next favorite tool

Independent devtool reviews and the latest betas, in your inbox every Thursday. Free.