Visibility and controls to secure agents.

Agents are here. Oso makes them safe.

Trusted by

Integrated into your stack

Real-world AI agent failures, exploits, and defenses

The Agents Gone Rogue registry tracks the latest agentic failures, exploits, and emergent attack patterns so organizations can understand where real risks exist and how to mitigate them.
Go to registry

Your employees ignore 96% of their permissions. Agents won't.

‍New study reveals that nearly all enterprise permissions are left untouched by humans, creating a massive risk when agents inherit human access.
Read the reseach
Featured in
Foundry-Logo

Testimonials

close-quote-icon
You can’t prompt your way to least privilege. Oso wires it into every call. Let’s have a cocktail.
Jared Rosoff,
VP of Infra, Roblox
close-quote-icon
Agents should unlock creativity, not create new categories of risk. Oso's approach—automated least privilege—is exactly how you make that real.
Kareem Amin
Co-Founder & CEO, Clay
close-quote-icon
We want partners who understand where security is headed, not just where it's been. Oso gets that agentic systems need fine-grained authorization baked in from the start.
Mark Hillick
CISO, Brex
close-quote-icon
Agents in production need the same rigor we bring to clinical decisions: precise, measurable, auditable. Oso gets that.
Adam Chekroud
Co-Founder & President, Spring Health
close-quote-icon
At 1Password, we’re seeing the same pattern Oso highlights as teams start putting AI agents into real production workflows. Access models built for humans don’t map cleanly to agents. When agents are handed broad, static permissions, the unused ones don’t just sit there, they quietly expand the attack surface.
Nancy Wang
CTO at 1Password

Get your arms around agent adoption

Schedule time with Graham Neray, Oso’s founder, to learn more about automated least privilege enforcement for agents.

RBAC, ReBAC, ABAC, AnyBAC you need.

Never build authorization again.

Trusted by

How Oso for apps works

Oso is what engineering teams use when they’re done rolling their own permissions. It lets your application answer questions like “can this user read that document?” and “which objects can this agent manage?”

Write your policy

RBAC, ReBAC, ABAC, AnyBAC you need. Express any authorization model with Polar, our flexible DSL for permissions logic.

how-oso-works-code-snippet

Plug in your data

Sync your authorization data with Oso, or keep it in your database – whatever fits your architecture best.

how-oso-works-subsection-2-diagram

Integrate (for the last time)

The right abstractions for every use case. Idiomatic SDKs in the language of your choice. Inline policy tests. Logging, regression testing, and debugging. Backed by the most comprehensive documentation on earth and the team that created the category.

Logos for various programming languages like JavaScript, Ruby, .Net, and Python.
how-oso-works-subsection-3-diagram
Featured in
Foundry-Logo

Testimonials

Duolingo-logo-mark
close-quote-icon
Oso is a compelling fit because of their singular focus on authz, plus the flexibility of their Polar rule definitions. In twenty minutes we’d managed to define a custom Polar definition to handle our current use case.

Evan Ziebart
Engineer, Duolingo
Productboard-logo-mark
close-quote-icon
We reviewed multiple solutions – Oso came out on top for its devex, scalable and consistent performance, and the flexibility to match all our needs.
Jiří Brunclík
VP Engineering, Productboard
Intercom-logo-mark
close-quote-icon
Oso is A+. As we moved upmarket, being able to implement authz consistently and accurately helped us move faster and resolved a never-ending source of bugs.
Brian Scanlan
Engineer, Intercom
Oyster-logo-mark
close-quote-icon
It used to take us months to add new roles. With Oso we cut that time 10x. The Oso team has also been very helpful, making our migration super smooth.
Derick Matamoros
Lead Engineer, Oyster HR
Wayfair logo mark
close-quote-icon
We needed to break our monolith into microservices [and] manage authorization across all of our new microservices. The answer was the Oso authorization framework... Today, we have multiple services within our domain that are utilizing Oso as their source of authorization management.
Nicholas Matison
Senior Engineer, Wayfair

Built for the critical path

Scalability
Scales horizontally to
1M+
requests/sec
Performance
Delivers
<10ms
p90 latency
Built in Rust
rustacean-flat-white-logo-mark