compare
Cerbos vs Topaz
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Cerbos | Topaz |
|---|---|---|
| Language | Go | Go |
| Licence | Apache-2.0 | Apache-2.0 |
| Stars | 4.6k | 1.4k |
| Latest | v0.56.0 | v0.33.22 |
| Last push | 2026-10-19 | 2026-10-14 |
| Release cadence | about 36 days between releases | about 7 days between releases |
| Active contributors | 6 commit authors on the default branch in the last 90 days | 2 commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
Both replace AWS Verified Permissions. Alternatives to AWS Verified Permissions →
PartialCerbosPolicy-based RBAC and ABAC written in YAML and evaluated by a service you run; open core.
PartialTopazFine-grained authorization combining OPA policies with a Zanzibar-style relationship store, self-hosted.
Both replace Oso Cloud. Alternatives to Oso Cloud →
PartialCerbosDeclarative authorization policies evaluated by your own service instead of a hosted one.
PartialTopazPolicies and a relationship directory run on your own infrastructure.
Cerbos
Cerbos
✓ signed The latest release, v0.56.0, carries a signature GitHub verified.
Loading the security report
Topaz
✓ signed The latest release, v0.33.22, carries a signature GitHub verified.
Loading the security report