AuthZed

Name: AuthZed
Brand: AuthZed

AI Native

Creators of SpiceDB: open-source permissions database inspired by Google's Zanzibar. YC W21.

Est 2020|Valuation $50M|Raised $16M|20 Ref Customers

LinkedIn 4K|Web traffic 12K|FTEs 36|HQ New York, New York, US

Published Oct 15, 2026

01Common complaints

1) Only authentication/SSO and coarse RBAC are required - For many organizations, an identity provider combined with application-level checks is sufficient and simpler than deploying a dedicated permissions database. 2) Core need is ABAC over very large datasets with rich search - Community discussions describe potential challenges integrating Zanzibar-style permission graphs with high-scale attribute-based filtering and search; alternative architectures or hybrid approaches may be more suitable. 3) Inability to manage operational complexity (if self-hosting) - Operating SpiceDB requires observability, capacity planning, backing datastore management, and performance tuning. 4) Requirement for public compliance attestations prior to procurement - If procurement processes require publicly accessible SOC 2 or ISO artifacts prior to engagement, and those artifacts are not available publicly, the sales process may be delayed until documentation is provided under NDA. 5) Strict multi-tenant isolation within a single cluster as a hard requirement - Historical discussions have indicated that multi-tenancy was a non-trivial topic; buyers should validate the current state of multi-tenant features and topology support.

Deal disqualifiers

Requirements limited to simple RBAC or authentication-only capabilities that can be handled by an identity provider and in-application checks
Workloads dominated by ABAC or large-scale search where relationship modeling would not be the primary enforcement mechanism
Organizations unwilling or unable to accommodate operational complexity when self-hosting

Observed limitations from community and vendor sources

- Consistency mode tradeoffs: Different consistency modes have tradeoffs between latency and freshness; fully consistent reads may bypass caching and increase latency, and other modes can have non-obvious performance implications in certain environments. - Multi-tenancy: Historical issue discussions indicated that built-in multi-tenant topologies were not present in early versions; confirm the current status for tenant isolation requirements. - Memory protection and backpressure behavior: The system includes a memory protection middleware that can reject requests with HTTP 429 under high memory usage to protect overall stability; operators should plan capacity and handle retry/backoff logic.

Roadmap and vendor-stated forthcoming features

The vendor has described upcoming APIs for efficiently synchronizing systems with materialized permissions; buyers should verify current availability and timelines during procurement.

02Why they buy

Evidence-backed differentiators

Open-source ecosystem: SpiceDB and related tooling (operator, clients, CLI, and playground) provide an extensible base for teams that require customization or visibility into the implementation.
Zanzibar-inspired design and explicit consistency tooling (such as consistency tokens) are documented in vendor materials and are core conceptual differentiators compared with simpler RBAC systems.

Potential areas of differentiation versus alternatives

Support for multiple backing datastores (including Spanner and CockroachDB) may be relevant for enterprise architectures.

Areas where competitors may have advantages

Policy-language approaches (for example, Oso) may be more suitable when authorization logic is not naturally expressed as relationship graphs.
Some hosted competitors emphasize packaged compliance and SLAs; buyers should verify these claims with documentation.

03Field reports

Review-platform reality check (Gartner/G2/TrustRadius)

Searches did not surface robust listings for AuthZed/SpiceDB on mainstream review platforms in the accessible results. Some review platform queries returned pages primarily for other vendors. As a result, public third-party review coverage appears limited.

Implication: Assessment of the vendor may rely more on reference calls, open-source community signals (GitHub issues and discussions), technical benchmarks, and vendor-provided case studies.

Positive signals (vendor case studies / community)

1) Reddit Ads case study (vendor-published): - Reddit describes migrating from a homegrown system to SpiceDB and reports that the rollout did not create noticeable impact for end users, according to the vendor-published narrative. - The case study includes a statement that Reddit security audited the rollout and found no issues; no independent audit artifact was linked in the public case study. 2) Community showcase and events: - A vendor-hosted event lists speakers from organizations including Reddit, which supports claims of production usage, though this is vendor-curated. 3) Open-source adoption signals: - The SpiceDB repository shows community activity such as stars and forks, which indicate interest and engagement but do not directly quantify production satisfaction.

