# Oso Distributed authorization. Source: [Console review]() Website: [https://www.osohq.com/post/distributed-authorization]() Profile updated: 2026-10-16 Category: [Authentication]() ## Supported tech stack Research checked: 2026-10-11 ### Integrates with - MySQL (Integration) - PostgreSQL (Integration) Source: [Research source]() Documented compatibility; coverage may be incomplete. Written in describes implementation, not user-project language support. Local authorization supports PostgreSQL and MySQL databases. ## Console’s review — 2024-04-18 Reviewed: 2024-04-18 Author: [David Mytton]() Citation: [This review]() ### 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. This review reflects Console’s assessment at publication on 2024-04-18. Features and limitations may have changed since the review date. Topics covered: Authorization ## Is Oso a fit? Based on [Console’s review published on 2024-04-18](). Summary updated: 2026-10-16 ### 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 [Selection criteria]() · [About Console]() · [Browse tools]()