# warrant-dev/warrant

Warrant is a highly scalable, centralized authorization service based on Google Zanzibar. Use it to define, enforce, query, and audit application authorization and access control.

Repository: https://github.com/warrant-dev/warrant
Canonical: https://ross.abutalabs.com/products/warrant
Homepage: https://warrant.dev
Language: Go
License: Apache-2.0
License Family: permissive
Topics: access-control, authorization, golang, rbac, acl, fine-grained-access-control, fine-grained-authorization, permissions, abac, authz, role-based-access-control, ciam, rebac, zanzibar, iam, entitlements, pricing-tiers, zero-trust, relationship-based-access-control, fgac
Last push: 2025-12-05T19:39:14+00:00

## Health v2 (maintenance only)
Score: 46/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 55, release rhythm 8, longevity 92
- inputs: {"age_days": 1296, "days_push": 271, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1336, forks 53 (observed 2026-08-28T04:04:25.448877+00:00)

## What it is
Warrant is a highly scalable, centralized fine-grained authorization service inspired by Google Zanzibar, written in Go. It lets applications define, enforce, query, and audit access control rules supporting RBAC, ABAC, and ReBAC paradigms via HTTP APIs and SDKs.

## Use cases
- add role-based access control to a SaaS application
- check if a user is an editor of a document at runtime
- implement fine-grained permissions with tenants and pricing tiers
- self-service role and permission management for customers
- audit application access rules and entitlements
- integrate authorization with Auth0 or Firebase identity providers

## When to choose
- you need centralized, low-latency authorization checks across multiple applications
- you want Zanzibar-style relationship-based access control without building it yourself
- you need to support RBAC, ABAC, and ReBAC in one service

## When to avoid
- you only need simple authentication (authn), not authorization
- you want a fully managed service and prefer WorkOS FGA, its successor
- your stack cannot run a separate Go service or supported database

## Facets
- artifact type: service
- maturity: active
- function: authorization, api-framework, http-server
- domain: security, backend, web-development, developer-tools
- platform: self-hosted, windows, go
- tags: zanzibar, rebac, rbac, abac, fine-grained-authorization, access-control, entitlements, iam, docker, linux, macos

## Member repositories
- warrant-dev/warrant (main) score 46

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:25.448877+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T04:44:20.382951+00:00, confidence not recorded.
  - readme: https://github.com/warrant-dev/warrant (fetched 2026-08-28T04:04:25.448877+00:00, sha 4182d7d4f053)
  - homepage: https://warrant.dev (fetched 2026-08-29T12:03:31.556235+00:00, sha c1196c0bb116)
- Data as of 2026-08-30T08:39:29.467469+00:00.