Plug and play collaborative authorization
Define and evolve complex policies without requiring further developer time.
Join hundreds of leading companies using Cerbos
Why Cerbos?
Cerbos makes it possible to quickly, easily and securely set up and change roles and permissions of any complexity, allowing even non-technical stakeholders to make changes, while reducing the risk of incidents resulting from a failed update to authorization logic.
Agile
Define and evolve complex policies and roll them out without requiring a development cycle.
Enterprise ready
Be enterprise ready and meet each of your customer's organizational requirements with ease.
Centralized management
Cerbos Hub is a collaborative platform for streamlined authorization policy authoring, iteration and management, ensuring consistent permissions across applications.
Auditing & reporting
Ensure compliance with a full audit trail of policies, permissions, and resource access, while proactively addressing security and compliance concerns.
Cerbos overview
Learn about how Cerbos works and adds declarative access control into your application in minutes.
Unlock streamlined authorization with Cerbos
Built for scale
Whether you're managing a startup's application or a large enterprise solution, Cerbos scales with your needs. Its robust architecture ensures that as your business grows, your authorization system remains efficient and reliable.
Low-latency
With Cerbos, authorization checks are done in a service inside of your existing application architecture. The Policy Decision Points are just another component in your stack and evaluate policy decisions with any requirement to go to the cloud.
Active community
Join a thriving community of Cerbos users and contributors, ensuring you have ample support and resources at your disposal and keep on top of the latest developments with Cerbos.
How it works
#1
Capture business requirements
Gather requirements from across your business for what the premissioning logic should be in the application.
#2
Define policies
Based upon your business logic, define policies which implement the rules, checking roles and conditions for each resource kind in the application.
#3
Implement checks
Working with your development team add in the permission checks - this only has to be done once!
#4
Iterate
As new requirements come along new policies and conditions can be introduced without having to make a code change.
What our users say about Cerbos
Rob, Principal Engineer
@ Utility Warehouse
"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"
Joe, Software Engineer
@ 9fin
"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."
David, Senior Software Engineer
@ Salesroom
"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."
Joe, CEO & Co-Founder
@ Nook
"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."
Chuck, Head of Engineering
@ Salesroom
"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."
Steve, Staff Engineer
@ NTWRK
"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."
Engin, Head of Product and Growth & Co-Founder
@ Debite
"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."
Rounak, Founding Engineer
@ CommandK
"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."
Romina, Tech Lead
@ Wizeline
"It is easy to implement and provides a solution for a problem that is often not properly addressed."
Henry, CTO & Co-Founder
@ Nook
"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."
Rasmus, CTO
@ Firtal
"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!"
Most popular resources
Cerbos Policy Decision Point
Want to run authorization yourself?
Playground
Prototype policies in your browser right now
Docs
Check out our API reference and guides
Slack community
Join our community on Slack and learn
Success stories
Stories of Cerbos in production
Speak to an engineer
Book an intro call and learn more
Subscribe to our newsletter
Join thousands of developers | Features and updates | 1x per month | No spam, just goodies.