Critical/negative feedback (community discussions)

1) Performance and consistency complexity: - A user reported substantial slowdown when using ZedTokens and specific consistency modes. The report indicates that consistency modes can have non-obvious performance tradeoffs and that real-world tuning may be required. 2) Interaction with ABAC and search patterns: - Community discussion described difficulties when attempting attribute-based access control (ABAC)-like filtering over very large datasets, including a potential tuple explosion when intersecting search results with permission tuples. This suggests that Zanzibar-style systems can be less natural for arbitrary attribute filtering combined with full-text or structured search workflows.

Reasons customers choose SpiceDB (inferred from sources)

Need for a Zanzibar-inspired engine with explicit consistency concepts and design intended for high-scale scenarios.
Desire to offload operation of a distributed permissions system via managed offerings rather than self-hosting the system.

Reasons some customers might leave or avoid the product

Based on community discussions and common pitfalls:

Organizations without the ability to invest in modeling expertise and performance tuning may not achieve desired results.
Teams whose primary need is ABAC combined with large-scale search access patterns may find a Zanzibar-only approach awkward without hybrid architectures.

Reddit Ads Implements Scalable Sharing Capabilities using SpiceDB (vendor-published)

Describes replacing a homegrown system and validating behavior through comparative testing.
The case study reports that a security audit identified no issues; no independent audit artifact was provided in the public case study.
As a vendor-published case study, the narrative is curated and should be supplemented with direct reference checks where possible.

Vendor benchmarking and scale testing (vendor-published)

- The vendor published benchmarking material that reports achieving very high QPS and handling very large relationship counts in a specific configuration (SpiceDB Dedicated with a particular backing datastore). Critical evaluation: - The published material includes methodology and iterative test discussion, which provides more context than an unsupported claim. - Because the benchmarking was conducted by the vendor, buyers should request reproducible configuration details, validation that the workload shape matches their own use case, and vendor-provided cost estimates to achieve comparable throughput.

04Best fit

Company sizes

Typical fit:

Mid-market to enterprise organizations and high-growth SaaS companies that expect increased authorization complexity and scale.
Organizations with platform or security engineering teams capable of investing in authorization modeling and operations.

Industries

Customers cited in vendor materials include organizations across healthcare, finance, gaming, and software. Vendor-asserted customer names appear in press materials; buyers should treat these as vendor statements and perform reference checks where necessary.

Roles and personas

Platform engineering and infrastructure teams
Security engineering
Senior backend engineers focused on authorization design
Product teams implementing complex sharing and collaboration models

Fit criteria

Complex permission graphs (sharing, delegation, groups, hierarchical resources)
Need for consistent, auditable authorization checks across distributed services
Willingness to centralize authorization and accept associated coupling between services

05The pitch

What the product does (core value proposition)

AuthZed provides authorization infrastructure centered on SpiceDB, an open-source permissions database inspired by Google’s Zanzibar model. The product is designed to store relationship-based permission data (who can do what to which resource) and answer authorization questions (for example, whether a specific user can view a specific document) in real time via APIs. AuthZed offers several delivery options: - Managed SpiceDB (Cloud / Dedicated Cloud) for teams that want to outsource operation of a low-latency, security-focused, distributed permissions system. - Self-hosted enterprise offerings (subscription/license plus support). - Open-source SpiceDB (free) and ecosystem tooling (operator, clients, CLI, playground).

Target market and market positioning

AuthZed targets engineering teams and platform teams that: - Require fine-grained authorization beyond coarse Role-Based Access Control (RBAC), such as document sharing, multi-resource graphs, delegation, and hierarchical permissions. - Need to scale permission checks to high request rates with low latency and strong correctness properties. - Prefer relationship-based access control (ReBAC) or Zanzibar-like authorization models and want a database-style system of record for permissions. The product is often applicable to platform teams and organizations operating multiple services that require a shared authorization layer (for example, microservices or multi-product suites).

Get a comprehensive analysis of AuthZed including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →