Policy as Code Open Source Project – Roadmap Questions

In 2021, when Permit.io launched, we anchored our authorization framework on Policy as Code with a specific focus on OPA/Rego. We believed, and still do, that Policy as Code approach is key to scalable authorization.

While policy engines solve the challenge of decoupling policy and code, the challenge of scaling them and loading them with the right policy and data remains strong - especially for event driven systems.

We reviewed how Netlfix used OPA with a a replication pattern; and decided to create a similar yet more extensible and event-driven solution - and so OPAL (Open Policy Administration Layer) was born - creating a scalable, zero-trust way to manage policy engines and their policy/data at scale.

Fast forward two years, and the landscape has evolved. New policies as code languages and standards have emerged (Cedar, OpenFGA, etc.), and in this evolving market, OPAL has positioned itself as a leading solution for synchronizing policy as code with policy data, particularly for self-hosted environments.

What truly differentiates OPAL from other solutions like Topaz and Permify is its flexibility. OPAL is not limited to a single policy engine; it supports a variety, making it a versatile tool for authorization applications. Using a single Helm chart or Dockerfile, one can deploy a full-fledged authorization system, customized to specific policy models, languages, and engines.

As we look to the future, we're keen to gather insights from the HackerNews community. What features would you like to see in OPAL? How can we make it more robust and efficient for your authorization needs?

We value your feedback and are excited to see how your suggestions can shape OPAL's roadmap.

P.S. As with any open-source project, your support on GitHub, especially stars, helps us a lot. Thanks in advance for your backing!