Yes, Ory offers a similar level of flexibility and fine-grained control over authorization decisions. Ory Permissions, based on the open-source Ory Keto Permission Server, is a modern permission system that allows you to create a complete authorization system for your application or website, no matter the size or the complexity of the ACLs (access-control lists) your use case requires. Ory Permissions provides a flexible data model you can customize to fit a wide range of use cases. You can use the Ory Permission Language to create permission models that fit your exact use case - RBAC, ABAC, and beyond. This means you can define permissions as granular as

User:x is in readers of Document:y

, and allow permissions inheritance through groups, roles, and hierarchies. While the extracts do not explicitly mention the ability to send "facts" as part of the context of an authorization request, the flexibility of the Ory Permission Language and the ability to create custom permission models suggest that you could potentially achieve a similar level of contextual information in your authorization decisions. For more detailed information on how to implement this with Ory, you may want to refer to the [Ory Keto documentation](https://www.ory.sh/docs/keto).