
Use FusionAuth's flexible user data model, application roles, and custom data fields to drive fine-grained authorization decisions in Cerbos.
Use FusionAuth's per-application role assignments to write authorization rules scoped to each application registration
Reference FusionAuth user.data and registration.data fields directly in Cerbos policy conditions
Combine FusionAuth tenant isolation with Cerbos scoped policies for per-tenant authorization logic
FusionAuth 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.
FusionAuth gives developers full control over their user data model: per-application role assignments, custom data fields on users and registrations, multi-tenant isolation, and JWT lambdas for claim customization. Cerbos uses that rich identity data to make fine-grained authorization decisions at the resource level.
FusionAuth's role system is application-scoped, which is a good starting point. But many applications need authorization decisions that depend on the specific resource being accessed, the relationship between the user and the resource, or contextual data like time or location. Cerbos policies express these rules using the identity data FusionAuth provides.
Watch our demo video or explore the Express + FusionAuth + Cerbos example project to see the integration in action.
Yes. FusionAuth assigns roles per application registration, so a user can have different roles in different applications. Your application passes the registration-specific roles to Cerbos, and policies can scope authorization decisions to the correct application context.
FusionAuth lets you store arbitrary key-value data on user objects and application registrations. When included in JWT claims via lambdas, this custom data can be passed to Cerbos as principal attributes and used in policy conditions.
Yes. FusionAuth's tenant ID and tenant-specific user data can be passed as principal attributes to Cerbos. Policies can then enforce different access rules per tenant without duplicating policy logic.



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.