Question 1

How is this different from a simple database check?

Accepted Answer

The Authz service centralizes evaluation through a DB provider with object inheritance, revision tokens for consistency, and CEL conditions. Performance must be measured against the target policy model, data volume, and deployment.

Question 2

Can I model complex organizational hierarchies?

Accepted Answer

Yes. The Object-Edge graph allows you to model any depth of hierarchy (e.g., Team -> Department -> Company). Permission checks can automatically traverse these edges, ensuring that a company-level grant correctly propagates to all child objects.

Question 3

Does it support attribute-based access control (ABAC)?

Accepted Answer

Absolutely. Using Common Expression Language (CEL) conditions, you can evaluate request attributes, IP ranges, time-of-day, or custom user metadata during the permission check itself without extra database lookups.

Question 4

Are there limits on the number of permission checks?

Accepted Answer

The commercial model is source licensing rather than per-check metering. Infrastructure, provider, support, and license costs still apply, and capacity is validated against the target policy and workload.

Common Questions & Answers

Related services

Related use cases