authorizerdev/authorizer
Your data, your control. Fully open source, authentication and authorization. No lock-ins. Deployment in Railway in 120 seconds || Spin a docker image as a micro-service in your infra. Built in login page and Admin panel out of the box. observed · 2026-08-28
Health v2 · maintenance only
98/100
- Activity 98
- Release rhythm 98
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: 9.5
- age_days: 1918
- days_rel: 14
- days_push: 14
- n_releases_24m: 7
Adoption not part of the score
1984 stars · 210 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
Authorizer is an open-source, self-hosted authentication and authorization server written in Go, providing OAuth2/OIDC, SAML SSO, MFA, social logins, magic links, passkeys, and fine-grained ReBAC authorization via an embedded OpenFGA engine. It supports 13+ database backends so user data stays in your own database, and ships with a built-in login page, admin dashboard, and an MCP server for permission-aware AI agents.
Use cases
- self-host user authentication instead of Auth0 or Clerk
- add OAuth2 and OIDC login to my app
- implement role-based access control with my own database
- add social logins and magic link passwordless sign-in
- set up enterprise SSO with SAML and SCIM provisioning
- check user permissions from an AI agent before RAG retrieval
- add multi-factor authentication with TOTP and passkeys
When to choose
- you want full control over user data and identity infrastructure in your own cloud or VPC
- you need OAuth2/OIDC, SAML, MFA, and fine-grained authorization from a single self-hosted service
- you want to keep user records in an existing database like Postgres, MySQL, or MongoDB
- you need permission-aware AI agents via a built-in MCP server
When to avoid
- you prefer a fully managed hosted identity provider with no operational burden
- you need only a lightweight embedded auth library inside a single app rather than a standalone server
- you cannot operate a stateful service with database, secrets, and key rotation responsibilities
Facets
service · maturity active
auth authorization api-framework graphql mcp security self-hosted security backend web-development developer-tools apis self-hosted go cloud oauth2 oidc saml sso rbac fga openfga multi-tenancy scim passkey mfa social-login magic-link identity-provider jwt docker kubernetes linux web-server
6 sources
- readme: https://github.com/authorizerdev/authorizer · fetched 2026-08-28 · fcd16d2187ab
- homepage: https://authorizer.dev · fetched 2026-08-29 · 7a432a4d8d8a
- site_page: https://docs.authorizer.dev · fetched 2026-08-29 · 99560788c9c7
- site_page: https://docs.authorizer.dev/getting-started · fetched 2026-08-29 · c0cc2dc3beba
- site_page: https://docs.authorizer.dev/core/mcp · fetched 2026-08-29 · 5bdb1d68a408
- site_page: https://docs.authorizer.dev/core/databases · fetched 2026-08-29 · 79099dd13be0
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| authorizerdev/authorizer | main | 98 |
For agents
markdown · JSON · MCP: product_card(name="authorizerdev/authorizer")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem