Hi @dorneanu, there are a couple of major differences between Ory's authorization solution, Keto:
Multi Tenancy: Our architecture is tenancy-based, which means you can create custom authorization models and relation tuples accordingly for different tenants and manage them in a single place. This is an important feature, especially for internal authorization use cases.
Attribute Based Access Control: We're supporting attribute-based access control and contextual permissions. This gives users the ability to define more complex policies using dynamic attributes such as boolean variables, IP range, time periods, location, etc.
Schema Management & Visibility: We're taking an approach that help engineering teams to ease and streamline the management and collaboration of their authorization systems. We have features like Schema Stating to manage schema changes in different stages, Partial Schema Update to update schema smoothly with multiple engineering teams, Relationship Bundles to streamline relation tuple creation, and more.
Security Architect and Software Engineer building secure systems in Golang/Python. I work with Kubernetes, OpenStack, and cryptographic services. Emacs & ORG mode for everything.
Hi @dorneanu, there are a couple of major differences between Ory's authorization solution, Keto:
Ok, thanks for the explanations!