§50 · Lane 8 — Agent Infrastructure Standards & Toolchain

Oso (Polar + Oso Cloud)

Oso Security, Inc. (2026) · Oso Cloud + Polar

policy-engine Tier 1 Lane 8 Commercial / Apache-2.0
Read on publisher · Commercial / Apache-2.0

Bibliographic data

Title
Oso — Polar authorisation language and Oso Cloud platform
Authors / Issuing body
Oso Security, Inc. (osohq)
Venue / Publisher
Oso Security, Inc.
Year
2026
Designation
policy-engine
Licence
Commercial / Apache-2.0 — refer to publisher for full licence terms.

How to cite

Oso Security, Inc. (2026). Oso — Polar authorisation language and Oso Cloud platform. Oso Security, Inc.. https://www.osohq.com/docs.

Authorisation platform built on the Polar declarative policy language, delivered as the hosted Oso Cloud service with open-source Polar client libraries.

Why it matters for NETEVO

Oso models application authorisation in the Polar declarative language and answers questions such as whether a given actor may take a given action on a given resource, and which resources an actor may access. The current product is the hosted Oso Cloud service; the Polar language and the Oso client libraries are open source under Apache-2.0. Citing Oso gives NETEVO surfaces a commercial-managed-service alternative to the open-source engines Cedar and OPA.

The licence split matters for citation discipline. Oso Cloud is commercial with proprietary terms; only Polar and the client libraries are Apache-2.0. NETEVO prose discussing Oso must distinguish the hosted platform from the open-source language. For clients evaluating policy-engine adoption, the choice is between self-hosting an open-source engine and procuring a managed service — both legitimate, with the trade-off being the operational-overhead-versus-vendor-concentration trade-off familiar from any infrastructure choice.

A currency note: the maintained path is Oso Cloud. NETEVO surfaces citing Oso should point at the live osohq.com/docs surface.

Where NETEVO applies this

Related audiences