OpenFGA

OpenFGA is a self-hostable, high-performance authorization engine that helps developers model and enforce fine-grained access control in applications.

  • Security
  • Tools & Utilities
OpenFGA is a self-hostable, high-performance authorization engine that helps developers model and enforce fine-grained access control in applications.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

79/100 Good

Maintained
100last commit 14 days ago
Popular
766,110 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
95no serious findings, 1 minor, CI, tests, OpenSSF Scorecard 9.6/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
6,110
Open issues
246
Last commit
2026-11-07
Latest release
v1.22.1
License
Apache-2.0
Activity
steady

Checked 14 days ago - source: GitHub (openfga/openfga)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Start OpenFGA in Docker and expose ports Run the provided Docker image with ports 8080 and 3000 mapped so your app can reach OpenFGA’s HTTP and gRPC endpoints. Without the port mappings, your programs on the host cannot talk to it. source
  • Create a store before using OpenFGA OpenFGA needs a named store to hold authorization models and relationship data. Use the example POST command to create one, otherwise your app has no place to save or check permissions. source
  • Use Postgres if you need persistent data The simple Docker run example uses in-memory data, so everything is lost when the container stops. Use the provided Docker Compose file with Postgres if you want your stores and settings to survive restarts. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which datastores can OpenFGA use when self-hosting?

OpenFGA supports a pluggable datastore that currently supports PostgreSQL and an in-memory datastore.

What should be configured before running OpenFGA in production?

Configure authentication and enable HTTP TLS, gRPC TLS, or both. Set the log format to json and the log level to info, and disable the Playground.

Does OpenFGA configuration assume the binary is available in PATH?

The configuration docs assume OpenFGA is installed and the openfga binary is in PATH. If you built the binary elsewhere, you can refer to it directly.

Answers sourced from openfga.dev, openfga.dev, www.reddit.com

Community

Collected 48 days ago - public community threads