#Spice DB vs Permify

1 messages · Page 1 of 1 (latest)

foggy escarp
#

There are a few differences such as multi-store/tenant approach.

With us you can create isolated tenants and schemas for different applications while using a single Permify. We assign tenant ID for each of those applications tuples.

This is very helpful incases where you have interpolated multiple applications in your stack for instance;

  • Having multiple internal custom applications which you’re going to build authz for.
  • Or having a modular application with multiple different systems, an example might be SalesForce.

Also we have an advanced version of this system on-prem or managed which basically a pre-built control plane that allows you to create shadow schemas.

An easier way to explain this is basically having an import feature which each schema of different applications can talk to each other so you can separate schemas for each team/application/module while maintaining the interpolation.

Here’s a differentiation docs we prepared: https://permify.notion.site/Differentiation-9a7b31e5e029454ca3148a9f89ed9a2a?pvs=4

Permify on Notion
Differentiation | Notion

Core differences between Zanzibar based solutions (Keto, OpenFGA, SpiceDB)

silent temple
#

Ah this is great! More detailed than the one currently on the site, thanks!

foggy escarp
#

Absolutely let me know if you need any assistance

silent temple
#

May want to update the OpenFGA comparison as they released ABAC support in 1.4 I believe. Still early days but it seems very similar to SpiceDB implementation.