aserto-dev/topaz
Cloud-native authorization for modern applications and APIs observed · 2026-08-28
Health v2 · maintenance only
99/100
- Activity 99
- Release rhythm 99
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 7.0
- age_days: 1410
- days_rel: 7
- days_push: 8
- n_releases_24m: 57
Adoption not part of the score
1360 stars · 45 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
Topaz is an open-source, cloud-native authorization service that provides fine-grained, real-time, policy-based access control for applications and APIs. It combines Open Policy Agent (OPA) as its decision engine with a built-in directory inspired by Google's Zanzibar data model, storing users, groups, objects, and relationships in an embedded local database for fast decisions.
Use cases
- centralize authorization logic instead of scattering it across application code
- implement RBAC, ABAC, or ReBAC access control for APIs and applications
- check if a user has permission to access a document or resource in real time
- deploy an authorizer as a sidecar next to my app for low-latency decisions
- model users, groups, and relationships in a Zanzibar-style directory
- audit and log every authorization decision for compliance
- manage authorization policies as code with signed OCI artifacts
When to choose
- you need fine-grained, real-time authorization (RBAC, ABAC, ReBAC or combinations) for cloud-native apps
- you want to separate authorization logic from application code with a policy-as-code workflow
- you want OPA-style policy rules combined with a Zanzibar-style relationship directory in one self-hosted service
- you need decision logging for audit trails and compliance
- you want SDKs and middleware for Node.js, Go, Python, Java, .NET, or Ruby
When to avoid
- you only need simple role checks that a lightweight in-app library can handle
- you prefer a fully managed hosted authorization service rather than self-hosting
- your stack has no supported SDK and you cannot integrate via gRPC/REST
- you need a solution with no Docker/container runtime dependency, since the authorizer runs as a container
Facets
service · maturity active
authorization auth api-gateway middleware database security backend apis developer-tools self-hosted windows self-hosted go cloud zanzibar opa rbac abac rebac policy-as-code access-control sidecar grpc fine-grained-authorization linux macos docker
10 sources
- readme: https://github.com/aserto-dev/topaz · fetched 2026-08-28 · a902a3aed353
- homepage: https://www.topaz.sh · fetched 2026-08-29 · c49445b5fcfb
- site_page: https://www.topaz.sh/docs/intro · fetched 2026-08-29 · 32e0f22e4fbf
- site_page: https://www.topaz.sh/docs/getting-started · fetched 2026-08-29 · edc57e8c70f1
- site_page: https://www.topaz.sh/docs/software-development-kits/javascript/express · fetched 2026-08-29 · dfe4daddb180
- site_page: https://www.topaz.sh/docs/software-development-kits/go/install · fetched 2026-08-29 · 6f82cf84146c
- site_page: https://www.topaz.sh/docs/software-development-kits/python/api-client · fetched 2026-08-29 · 038e8dbc64c1
- site_page: https://www.topaz.sh/docs/software-development-kits/java/authorizer · fetched 2026-08-29 · 64677885b676
- site_page: https://www.topaz.sh/docs/software-development-kits/dotnet/dotnetcore · fetched 2026-08-29 · 0b8057bb4e81
- site_page: https://www.topaz.sh/docs/software-development-kits/ruby/middleware · fetched 2026-08-29 · 4088c5d504cc
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| aserto-dev/topaz | main | 99 |
For agents
markdown · JSON · MCP: product_card(name="aserto-dev/topaz")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem