A policy administration and management platform for externalized authorization
A complete authorization management system for authoring, testing and deploying policy
Web IDE for building policies
Create policies in YAML with our policy wizard, and use the playground to define, validate, and test authorization rules.
Real-time group collaboration
Pair programmers or different team members to edit and review policies like a Google doc.
Push authorization policy files changes directly from the Playground IDE to your Github repo.
Test-driven development (TDD)
All tests are executed in the Cerbos Hub CI pipeline before policy is rolled out to PDPs.
Policy testing
A managed CI/CD pipeline builds and tests every new commit to the policy repository following Git-ops principles.
Policy orchestration
Cerbos Hub keeps policies up-to-date by coordinating each new rollout to all PDPs across your infrastructure.
Decision point monitoring
Observability into all deployed PDPs, with instance logs, deployed policy version details and metrics in a single screen.
In your infrastructure
Whether on-premise, cloud, functions, or Kubernetes, Cerbos Hub simplifies testing and distribution keeping policy in sync.
Serverless architectures
Works in Vercel, Netlify, AWS Lambda & CloudFront, Google Cloud Functions, and Azure Functions.
At edge & embedded devices
Pre-compiled libraries provide local execution for edge devices such as security hardware and cameras.
In browser runtime
Make local, in-browser authorization calls for React, Angular, and front-end frameworks, powered by WebAssembly.
Capture every decision
Every decision made by a Cerbos PDP is captured - know exactly which principal, did which action on which resource, and whether it was allowed or not.
Decision lineage
Audit logs provide not just the decision, but also how it was reached. Every record provides the specific policy, version, and releases which was responsible for the decision being made.
Collated across environments
Cerbos Hub collects and aggregates decision logs from every connected PDP, in every environment they are deployed.
Provide trials, feature bundles and custom packages for customers.
"It's weird to say an outside company has our back, but Cerbos does. It's the people. It's their open-source code: it's high quality, you can read it, it does what it says on the tin"
"It's a good feeling being able to say yes to almost any permissioning requirement." "Cerbos is small, contained and easy to implement. It 100% delivers on the promise of abstracting away the complexity of decision making."
"We're not worried about scaling because we can easily increase our load on Cerbos. It will also be easy for us to change how we're distributing policies as we reach different points of scale."
"We went from one user - every role, to a world where there are many users - many roles. And the product, it relies on Cerbos to actually bring the value that we want to bring to customers. All of our customers are relying on Cerbos, by relying on the product, which is of course relying on Cerbos."
"Instead of thinking of how much time Cerbos has saved us, I think about how much time it didn't cost us. It didn't cost us any time. Cerbos just works. I don't have to think about it. It's as simple as that."
"One of our big considerations was speed. We have strict latency tolerances. When it comes to Cerbos - you can call it a hundred times during a request and it doesn't matter. It's incredibly fast."
"If it wasn't for Cerbos, one thing is for sure - we would've launched later than we did. As a result, we would have less customers. And the maintenance part is also very important. Our technical team would be dealing with daily stuff regarding access controls, access logs. Now, we don't have to spend any time on that."
"Cerbos policy writing is quite flexible, and deploying as a unit microservice as well. Cerbos "doesn't get in the way" once integrated, that's the best part."
"It is easy to implement and provides a solution for a problem that is often not properly addressed."
"Having the separation of the permissions from the code base just makes the code base more elegant. It makes the permissioning more elegant. It means they're centralized, so they're not tied to specific endpoints. And ultimately it means that different business owners have the ability to actually make updates."
"Just discovered your embedded testing framework. This is probably the best balance between hyperfocused functionality and embedded tooling I've ever seen in an open source project. Damn, good work!"
Want to run authorization yourself?
Prototype policies in your browser right now
Check out our API reference and guides
Join our community on Slack and learn
Stories of Cerbos in production
Book an intro call and learn more
Join thousands of developers | Features and updates | 1x per month | No spam, just goodies.