Oso: Agent Security & Authorization

Coding agents are here. Oso makes them safe.

Automated least privilege for Claude Code, Cursor, Codex, and whatever's next.

Book a demo Learn more

Trusted by

Your engineers are already using coding agents.

Next up is product, finance, and sales – the whole company.
How do you get your arms around agent adoption?

Scope

Get the permissions house in order

Every user in your org has permissions. Most have too many.
Oso maps this posture: who has access to what, classified by risk. Then it recommends what to scope down — before agents inherit the mess.

Risk monitoring dashboard for agents showing alert threshold rules and frequency and severity graphs for finance-automation agent with peaks and configurable thresholds.

Watch

See what agents are doing

Every prompt, every tool call, every MCP server — captured in real time.
Default alerts for PII exfiltration, unusual velocity, and access to sensitive resources. Add your own rules in minutes.
When agents exceed least privilege, you know immediately.

Dashboard interface for Oso for Agents showing Content settings to detect sensitive data types like phone numbers, email addresses, credit card numbers, social security numbers, and names, all toggled on.

Enforce

Narrow access automatically as risk builds

Permission risk isn’t static. It’s a function of the user, the agent, and the session so far.
As risk climbs, access narrows — automatically.
High-risk actions go through deterministic controls. Block agents from leaking data, modifying critical infra, or breaking any rule you set.

Dashboard showing agent activity logs with timestamps, event types, session IDs, agent IDs, and user emails.

Audit

Keep receipts

Full trails of every action, tool call, command, and LLM response.
Backwards visibility to handle incident response and post-mortems.
Reports on agent posture and proof that you're on top of it.
Compliance records for auditors.

Testimonials

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

Agents should unlock creativity, not create new categories of risk. Oso's approach—simulate, enforce, detect—is exactly how you make that real.

Kareem Amin

Co-Founder & CEO, Clay

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

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

Oso made building Productboard Pulse much faster, since every API can just call Oso to figure out what’s allowed, no matter where the data resides. By building on top of a proven authorization foundation, we’ve avoided the biggest hurdles derailing AI efforts in many companies.

Matúš Koperniech

Staff Engineer, Productboard

Resources

RBAC, ReBAC, ABAC, AnyBAC you need.

Never build authorization again.

Try for free Meet an Eng

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.

Show me the code

Plug in your data

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

See how it works

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.

Read the docs

Testimonials

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

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

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

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

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