Use Ory Kratos identity schemas, session data, and traits to drive fine-grained authorization decisions in Cerbos policies.
Use Ory Kratos identity traits defined in your JSON schemas as first-class attributes in Cerbos policies
Integrates alongside Ory Kratos, Oathkeeper, and Hydra without replacing any component in your identity infrastructure
Both Ory and Cerbos are open source, giving you full transparency and control over your authentication and authorization stack
Ory handles authentication, confirming who a user is. Cerbos handles authorization, deciding what that user can do. Together they give you a complete access control stack without coupling identity logic to business rules.
Cerbos lets you write fine-grained, context-aware authorization policies in human-readable YAML. Policies are decoupled from application code so product and security teams can update permissions without a release cycle.
Because Cerbos runs as a stateless Policy Decision Point (PDP) next to your application, authorization checks are sub-millisecond and scale horizontally with your infrastructure.
Ory Kratos lets you define identity through JSON schemas, giving you full control over what traits each identity carries (department, subscription tier, organization, custom fields). Cerbos uses those traits to make fine-grained authorization decisions, turning your identity schema into an authorization data source.
Because Ory Kratos identity schemas are fully customizable, you can design your identity data model to include exactly the attributes your authorization policies need. Cerbos policies reference these traits directly, so adding a new trait to your identity schema immediately makes it available for authorization decisions, no code changes required.
Check out the Cerbos documentation to learn how to pass Ory Kratos session traits to Cerbos for policy evaluation.
Ory Kratos uses JSON schemas to define identity traits (department, tier, role, organization, etc.). After authentication, your application retrieves the session and passes these traits to Cerbos as principal attributes. Policies can reference any trait defined in your schema.
Yes. Ory Oathkeeper can act as a reverse proxy that validates sessions and injects identity data into request headers. Your application or API gateway reads these headers and passes the identity data to Cerbos for authorization. Oathkeeper handles authentication enforcement, Cerbos handles authorization.
Yes. Cerbos integrates at the application layer using session data from Ory. Whether you run Ory Kratos self-hosted or use Ory Network (their managed cloud), the integration pattern is the same: extract identity traits from the session and pass them to Cerbos.



What is Cerbos?
Cerbos is an end-to-end enterprise authorization software for Zero Trust environments and AI-powered systems. It enforces fine-grained, contextual, and continuous authorization across apps, APIs, AI agents, MCP servers, services, and workloads.
Cerbos consists of an open-source Policy Decision Point, Enforcement Point integrations, and a centrally managed Policy Administration Plane (Cerbos Hub) that coordinates unified policy-based authorization across your architecture. Enforce least privilege & maintain full visibility into access decisions with Cerbos authorization.