SpiceDB is the most scalable and consistent Google Zanzibar-inspired database for storing and computing permissions data—use it to build global-scale fine grained authorization services.
Expressive gRPC and HTTP/JSON APIs for powering authorization logic in your client applications.
Distributed, parallel graph engine faithful to the architecture described in Google’s Zanzibar paper.
A flexible consistency model configurable per-request that includes resistance to the New Enemy Problem.
Intuitive authorization configuration language — SpiceDB Schema — with CI/CD integrations for validation & testing.
Support for in-memory, Spanner, CockroachDB, PostgreSQL, and MySQL relationship storage.
Deep observability with Prometheus metrics, pprof profiles, structured logging, and OpenTelemetry tracing.
Add DispatchExecutor, a query plan executor that is Dispatch-aware and sends subproblems on Alias boundaries (https://github.com/authzed/spicedb/pull/3074)
Implement Dispatch caching for query plan execution (https://github.com/authzed/spicedb/pull/3079)
Add new optimizer to query planner based on set theory laws for simplifications (https://github.com/authzed/spicedb/pull/3051)
Experimental: Add unified schema storage with ReadStoredSchema/WriteStoredSchema APIs for improved schema read performance (https://github.com/authzed/spicedb/pull/2924)
This feature stores the entire schema as a single serialized proto rather than reading individual namespace and caveat definitions separately, significantly improving schema read performance.
Migration to unified schema storage is controlled by the --experimental-schema-mode flag, which supports a 4-phase rolling migration:
read-legacy-write-legacy (default) - No change; reads and writes use legacy per-definition storage.read-legacy-write-both - Reads from legacy storage, writes to both legacy and unified storage. This is the first migration step and backfills the unified schema table.read-new-write-both - Reads from unified storage, writes to both. Validates the new read path while maintaining backward compatibility.read-new-write-new - Reads and writes only unified storage. This is the final migration target.Deployment:
--experimental-schema-mode flag and performing a rolling restart at each stage. You can also take the system down briefly and move directly from stage 1 to stage 4, which runs the full migration in one step.Full Changelog: https://github.com/authzed/spicedb/compare/v1.52.0...v1.53.0
This release is available at authzed/spicedb:v1.53.0, quay.io/authzed/spicedb:v1.53.0, ghcr.io/authzed/spicedb:v1.53.0
kubectl create spicedbclusterDesign tailored authorization systems by defining relationships, permissions based on those relationships, and bits of policy called Caveats.