Top 3 Go entitlement Projects

entitlements

• Add a project

1. spicedb

   1 42 5,572 9.8 Go

   Open Source, Google Zanzibar-inspired database for scalably storing and querying fine-grained authorization data

   

   Project mention: Beware of the New Enemy Problem ⚠️ | dev.to | 2025-03-06

   Here's an example of how it works in SpiceDB - a database inspired by Google Zanzibar. A zookie is passed when making a permissions check request, and guarantees that the policy and individual relationships used to compute the answer will be at least as fresh as the Zookie presented requires.

2. InfluxDB

   influxdata.com featured

   InfluxDB high-performance time series database. Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems.

   

3. openfga

   2 18 3,500 9.7 Go

   A high performance and flexible authorization/permission engine built for developers and inspired by Google Zanzibar

   

   Project mention: Who Needs Roles Anymore? Introducing OpenFGA, the Future of SaaS | dev.to | 2025-01-14

   It’s 2025 y’all, time to retire that ancient, one-size-fits-all approach. OpenFGA gives you the flexibility to handle complex user relationships with elegance. Whether you’re cooking up the next Slack, managing external contractors, or just tired of editing roles for your friends named Bob, ReBAC can save you from permissions purgatory.

4. warrant

   3 41 1,261 5.9 Go

   Warrant is a highly scalable, centralized authorization service based on Google Zanzibar. Use it to define, enforce, query, and audit application authorization and access control.

   

   Project mention: Show HN: Permify 1.0 – Open-source fine-grained authorization service | news.ycombinator.com | 2024-08-21

   I think one major difference between the Zanzibar implementations that are out there is support for the 'zookie' consistency token (as mentioned in the original paper). OpenFGA afaik doesn't implement zookies yet[1]. With zookies, each permission write generates a unique token that represents that particular write. Clients can store that token (per resource) and optionally provide it during runtime checks to ensure checks are consistent up to that write. It also helps the system guard against the 'new-enemy problem' (incorrect permissions checks due to permissions changes being read out of order) by ordering writes.

   I'd argue that it also unlocks a variety of caching implementations on the Zanzibar server while still allowing clients to specify desired consistency on a per-request/per-resource level. In other words, a Zanzibar implementation with support for zookies can guarantee consistency at a much higher throughput than one that relies on time (second, millisecond delay). This is important for generic 'read after write' scenarios.

   Disclaimer: I'm a former founder of Warrant[2] which was recently acquired by WorkOS. Our team has spent a ton of time building our Zanzibar-based authorization service (WorkOS FGA[3]) which supports zookies[4] and other Zanzibar concepts.

   [1] https://openfga.dev/docs/interacting/consistency#future-work

   [2] https://warrant.dev/

   [3] https://workos.com/docs/fga

   [4] https://workos.com/docs/fga/warrant-tokens

Go entitlements related posts

• We built an open source authorization service based on Google Zanzibar

  7 projects | /r/golang | 3 Nov 2022

Index

Sponsored

InfluxDB high-performance time series database

Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems.

influxdata.com

Do not miss the trending Go projects with our weekly report!