system:compare@en

Ecosystem

Zanzibar-style systems compared

SpiceDB, OpenFGA, Permify, Ory Keto, Topaz and Warrant set against the paper, one concern at a time.

Facts checked on Paper sections §2.1, §2.2, §2.3.1, §2.4, §3, §3.2.4

Several open-source projects describe themselves as inspired by or modelled on Zanzibar. This page lines six of them up against the paper, one concern per table. Cells are short; the sources for every row are listed under each table. Facts were checked on 2026-11-13 and come from each project’s own repository and documentation, so most are vendor-authored.

The six: SpiceDB (AuthZed), OpenFGA (CNCF), Permify (FusionAuth), Ory Keto (Ory), Topaz (its maintainers, after Aserto wound down) and Warrant (WorkOS). Each has its own page: SpiceDB, OpenFGA, Permify, Ory Keto, Topaz, Warrant.

Schema language

The paper calls it a namespace configuration: relations with userset rewrite rules (§2.3). Figure 1 writes one in a protocol-buffer-style text syntax; the paper does not name the format.

System Schema language Format
Paper Namespace config Protobuf-style text in Figure 1 (format not named)
SpiceDB Schema (definition, relation, permission) Own language
OpenFGA Authorization model (type, define) DSL, compiled to JSON
Permify Permify Schema (entity, relation, permission / action, attribute, rule) Own language
Ory Keto Ory Permission Language (OPL) TypeScript subset
Topaz Manifest (types, relations, permissions) YAML, version: 3
Warrant Object types (inheritIf, rules) JSON

Sources: SpiceDB schema · OpenFGA configuration language · Permify modeling · Ory Permission Language · Topaz manifest reference · Warrant spec.go

Tuple syntax

The paper writes a tuple as object#relation@user, where the user can itself be a userset object#relation (§2.1). The rows below show Beto’s group being viewers of the readme where the docs give a string form.

System Name Shape
Paper Relation tuple doc:readme#viewer@group:eng#member
SpiceDB Relationship doc:readme#viewer@group:eng#member
OpenFGA Relationship tuple user group:eng#member, relation viewer, object doc:readme
Permify Relational tuple doc:readme#viewer@group:eng#member
Ory Keto Relation tuple Doc:readme#viewers@Group:eng#members
Topaz Relation Fields object_type, object_id, relation, subject_type, subject_id, optional subject_relation
Warrant Warrant [user:1] is an [editor] of [document:docA] (README’s example)

Sources: SpiceDB relationships · OpenFGA concepts · Permify sync data · Ory Keto relation tuples · Topaz common.proto · Warrant README

Rewrite operators

The paper’s rewrite rules combine three leaves, _this, computed_userset and tuple_to_userset, with union, intersection and exclusion (§2.3.1).

System Union / intersection / exclusion computed_userset tuple_to_userset
Paper union / intersection / exclusion computed_userset tuple_to_userset
SpiceDB + / & / - Name a relation or permission parent->view (also .any(); .all() intersects)
OpenFGA or / and / but not Bare relation name viewer from parent
Permify or / and / not Bare name Dot: org.admin
Ory Keto || / && / ! this.permits.x(ctx) .traverse(...)
Topaz | / & / - Name a relation or permission parent->can_read
Warrant anyOf / allOf / noneOf inheritIf ofType + withRelation

Sources: SpiceDB schema · OpenFGA equivalent Zanzibar concepts · Permify modeling · Ory Permission Language · Topaz manifest reference · Warrant spec.go

Consistency token and modes

The paper’s zookie is “an opaque byte sequence encoding a globally meaningful timestamp” (§2.4); a check is evaluated at a snapshot no earlier than the zookie it carries (§2.2, §2.4.4).

System Token Modes or behaviour
Paper Zookie With zookie: at least as fresh; without: “a reasonably recent snapshot” (§2.4.1)
SpiceDB ZedToken minimize_latency, at_least_as_fresh, at_exact_snapshot, fully_consistent
OpenFGA None MINIMIZE_LATENCY (default), HIGHER_CONSISTENCY; cache off by default
Permify Snap Token Returned by Write, passed to Check as snap_token; without one, the latest transaction
Ory Keto snaptoken field “not implemented yet and has no effect”
Topaz None documented No token fields in the reader API
Warrant Warrant-Token header The open-source server returns no token and acts only on latest, which sends the read to the primary database

Sources: SpiceDB consistency · OpenFGA consistency · Permify snap tokens · Keto check_service.proto · Topaz reader.proto · Warrant wookie.go, sql.go, warrant/service.go

Which products carry something in the zookie’s place?

