Skip to content
Start with Identity
Authorization

AuthZed

Founded 2020New York, New York, USAPrivate (open source)Score 4.3/5Evaluated 2026-09-20Website ↗

Capability scores

Methodology →
Authentication
2.0
SSO & Federation
2.0
Authorization
5.0
Lifecycle & Provisioning
2.5
MFA & Passwordless
1.5
Governance & Audit
3.5
Developer Experience
4.5
Deployment Flexibility
4.5
Pricing Transparency
3.5
Support & Ecosystem
3.0

Scored 0–5 against a published rubric. Independent analysis, no vendor sponsorship.

Overview

AuthZed builds SpiceDB, the open-source authorization database inspired by Google's Zanzibar paper, plus a managed cloud, a dedicated offering and a commercial self-hosted build. It is a relationship-based access control engine: permissions are modelled as a graph of relationships between subjects and objects, and checks traverse that graph. Founded in 2020, it raised a 12 million dollar Series A led by General Catalyst in June 2024, bringing total funding to 15.9 million dollars, with Canva and Turo as named customers.

SpiceDB is Apache 2.0 and has stayed that way, with roughly 7,100 GitHub stars and a current release of v1.56.2 from September 2026.

What it is good at

Zanzibar fidelity and operational maturity. SpiceDB models nested ownership, sharing, groups and hierarchies that flat RBAC cannot express, and its consistency controls are the strongest argument for it: ZedToken is the documented equivalent of Zanzibar's Zookie, with four per-request consistency modes from minimize_latency through fully_consistent, explicitly addressing the New Enemy Problem where stale permission data leaks access. OpenFGA offers a coarser opt-in consistency flag by comparison.

Pricing structure is a quiet advantage. AuthZed meters on compute capacity, by vCPU and region, rather than per relationship or per check, so storing more permission facts does not itself increase cost. AuthZed Cloud starts at 2 dollars per hour with no annual commitment.

Materialize reached general availability in September 2026 on the Dedicated tier, precomputing transitive relationships for deeply nested graphs where live traversal is too slow.

Where it falls short

Four capabilities are reserved to SpiceDB Enterprise: restricted API access, audit logging, rate limiting and Security Embargo. That last one means open-source users receive vulnerability detail only at public disclosure while paying customers get advance notice, which is a real consideration for self-hosters.

Funding is over two years stale with no announced Series B, and no customer count is published beyond two named logos.

The CVE record is honest but non-trivial, including a September 2026 cache-key flaw that could return a full permission grant where a conditional result was correct, and two separate incidents of datastore passwords written to logs.

As an authorization engine it does nothing for authentication, SSO or MFA, and relationship modelling has a genuine learning curve.

Pricing

SpiceDB free under Apache 2.0. AuthZed Cloud from 2 dollars per hour, hourly metered. SpiceDB Enterprise and Dedicated are quoted, priced on region and reserved vCPU. Model it with our TCO calculator.

Best for, and who should look elsewhere

Choose AuthZed when sharing, nesting and hierarchy dominate your permission model and you need consistency guarantees. Choose OpenFGA for CNCF governance, Oso for a unified model with SQL filtering, or Cerbos for stateless policy decisions. See OpenFGA vs AuthZed vs Cerbos.

Bottom line

The most faithful open-source Zanzibar implementation available, with capacity-based pricing that does not punish scale, provided you can live with Enterprise-gated audit logging and embargoed security disclosures.

AuthZed: frequently asked questions

