compare
SpiceDB vs Topaz
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | SpiceDB | Topaz |
|---|---|---|
| Language | Go | Go |
| Licence | Apache-2.0 | Apache-2.0 |
| Stars | 7.2k | 1.4k |
| Latest | v1.56.2 | v0.33.22 |
| Last push | 2026-10-18 | 2026-10-14 |
| Release cadence | about 34 days between releases | about 7 days between releases |
| Active contributors | 13 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 →
PartialSpiceDBZanzibar-style relationship checks instead of Cedar policies, run on your own infrastructure.
PartialTopazFine-grained authorization combining OPA policies with a Zanzibar-style relationship store, self-hosted.
Both replace Oso Cloud. Alternatives to Oso Cloud →
PartialSpiceDBRelationship-based permissions in the style of Google Zanzibar, self-hosted instead of a hosted service.
PartialTopazPolicies and a relationship directory run on your own infrastructure.
SpiceDB
- v1.56.22026-09-11Increase the timeout for datastore readiness checks to account for the possibility of far away databases
- v1.56.12026-08-26Schema compilation: reduce memory usage when caveats are involved
- v1.56.02026-07-24New metric check_permissionship_total for CheckPermission and CheckBulkPermissions that counts the number of requests t…
- v1.54.02026-06-18Prevent cache poisoning. The dispatch Check cache key now incorporates check hints. See
- v1.53.02026-05-13Add DispatchExecutor, a query plan executor that is Dispatch-aware and sends subproblems on Alias boundaries
SpiceDB
✓ signed The latest release, v1.56.2, 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