What each system uses in place of the zookieThe paper's zookie sits in the centre. Solid arrows connect it to the two working equivalents: SpiceDB's ZedToken and Permify's Snap Token. Dashed lines lead to systems without a working token: Warrant's open-source server understands only Warrant-Token: latest, OpenFGA has no token, Topaz documents none, and Ory Keto has snaptoken fields that are not implemented.zookie(paper §2.4)SpiceDBZedTokenPermifySnap TokenWarrantWarrant-Token: latest onlyOpenFGAnoneTopaznone documentedOry Ketosnaptoken: not implementedequivalent
Solid: a token the client gets back from a write and can carry, as with zookies. Dashed: no working token; Warrant's open-source server has a header that only means “read the primary”, and OpenFGA offers two consistency modes instead.

Notice that only the two solid links let an application say “at least as fresh as my write”, which is what protects against the new-enemy problem in the paper (§2.2).

Watch and changelog

The paper’s Watch streams tuple changes from a changelog, with heartbeat zookies to resume from (§2.4.3, §3).

System API Shape
Paper Watch Stream, resumable with a zookie
SpiceDB Watch Stream, resumable with a ZedToken (changes_through)
OpenFGA ReadChanges Paginated read with a continuation token (polled)
Permify Watch Stream (stream WatchResponse)
Ory Keto None No watch service in the protocol files
Topaz None No watch service in the protocol files
Warrant None No change or event endpoint in the repository

Sources: SpiceDB watch_service.proto · OpenFGA openfga_service.proto · Permify service.proto · Keto protos · Topaz go-directory protos · Warrant repository

Leopard-like index

Leopard is the paper’s index for large and deeply nested groups, built from snapshots and Watch updates (§3.2.4).

System Precomputed index Note
Paper Leopard Serving, offline and incremental parts (§3.2.4)
SpiceDB AuthZed Materialize Commercial, for AuthZed Dedicated customers; “takes inspiration from the Leopard index component”
OpenFGA None documented Check and iterator caches
Permify None documented “process-local cache; there is no shared cache layer”
Ory Keto None documented
Topaz None documented
Warrant None documented

Sources: AuthZed Materialize · OpenFGA consistency (cache flags) · Permify cache · Ory Keto docs · Topaz architecture · Warrant repository. “None documented” means the pages listed describe no such index, not that one was ruled out.

Storage

The paper stores tuples, configs and the changelog in Spanner (§3, §3.1).

System Datastores
Paper Spanner
SpiceDB CockroachDB, Cloud Spanner, PostgreSQL, MySQL (not recommended), memdb (development)
OpenFGA memory (default), PostgreSQL, MySQL, SQLite
Permify PostgreSQL, memory
Ory Keto PostgreSQL, MySQL, CockroachDB, SQLite (not for production)
Topaz Embedded BoltDB
Warrant MySQL, PostgreSQL, SQLite

Sources: SpiceDB datastores · Configure OpenFGA · Permify configuration · Ory deployment · Topaz architecture · Warrant migrations

License

System License Language
SpiceDB Apache-2.0 Go
OpenFGA Apache-2.0 Go
Permify AGPL-3.0 (Apache-2.0 from 2023-02-14 until 2025-05-12) Go
Ory Keto Apache-2.0 Go
Topaz Apache-2.0 Go
Warrant Apache-2.0 Go

Sources: each repository’s LICENSE file, read through the GitHub API: SpiceDB · OpenFGA · Permify · Ory Keto · Topaz · Warrant. Permify’s LICENSE file history, read at each commit that touched it: Apache-2.0 (2022-07-14), GPL-3.0 (2022-08-25), AGPL-3.0 (2022-08-26), Apache-2.0 (2023-02-14), AGPL-3.0 (2025-05-12).

Status

As of 2026-11-15.

System Owner Latest release Status
SpiceDB AuthZed v1.57.1 (2026-11-10) Active
OpenFGA CNCF; Okta is a core maintainer v1.22.1 (2026-10-28) Active, CNCF Incubating (moved 2025-10-28, announced 2025-11-11)
Permify FusionAuth (acquired 2025-11-20) v1.7.6 (2026-11-05) Active; docs moved to fusionauth.io
Ory Keto Ory v26.2.0 (2026-03-20) Active
Topaz Its maintainers, under the aserto-dev organization v0.33.28 (2026-11-14) Active; Aserto wound down as a company (2025-04-27 post)
Warrant WorkOS v1.15.1 (2024-06-10) No release since; not archived; warrant.dev reads “Now WorkOS FGA”

Sources: releases and repository metadata from the GitHub API for each repository above · CNCF on OpenFGA · CNCF project page · Auth0 FGA docs · Permify acquisition post · FusionAuth post · Aserto, “The final chapter” · warrant.dev

zanzibar.tech is “The Google Zanzibar Paper, annotated by AuthZed”: the paper’s text with AuthZed’s notes alongside (“Annotations © 2026 AuthZed, Inc. Zanzibar Paper © USENIX and original authors”). Its source is on GitHub at authzed/zanzibar-annotated. The annotations are written by the company that makes SpiceDB.

Sources