Congratulations on the OSS launch! Was it always in the cards to open source Cedar?<p>I'm excited to see you've found a way to bring verification that exists in non-policy-based authorization solutions to Cedar. Was that functionality the driving factor that made the team create something new instead of leveraging the widely adopted Rego/OPA[0] stack for policy?<p>It looks like this talk[1] briefly covers why you made Cedar, but I'd be eager to hear more about the trade-offs in design, because other policy languages are leveraging decades of formal research on Datalog.<p>Disclosure: I work on SpiceDB[2], an authorization database inspired by Google's Zanzibar system[3], but I wouldn't say Cedar is directly competitive as SpiceDB is not a policy-based system.<p>[0]: <a href="https://www.openpolicyagent.org/docs/latest/policy-language/" rel="nofollow">https://www.openpolicyagent.org/docs/latest/policy-language/</a><p>[1]: <a href="https://youtu.be/k6pPcnLuOXY?t=2037" rel="nofollow">https://youtu.be/k6pPcnLuOXY?t=2037</a><p>[2]: <a href="https://github.com/authzed/spicedb">https://github.com/authzed/spicedb</a><p>[3]: <a href="https://zanzibar.tech" rel="nofollow">https://zanzibar.tech</a>