An update from Cerbos!
This is an exciting moment for us as we are kicking off our newsletters! You are receiving this email because either we have met, chatted, or you’ve visited our website cerbos.dev and asked us to keep you up-to-date. If you don't want to receive these emails you can unsubscribe below, but we hope you stay!
What happened in the last 6 months?
Earlier this year we set about building Cerbos as we saw a clear need in the market for a solution to authorization and more specifically user permissions (you can read more why in our blog post “Why are we building Cerbos”).
Since then we have been busy developing Cerbos and last month took the big step and open sourced our core engine which you can find on GitHub. We are now up to v0.8 out just last week and have already got users putting it to the test.
Off the back of this early development and releases, we are very excited to reveal that we have completed our seed funding round. We were overwhelmed with the amount of interest we received and we will be announcing more details about this very soon.
Cerbos use cases
Through our ongoing discovery process, we’ve talked to hundreds of potential users and customers about Cerbos, gathering requirements and feedback and we have now identified an initial four authorization use cases that Cerbos can solve:
- Application Permissions: Go beyond roles! context aware authorization allows for fine grained access control to any resource in the system without hard coding logic and complicated spaghetti code
- Product Packaging: With each customer having a different version of a package, trials and grandfathered features, have a central point which manages access across the system
- Multi-tenant SaaS: Scaling your SaaS offering with controlled, audited and isolated environments per customer enforced by policies
- Enterprise Ready: Easily enforce access control across the complex web of departments, offices and geographies of any organisation
We are producing lots more content, demos and case studies around these themes and would love to hear from you about what challenges you are facing that we can help solve with Cerbos.
How can one get started?
Our aim is to make Cerbos as easy as possible to get started with, so we have been busy creating comprehensive documentation:
In addition to this we have created our first policy writing tutorial that demonstrates how to design policies for a photo sharing application, as well as releasing a number of demos: Go REST API, GraphQL Demo, JSON Web Tokens and Python.
To simplify things every further we are publishing a set of SDKs with Java, Go and Node JS already available and more in the works covering Python, .NET and Ruby.
Finally, not everyone wants to go through the steps required to set up Cerbos locally, so now we have our Playground which is a fully-featured environment to compose, validate and test writing Cerbos policies. The advantage of being web-based is that it is possible to save policies online and share them easily with colleagues. We have a lot more planned for this tool and would love to hear your feedback on what you would like to see.
.png)
