cerbos/cerbos

Cerbos is an open-core authorization management platform for authorizing every identity and governing every action across applications, gateways, workloads,...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 25 minutes ago
Type:Server / PlatformCategory(s):Identity, Auth & SecretsSecurity & Privacy
Added to GitGenius on September 15th, 2026
Created on March 21st, 2021
Open Issues & Pull Requests: 60 (+0)
GitHub issues: Enabled
Number of forks: 213
Total Stargazers: 4,592 (+0)
Total Subscribers: 34 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.1 hours
Mean response time: 36.2 days
90th percentile: 29.8 days
Tracked items: 72

Most active contributors

Sign in to see contributor activity.

How this project is maintained

92% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 69% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 26
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 510 days
Stale 30+ days: 22
Stale 90+ days: 19

Recent activity

Opened in 7 days: 2
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • kind/bug (27)
  • status/triage (22)
  • kind/feature (14)
  • kind/enhancement (7)
  • area/testing (5)
  • area/api (3)
  • area/ci (3)
  • kind/question (3)

Most active issues this week

Detailed Description

Cerbos is a policy decision point and authorization management platform that enables applications to make dynamic access control decisions based on context-aware rules.

Cerbos solves the problem of implementing fine-grained authorization across distributed systems by centralizing access control logic into a dedicated service. Rather than embedding authorization checks throughout application code, developers define policies as YAML files that specify which principals can perform which actions on which resources. The platform continuously monitors these policies, which can be stored on disk, in cloud object stores, Git repositories, or databases, and exposes APIs that applications query to evaluate whether a specific access request should be allowed. This approach decouples authorization logic from application code and makes policies auditable and version-controlled.

Teams should adopt Cerbos when they need authorization that goes beyond simple role-based access control and must handle context-dependent decisions across multiple applications or services. It suits projects where policies need to be managed centrally, updated without redeploying applications, and potentially shared across a fleet of policy decision points. The platform is particularly valuable in microservices architectures, serverless deployments, and edge computing scenarios where authorization decisions must be made consistently across distributed components. Cerbos Hub, a companion service, streamlines policy authoring in interactive playgrounds and simplifies distribution of policy updates to self-hosted instances, though the core platform can operate entirely self-hosted.

The project maintains active continuous integration with automated snapshot builds. The codebase demonstrates strong quality standards as evidenced by its Go Report Card rating. Development follows semantic versioning for releases, and the project has adopted a formal contributor covenant, indicating structured community governance.