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.
--enable-memory-protection-middleware=false to disable) by @miparnisari in https://github.com/authzed/spicedb/pull/2691.
⚠️ Now, if your server's memory usage is too high, incoming requests may be rejected with code "ResourceExhausted" (HTTP 429).Full Changelog: https://github.com/authzed/spicedb/compare/v1.47.1...v1.48.0
This release is available at authzed/spicedb:v1.48.0, quay.io/authzed/spicedb:v1.48.0, ghcr.io/authzed/spicedb:v1.48.0
kubectl create spicedbclusterDesign tailored authorization systems by defining relationships, permissions based on those relationships, and bits of policy called Caveats.