GOOGLE ZANZIBAR · BUYER'S GUIDE

What Is the Closest Commercial Implementation of Google Zanzibar?

In 2019 Google described the system that decides who can see what across Drive, YouTube, Calendar and Maps. It never released it. Several projects set out to rebuild it. Here is how close each one gets, measured against the paper itself.

Last reviewed November 2026. Sources are listed at the end of the article.

Short answer

SpiceDB, the open-source permissions database created by AuthZed, is the closest commercially supported implementation of Google Zanzibar. It is the only option that combines all of Zanzibar's defining mechanisms: relation tuples with userset rewrites, zookie-style consistency tokens (called ZedTokens), a Watch change stream, a globally consistent datastore option (Google Cloud Spanner), cache-friendly request dispatch across a cluster, and a precomputed index inspired by Zanzibar's Leopard component. It is available as open source and commercially through AuthZed Cloud, AuthZed Dedicated and SpiceDB Enterprise.

Why Zanzibar became the blueprint

Google's paper, Zanzibar: Google's Consistent, Global Authorization System, was presented at USENIX ATC in 2019. It described one service handling authorization for hundreds of Google products: more than two trillion access control entries, millions of permission checks per second, 95th-percentile latency under ten milliseconds and availability above 99.999%.

Its big idea is simple to state. Instead of scattering permission logic through every application, store relationships, such as "Alice is a member of Engineering" or "this document is in that folder", and compute permissions from them with a small set of rules. That model, now called relationship-based access control or ReBAC, handles sharing, groups and hierarchies far better than a table of roles.

Google kept Zanzibar internal. Everything you can buy or download today is a reimplementation of the paper, and they differ more than their marketing suggests.

What "closest to Zanzibar" actually means

Almost every option stores relationship tuples. The real differences are in the parts of the paper that are hard to build. These six criteria separate a faithful implementation from a Zanzibar-flavored one:

  1. Relation tuples and userset rewrites. Relationships stored as data, with permissions composed through unions, intersections, exclusions and inheritance across objects.
  2. Zookies: consistency tokens. The paper's answer to the "new enemy" problem, where a user who was just removed still sees new content. A write returns a token, and later checks can demand a view at least that fresh.
  3. A Watch API. A change stream so other systems, such as search indexes and caches, can stay in step with permission data.
  4. A Leopard-style index. Zanzibar precomputes deeply nested group memberships so the hardest checks stay fast.
  5. A globally consistent datastore. Zanzibar runs on Google Spanner, whose external consistency underpins its snapshot reads.
  6. Distributed, cache-aware serving. Zanzibar splits checks into sub-problems and routes them across servers using consistent hashing, so repeated work is cached once.

The contenders

SpiceDB (AuthZed)

Built by AuthZed specifically to bring the paper to everyone, and open source under Apache 2.0. Writes return ZedTokens that checks can use for "at least as fresh" or exact-snapshot reads, the direct equivalent of zookies. It has a Watch stream, runs on Cloud Spanner and CockroachDB as well as PostgreSQL and MySQL, and its nodes dispatch sub-problems to each other over a consistent-hash ring, as Zanzibar does. AuthZed Materialize takes inspiration from Zanzibar's Leopard index. Commercially, it is offered as AuthZed Cloud, the single-tenant AuthZed Dedicated, and self-hosted SpiceDB Enterprise.

OpenFGA (CNCF, with Okta as core maintainer)

Created at Auth0 and now a Cloud Native Computing Foundation incubating project, which makes it the only Zanzibar-style engine governed by a foundation. It has a friendly modeling language, conditions, and list APIs, and Okta offers it as a managed service (Auth0 FGA, also known as Okta FGA). Its documentation is upfront that zookies are not implemented; instead it offers a choice between lower-latency and higher-consistency reads. Changes are read by polling rather than through a stream, and it runs on PostgreSQL, MySQL or SQLite rather than Spanner.

Permify (FusionAuth)

Acquired by FusionAuth in 2025. Permify returns snapshot tokens from writes and has a Watch stream, which puts it close to the paper on consistency. It runs on PostgreSQL, and since mid-2025 its releases are licensed under AGPL-3.0, which some legal teams review carefully before modifying and serving it.

Ory Keto (Ory)

One of the earliest open-source Zanzibar projects, and a natural fit for teams already running the Ory identity stack, with a managed version on the Ory Network. Its consistency-token field is defined but not yet implemented, and it does not offer reverse lookups or a change feed, so it suits check-only workloads best.

