open sourceSpiceDB Field Resources

Build great features. Not authorization.

See what modern authorization looks like with SpiceDB.

Explore interactive demos, understand Google Zanzibar-inspired ReBAC, and see how to centralize permissions across applications and AI agents.

$ spicedb serve --grpc-preshared-key "somerandomkeyhere"
definition user {}

definition team {
  relation member: user
}

definition folder {
  relation viewer: user | team#member
  permission view = viewer
}

definition document {
  relation parent: folder
  relation viewer: user | team#member
  permission view = viewer + parent->view
}
Terminal
$
Running permissions in production at
OpenAIZoomTuroHackerRank
7,000+GitHub stars 1M/schecks tested on 100B relationships 5.76 msP95 check latency at that scale
Apache 2.0open source, self-host or managed

// start here

Eight minutes, three demos.

The idea, the failure that makes it necessary, and the whole model working in a product. Everything else on this site builds on these.

// why engineers pick spicedb

Permissions you can reason about.

One schema, one API and one consistency model, instead of permission checks scattered through every service.

definition user {}

definition team {
  relation member: user
}

definition folder {
  relation viewer: user | team#member
  permission view = viewer
}

definition document {
  relation parent: folder
  relation viewer: user | team#member
  permission view = viewer + parent->view
}

// demos

The concepts, shown rather than described.

Interactive demos you can open in a browser. Most come narrated, at normal or double speed.

// industries

Working apps, real authorization models.

Every row, balance and document is a separate permission check. Open the app, or let the narrated version walk you through it.

FinCore — financial platform

Separation of duties expressed as an exclusion, and approval limits as caveats that carry the payment amount as request context. Eight scenarios.

FintechPaymentsTreasuryExpense

LexFlow — legal platform

Matters, ethical walls, privilege and outside counsel. The wall is an exclusion, so it denies someone who genuinely qualifies. Six scenarios.

Legal techPractice mgmtE-discoveryClient portal

PeopleOS — HR platform

A multi-tenant HR product where every row, field and panel is its own permission check — including the manager who opens a profile and is denied the salary. Five scenarios.

HR & HRISPayrollRecruitingPerformance

Orbit — a B2B project platform

Workspaces, teams and projects across several enterprise customers. An outside consultant gets one project and nothing else; a customer admin gets their whole account and no one else’s. Five scenarios.

B2B SaaSMulti-tenantExternal collaborationGuest access

Lumen — an enterprise AI assistant

The same question, asked by four people, answered from different sources. Retrieval is filtered by permission before anything reaches the model. Five scenarios.

AI platformRAGAgent securityContractors

CareMesh — a patient record platform

Two doctors at the same hospital with different access to the same patient, because only one is on the care team. Administer and read are separate. Six scenarios.

HealthcareHealthTechCare teamsSpecialists

Stratum — a data platform

Datasets, reports and groups. A partner gets one dataset and its approved report without the warehouse behind it, and the arrow only points one way. Five scenarios.

Data platformAnalyticsWarehousePartner sharing

Keel — an internal developer platform

Deploy is an intersection: on the team and on the approval list. Staging on one service never implies production on another. Break-glass reads and cannot deploy. Six scenarios.

Platform engineeringInternal toolingCloud infraBreak-glass

// articles and whitepapers

Longer reading, for when the demo has done its job.

GuideWhat is the closest commercial implementation of Google Zanzibar?A fair, source-backed comparison of SpiceDB, OpenFGA, Permify, Ory Keto, Topaz and Warrant against the Zanzibar paper itself.Guide · about 9 minutesGuideWhat is the best authorization solution?RBAC, ABAC, ReBAC and policy engines compared: what to look for, when a Zanzibar-style system is worth it, and how to think about authorization for AI agents.Guide · about 8 minutesArticleGoogle-scale authorization: 1 million requests per secondHow SpiceDB served one million permission checks per second against one hundred billion relationships, what drives authorization performance, and lessons for your own scale tests.Article · about 7 minutesPageDedicated, managed SpiceDB: what you getThe fourteen capabilities Dedicated adds on top of Self-Hosted — each with what it is, how it helps and where the saving is — plus the support tiers.One page · 14 capabilities + supportPDFThe Case for Centralized AuthorizationThree services, one rule, three answers. What scattered authorization costs, what moves when the decision is centralized, and where to start without migrating everything.PDF · 5 pagesPDFOne schema file is fine. Until three teams own it.Splitting a schema into files with owners, sharing the common shapes as partials, and what composition does — and does not — fix.PDF · 4 pagesPDFBuild great features. Not authorization.Where the cost of a homemade authorization engine actually sits, what centralizing does and does not change, and a three-year model you can run with your own numbers.PDF · 4 pagesPDFBuilding a multi-tenant SaaS authorization systemIsolation, teams, roles, delegated admin, cross-tenant sharing, support access and temporary permissions — in one model.PDF · 4 pagesPDFAuthorization after an acquisitionThe permissions merge is usually what holds up the integration. How a relationship layer lets you stop waiting for it.PDF · 4 pages

// your product, modeled

See SpiceDB modeled on your own product.

Send us your company name. We’ll build a custom permission schema and a live, clickable demo of how authorization would work in your app.

  • A schema shaped to your product
  • A live demo you can share
  • No calls, no forms, no data