Warrant is an authorization service written in Go. Its README describes “a relationship based access control (ReBAC) engine (inspired by Google Zanzibar)” that also covers role-based and attribute-based rules, and writes a relationship as [user:1] is an [editor] of [document:docA] (README). A stored relationship is called a warrant.
WorkOS acquired Warrant in 2024. The date, 2024-04-23, comes from a WorkOS post on X (post): X did not serve the page to this site’s checker, so the date was decoded from the post’s ID, and the post’s text (“Today, we are excited to announce the acquisition of @warrant_dev”) was seen only in a search result. No first-party WorkOS blog post was found. The Warrant website now reads “Warrant —> Now WorkOS FGA” (warrant.dev), and the README links to the WorkOS FGA docs.
Paper and Warrant side by side
The Warrant documentation site is gone, so this table is drawn from the open-source code.
| In the paper | In Warrant (open source) |
|---|---|
| Namespace config (§2.3) | An object type: JSON with type and relations, each relation a rule (spec.go) |
Relation tuple object#relation@user (§2.1) |
A warrant: objectType, objectId, relation and a subject with objectType, objectId and an optional relation |
_this |
Direct warrants, which a check always tries first (“1. Check for direct warrant match”, check/service.go) |
computed_userset |
{ "inheritIf": "owner" } |
tuple_to_userset |
{ "inheritIf": "viewer", "ofType": "folder", "withRelation": "parent" } |
| Union, intersection, exclusion | inheritIf set to anyOf, allOf or noneOf, with nested rules |
| Zookie (§2.2, §2.4) | The Warrant-Token header; the open-source server acts only on the value latest (see Consistency) (wookie.go) |
| Check (§2.4.4) | POST /v2/check (also /v2/authorize) |
| Read (§2.4.1) | GET /v2/warrants; GET /v2/query for queries over the graph |
| Write (§2.4.2) | POST /v2/warrants, DELETE /v2/warrants |
| Watch (§2.4.3) | None |
| Expand (§2.4.5) | None |
| Leopard (§3.2.4) | None |
| Spanner (§3.1) | MySQL, PostgreSQL or SQLite, with an optional read replica |
The running example as object types
The paper’s Figure 1 makes owners editors, editors viewers, and viewers of the parent folder viewers of the document (§2.3.1). In Warrant each object type lists its relations; an empty object {} means “direct warrants only”, and inheritIf adds a rule.
[
{ "type": "group", "relations": { "member": {} } },
{ "type": "folder", "relations": { "viewer": {} } },
{
"type": "doc",
"relations": {
"parent": {},
"owner": {},
"editor": { "inheritIf": "owner" },
"viewer": {
"inheritIf": "anyOf",
"rules": [
{ "inheritIf": "editor" },
{ "inheritIf": "viewer", "ofType": "folder", "withRelation": "parent" }
]
}
}
}
]
There is no user entry: the server creates a built-in user object type in its initial database migration (migration). The rule with ofType and withRelation finds the warrants doc:readme#parent@folder:… and checks viewer on each folder found, as in the check code (getMatchingSubjectsBySubjectType in check/service.go).
The five warrants of the running example, as POST /v2/warrants bodies:
{ "objectType": "doc", "objectId": "readme", "relation": "owner", "subject": { "objectType": "user", "objectId": "anne" } }
{ "objectType": "group", "objectId": "eng", "relation": "member", "subject": { "objectType": "user", "objectId": "beto" } }
{ "objectType": "doc", "objectId": "readme", "relation": "viewer", "subject": { "objectType": "group", "objectId": "eng", "relation": "member" } }
{ "objectType": "doc", "objectId": "readme", "relation": "parent", "subject": { "objectType": "folder", "objectId": "A" } }
{ "objectType": "folder", "objectId": "A", "relation": "viewer", "subject": { "objectType": "user", "objectId": "chen" } }
Which warrant and which rule decide each person’s viewer relation to the readme?
Architecture
Which database answers a request?
- One Go service serves the HTTP API (router.go).
- MySQL and PostgreSQL configurations take a
dsnand an optionalreaderDsn(config.go); SQLite is also supported, “in-memory or file” (README). - The rule for choosing a pool is a comment in sql.go: use the writer if the call is a write, if there is no reader, if the context “contains ‘latest’ wookie”, or if code inside the server has set a writer override; otherwise use the reader.
Consistency
Warrant’s code calls its token a wookie (wookie). A Token type holds an ID, a version and a timestamp, but the open-source server never sends one to the client: the warrant service returns nil in that slot and the HTTP handlers ignore it (warrant/service.go, warrant/handlers.go). What the server does read is the request header Warrant-Token, and only one value changes behaviour: latest.
What does Warrant-Token: latest change for a check right after a write?
The README itself says that low latency at high throughput “requires running Warrant as a distributed service with the use of Warrant-Tokens (also referred to as Zookies in Google Zanzibar)”, and that “this open source version of Warrant is only capable of handling low-to-moderate throughput” (README, vendor-authored). Its link for Warrant-Tokens now leads to the general WorkOS FGA overview, which does not describe them.
Notice the difference from the paper. A zookie sets a lower bound, which allows Zanzibar “to choose any timestamp fresher than the one encoded in a zookie” and to serve most checks “at a default staleness with already replicated data” (§2.2). latest has no point in time in it: it moves the read to the primary, which is the freshest copy but gives up the replica.
Differences from the paper
- No snapshot tokens in the open-source server, as above.
- RBAC and ABAC built in. Built-in object types for roles, permissions, tenants, pricing tiers and features, and policy conditions on warrants (README, migration).
- A query language.
GET /v2/queryanswers listing questions that the paper’s Read and Expand do not (query handlers). - No Watch, Expand or Leopard, and a single SQL primary instead of Spanner (§3.1).
Status
- Open source: first release v0.1.0 on 2023-02-23; last release v1.15.1 on 2024-06-10; last commit on 2025-12-05, a README change; not archived; about 1.3k stars (releases, GitHub API, 2026-11-13).
- Company: acquired by WorkOS, announced on X on 2024-04-23 (see above; the post itself could not be loaded).
- Product: WorkOS FGA. Its current documentation does not mention Warrant or Zanzibar. It presents FGA as an extension of WorkOS RBAC: “You configure resource types in the WorkOS Dashboard”, and FGA “can be adopted incrementally, with no data migration or confusing schema DSL” (WorkOS FGA docs, vendor-authored). The object-type JSON on this page is the open-source format, not WorkOS FGA’s.
Sources
- Warrant repository and README: github.com/warrant-dev/warrant
- Object type spec: pkg/authz/objecttype/spec.go
- Check engine: pkg/authz/check/service.go
- Tokens: pkg/wookie
- Database pools: pkg/database/sql.go, pkg/config/config.go
- Default object types: 000002_create_default_obj_types.up.sql
- Test fixtures: tests/v2/authz.json
- Website: warrant.dev
- WorkOS post on X: x.com/WorkOS/status/1782774170146791776
- WorkOS FGA docs: workos.com/docs/fga