Our POCs with Cerbos have been going very well, it seems to be a really great fit for us. So wanted to say thank you & well done to the team, both the implementation and the documentation are really great 👏 . A couple of questions that have come up: • Is there a roadmap for the future of Cerbos? • Other services in the authz space seem to be heading down the hosted, cloud-based route to productize - what is the teams thoughts on that? • What are the resource requirements when the policies get into the 100s or 1000s, and how much is respoonse time affected?

Hey @david so glad to hear things are going well and thanks for your kind words! Roadmap wise we are focusing still on making the open source core offering as feature complete as possible, ensuring it's has the best developer experience of all the options out there. There is indeed a trend for a cloud offering in this space which is something we are considering but taking a slightly different approach to others as there are big performance and latency considerations for your app if you rely on external systems for AuthZ which we personally wouldn't be comfortable with. We have done some basic load testing of policies at that scale with no noticeable difference to response time - this is down to the fact that at startup Cerbos loads in the policies and complies them to a far more performant internal representation in memory. As everything is stateless (you can run in serverless functions) scaling up doesn't require any other changes to your infra. If you are keen we would love to have a more detailed chat with your about your use case and we can chat more about the above. Pick some time at https://go.cerbos.io/workshop