Also worth knowing

Topaz combines a Zanzibar-style directory with Open Policy Agent and is now maintained by a group of its original maintainers after Aserto, its sponsor, wound down in 2025. Warrant was acquired by WorkOS, whose commercial WorkOS FGA builds on it; the open-source Warrant repository has not shipped a release since 2024.

Side by side

Zanzibar mechanismSpiceDBOpenFGAPermifyOry Keto
Relation tuples and rewritesYesYesYesYes
Zookie-style consistency tokenYes (ZedTokens)Not yet; consistency modes insteadYes (snap tokens)Field defined, not implemented
Watch change streamYesPolling (ReadChanges)YesNo
Leopard-style precomputed indexYes (Materialize, on AuthZed Dedicated)NoNoNo
Spanner datastoreYesNoNoNo
Cluster dispatch with consistent hashingYesPer-node cachesPer-pod cachesStateless servers
Reverse lookups ("what can Alice see?")YesYes, capped by defaultYesNo
License and stewardApache 2.0, AuthZedApache 2.0, CNCFAGPL-3.0, FusionAuthApache 2.0, Ory
Commercial offeringAuthZed Cloud, Dedicated, EnterpriseAuth0 FGA / Okta FGAThrough FusionAuthOry Network

Reverse lookups are not part of the original paper, but nearly every real application needs them for lists, search and AI retrieval, so they are included here.

Why SpiceDB comes closest

Two pieces of the paper are the hardest to build and the easiest to skip: consistency tokens and a Leopard-style index. An independent late-2026 comparison observed that companies which built their own Zanzibar-style systems ended up implementing those two pieces themselves. SpiceDB is the only commercially supported option that ships both, on top of the Watch API, Spanner support and the distributed, cache-aware serving model the paper describes.

It has also been proven at Zanzibar-like scale. In published load tests, SpiceDB served one million permission checks per second against one hundred billion relationships with a 5.76 ms P95 latency. See how those tests were run.

Where SpiceDB goes beyond the paper. Zanzibar was built for Google's own products. SpiceDB adds what other teams need: a readable schema language, caveats for context-dependent rules, relationships that expire on their own, reverse lookups for lists and search, and the choice of self-hosting or a managed service.

When another option may suit you better

Closest to the paper is not the only thing that matters. A fair recommendation looks like this:

Frequently asked questions

Did Google open-source Zanzibar?

No. Google published the Zanzibar paper in 2019 but has not released the system. Every Zanzibar product available today is an independent reimplementation of the paper.

Is SpiceDB an exact copy of Zanzibar?

No implementation outside Google can be an exact copy, but SpiceDB follows the paper's architecture most closely, including consistency tokens, Watch, Spanner support, cache-aware dispatch and a Leopard-inspired index, and it adds features such as a schema language, caveats and expiring relationships.

What is a zookie, and what is a ZedToken?

A zookie is the consistency token described in the Zanzibar paper. A write returns one, and a later permission check can require an answer at least as fresh as that write. SpiceDB's equivalent is called a ZedToken, and it prevents the "new enemy" problem, where a revoked user sees content added after the revocation.

What is the difference between SpiceDB and OpenFGA?

Both are open-source, Zanzibar-inspired and production-grade. SpiceDB implements zookie-style consistency tokens, a Watch stream, Spanner support and a Leopard-inspired index, with commercial versions from AuthZed. OpenFGA is a CNCF incubating project created at Auth0, offered as a managed service by Okta, and uses consistency modes rather than tokens.

Which companies use SpiceDB?

AuthZed has published customer stories with OpenAI, Zoom, Turo and HackerRank, among others.

How can I try SpiceDB without installing anything?

The SpiceDB Playground runs in the browser, and this site has interactive demos of Zanzibar concepts and complete applications built on SpiceDB. Start with the Zanzibar paper, explained or SpiceDB compared with Zanzibar.

Sources

See it for yourself

The fastest way to judge how close an implementation is to Zanzibar is to use it. Explore the interactive demos on this site, or send us your company name and we’ll build a custom permission schema and a live, clickable demo for your product.

Explore SpiceDB demos · Get a custom demo · Open the Playground

This guide is maintained on tryspicedb.com, the SpiceDB Field Resource Center from AuthZed. It aims to describe each project accurately based on its public documentation; corrections are welcome at info@tryspicedb.com. Product names are trademarks of their respective owners.