Dexvsqauth
Two self-hosted Keycloak alternatives, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Dex | qauth | |
|---|---|---|
| Score | 73/100 | 35/100 |
| Rank in category | #4 of 19 in Identity & Auth | #37 of 40 in Authentication |
| GitHub stars | 11 269 | 28 |
| Stars, last 30 days | +72 | +2 |
| Stable releases, 12 months | 4 | 14 |
| Latest release | v2.46.1 · 21 Oct 2026 | v0.2.9 · 16 Nov 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | No |
| License | Apache-2.0 | Apache-2.0 |
| Main language | Go | Typescript |
Which one should you pick?
Dex scores 73/100 against 35/100 for qauth, so it is the safer default.
qauth ships more often: 14 stable releases in the past year, against 4 for Dex.
If you want the quickest setup, Dex is easier to run; qauth needs more configuration.
Dex is growing faster right now (+72 stars in 30 days).
Key differences
- Language: Dex is written mainly in Go, qauth in Typescript.
- Only Dex ships an official Docker image.
- Features only Dex lists: Built-in login UI, Federated identity connectors, Group membership claims, gRPC management API and 9 more.
- Features only qauth lists: Agent-Native Authorization (RFC 8693), Crypto-Agile Architecture, Developer Portal, Dynamic Client Registration (RFC 7591) and 11 more.
Dex details →qauth details → All Keycloak alternatives →