How much does AuthZed cost?
SpiceDB self-hosted is free under Apache 2.0. AuthZed Cloud publishes one figure, deploying a permissions system from 2 dollars per hour, billed hourly and invoiced monthly in arrears with no annual commitment and a starter programme offering 700 dollars in credits. SpiceDB Enterprise, the self-hosted commercial build, is an annual subscription licensed per region and per vCPU, unpriced publicly. AuthZed Dedicated Cloud is tailored and based on reserved vCPU capacity. The important structural point is that AuthZed prices on compute capacity, not on relationships, tuples, requests or monthly active users, so cost does not scale with how many permission facts you store.
Is SpiceDB open source and has the licence changed?
SpiceDB is Apache 2.0 and remains so. There has been no relicensing event, no move to BUSL or SSPL, which is worth stating plainly given how many infrastructure projects have changed terms since 2023. The repository carries around 7,100 stars. SpiceDB Enterprise is a separate commercially licensed build of the same engine rather than a fork, and AuthZed runs it in its own managed services.
What do you lose by running open-source SpiceDB instead of Enterprise?
Four documented capabilities. Restricted API Access scopes which calls each service account may make. Audit Logging emits full request and response detail per API operation to a log sink. Rate Limiting applies distributed limits by endpoint, service account, header or CEL expression, currently marked tech preview. And Security Embargo gives private advance notice of vulnerabilities, with fixes and remediation time before public disclosure. That last one has a real consequence worth weighing: open-source users learn about SpiceDB vulnerabilities at public disclosure, paying customers learn earlier.
Is SpiceDB a true Zanzibar implementation?
It is the closest of the open-source options. SpiceDB implements token-based point-in-time consistency through ZedToken, which its documentation explicitly identifies as the equivalent of Zanzibar's Zookie, and names the New Enemy Problem it exists to prevent. Four consistency modes are exposed per request: minimize_latency, at_least_as_fresh, at_exact_snapshot and fully_consistent. OpenFGA offers an opt-in higher-consistency flag rather than token-based point-in-time consistency. If faithfulness to the Zanzibar paper matters to your design, SpiceDB is the stronger claim.
What is AuthZed Materialize?
Materialize precomputes transitive relationships across the authorization graph, periodically recomputing its view from a snapshot and consuming a live stream of relationship changes in between. It reached general availability on 10 September 2026 for AuthZed Dedicated only, after entering early access in February 2024. AuthZed states single-digit millisecond responses over billions of relationships in production since 2024. Event Streams remains early access; Accelerated Queries is the part that went GA. This is the answer to deeply nested permission graphs where live traversal becomes the bottleneck.
Does SpiceDB have known vulnerabilities?
Several, all patched, none severe enough to reach CISA KEV. The most recent is CVE-2026-55866, published 14 September 2026 at CVSS 3.7: cache keys for dispatch checks omitted CheckHints, so SpiceDB could return a full permission grant where a conditional or negative result was correct. It affects 1.34.0 up to 1.54.0 and is fixed in 1.54.0. Earlier: CVE-2026-46668 (2.3, improper cache reuse with nested caveat lists, fixed 1.52.0), CVE-2026-40091 (datastore connection string including a plaintext password written to startup logs, fixed 1.51.1), CVE-2023-46255 (similar log exposure) and CVE-2023-29193 (8.1, metrics port bound to untrusted networks leaking command-line flags). The pattern is authorization-logic and log-hygiene bugs rather than remote code execution.
How well funded is AuthZed?
Its last disclosed round was a 12 million dollar Series A announced 27 June 2024, led by General Catalyst with Work-Bench, Y Combinator and Amplify Partners, bringing total raised to 15.9 million dollars. Canva and Turo were named as customers. No funding has been announced since, so that figure is now over two years old. At the time SpiceDB had more than 4,500 GitHub stars; it has roughly 7,100 as of September 2026.
What are the best AuthZed alternatives?
OpenFGA, which reached CNCF Incubating maturity in October 2025, if vendor-neutral foundation governance matters more than Zanzibar fidelity. Oso if you want one model spanning roles, relationships and attributes with SQL-level data filtering rather than a relationship database. Cerbos if stateless policy decisions without a central relationship store fit better. Permit.io for a more managed, product-led experience. Stay with SpiceDB when sharing, nesting and hierarchy dominate your permission model and consistency guarantees matter.
Last reviewed By SWI Community TeamSuggest a correctionHow we research

By SWI Community Team · Last evaluated 2026-09-20

Independent, community-driven analysis. No vendor sponsorship. Compiled from public research and community input and verified on a best-effort basis, so details may be incomplete or out of date. Scores are opinions, not advice. Trademarks belong to their owners; mention does not imply affiliation or endorsement. See the full disclaimer, or send corrections to community@startwithidentity.com.