SPICEDB + PING IDENTITY

SpiceDB: A Relationship-Based Access Control (ReBAC) Solution That Works With Ping Identity

Ping Identity decides who gets in and whether each request should be allowed in the moment. SpiceDB adds a permissions database that knows how every person, team and object in your product relate. Together they cover authorization from the login screen to the last row of data.

Ping customers have already invested in a strong identity foundation: single sign-on, multi-factor authentication, identity orchestration and, with Ping's Dynamic Authorization, centralized policy decisions for applications, APIs and AI agents. That foundation answers the most important questions about every session.

As products grow, another kind of question shows up inside the applications themselves. Who can see this document? Who can edit this project, approve this payment or open this patient record? The answer depends on a web of relationships that changes every day: who owns what, which team someone belongs to, what was shared with whom, and which folder or account an object sits in. That is the question SpiceDB was built to answer, and it fits naturally next to Ping.

What Ping Dynamic Authorization does well

Ping's Dynamic Authorization, delivered through PingOne Authorize and PingAuthorize, takes authorization logic out of application code and puts it in one central place. Its strengths are clear:

If your priority is stopping fraud after login, applying risk and consent in real time, or governing what an API call may do, Ping is a strong place to make that decision.

What SpiceDB adds: relationships as data

SpiceDB is an open-source permissions database inspired by Google's Zanzibar, the system Google described for authorizing products such as Drive, Calendar and YouTube. Instead of evaluating a policy against attributes passed in with each request, SpiceDB stores the relationships themselves, such as Alice is a member of Engineering, Engineering can view the Specs folder and the Roadmap lives in Specs, and computes permissions from them when you ask.

Two engines, two questions

The simplest way to see how the two fit is to look at the question each one answers best.

Ping Dynamic AuthorizationSpiceDB
The questionShould this request be allowed right now, given who is asking, the context and the risk?Can this person act on this object? And which objects can they reach?
Core modelCentralized policies evaluated against identity, entitlements and real-time signalsA graph of relationships stored in a database, with permissions computed from it
Shines atFraud prevention, consent, step-up decisions, API and transaction governance, delegated entitlementsSharing, ownership, hierarchies, multi-tenant products, permission-aware lists, search and AI retrieval
Where decisions are enforcedGateways, services and data layersInside your applications and data platforms, through check and lookup APIs
Who usually owns itIdentity and security teams, through a low-code policy interfaceApplication and platform engineers, through schema as code
ScaleLow latency through caching and localized decisionsBillions of relationships, with precomputed permissions for the largest lists

Not either-or. Ping is excellent at deciding whether a request should go ahead in context. SpiceDB is excellent at knowing exactly which objects a person is connected to. Most mature architectures need both answers.

How they work together

People andAI agents Ping Identity Sign-in, MFA, SSO Dynamic Authorization: context and risk, per request token Your applications web and mobile apps, APIs, microservices, AI features Your dataonly what'sallowed check, lookup yes or no, and why SpiceDB relationships between people, teams and objects users and groups kept in sync (e.g. SCIM)
Ping establishes identity and makes in-the-moment policy decisions; SpiceDB answers the object-level question inside each application.

Because both rely on open standards and APIs, there is no rip-and-replace. These are the patterns teams use most:

1. Ping signs people in, SpiceDB decides what they can reach

Ping authenticates the user and issues a standard OpenID Connect token. Your application reads the user's identifier from that token and uses it as the subject of every SpiceDB check. Authentication stays exactly where it is.

2. Ping stays the source of truth for users and groups

When Ping provisions or updates users and groups, for example over SCIM, those memberships are written to SpiceDB as relationships. SpiceDB then adds the product-specific relationships that never belong in a directory: ownership, shares, folders, projects and customer accounts.

3. Layered decisions: context at the edge, objects inside

Ping's Dynamic Authorization decides whether a request should go ahead given risk, consent and context, at the gateway or API. Inside the service, SpiceDB decides whether the person can act on the specific object. A request has to pass both, which is defense in depth without duplicating logic.

4. Relationships as an input to Ping policy

Where your Ping policies can consult external services at decision time, a SpiceDB check can become one of the inputs. A central policy can then express rules such as "allow when the person is related to this record and the risk score is low", combining the strengths of both.

5. AI agents with the right boundaries

Ping establishes an agent's identity and the delegated, time-bound scope it acts under. SpiceDB makes sure the agent can only reach the documents and records the person it works for can see, including filtering retrieval before anything reaches the model.

When to add SpiceDB to your Ping environment

Getting started

  1. Model one application. Describe its objects and access rules as a SpiceDB schema, and try it in the browser playground.
  2. Connect identities. Use the user identifier from your Ping-issued tokens as the SpiceDB subject, and sync groups as relationships.
  3. Add checks and lookups. Call SpiceDB wherever the application shows or changes data, starting with the screens that matter most.
  4. Choose how to run it. Self-host the open-source release, or let AuthZed run it as a managed service.

See SpiceDB alongside your Ping setup

Send us your company name and we’ll build a custom permission schema and a live, clickable demo of how relationship-based authorization would work in your application, designed to sit alongside the identity platform you already run.

Get a custom demo · Explore SpiceDB demos · Open the Playground

AuthZed and Ping Identity are independent companies. This article describes common ways customers use the two together, based on standards such as OpenID Connect and SCIM; it does not describe a joint product. Ping Identity, PingOne, PingAuthorize, PingOne Authorize and related names are trademarks of Ping Identity. Product details reflect Ping Identity's published materials as of November 2026.