head to head · open source
oauth2-proxy vs KeePassDX
oauth2-proxy has 15,319 GitHub stars, 2,259 forks, 285 open issues and last shipped yesterday. KeePassDX has 7,613 stars, 425 forks, 541 open issues and last shipped 4 days ago. oauth2-proxy leads on adoption by 101% (15,319 vs 7,613 stars). oauth2-proxy is written in Go under MIT; KeePassDX is written in Kotlin under GPL-3.0. oauth2-proxy has attracted 15% as many forks as stars, KeePassDX 6%. oauth2-proxy was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| oauth2-proxy | KeePassDX | |
|---|---|---|
| GitHub stars | ★ 15K | ★ 7.6K |
| License | MIT | GPL-3.0 |
| Written in | Go | Kotlin |
| Last push | 2026-11-04 | 2026-11-01 |
| Forks | ⑂ 2.3K | ⑂ 425 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick oauth2-proxy if
- You weight community size — 15K stars and counting
- You want the MIT license terms
- Your stack matches Go
- You value the larger contributor base for long-term maintenance
pick KeePassDX if
- You want the KeePassDX feature set and don't need the biggest community
- You prefer the GPL-3.0 license terms
- Your stack matches Kotlin
- You evaluated both and KeePassDX fits your workflow better
About oauth2-proxy
OAuth2 Proxy is a flexible, open source tool that can act as either a standalone reverse proxy or a middleware component integrated into existing reverse proxy or load balancer setups. It provides a simple and secure way to protect your web applications with OAuth2 / OIDC authentication. As a reverse proxy, it intercepts requests to your application and redirects users to an OAuth2 provider for authentication. As a middleware, it can be seamlessly integrated into your existing infrastructure to handle authentication for multiple applications. OAuth2 Proxy supports a lot of OAuth2 as well as OIDC providers…
read the full oauth2-proxy overview →
About KeePassDX
Android KeePassDX Lightweight password safe and manager for Android , KeePassDX allows editing encrypted data in a single file in KeePass format and fill in the forms in a secure way. Features Passkeys for authentication and local storage of private keys . Biometric recognition for fast unlocking (fingerprint / face unlock / …). One Time Password management (HOTP / TOTP) for two factor authentication (2FA). Autofill for easy form filling with passwords. Magikeyboard to efficiently fill in any field. Create encrypted database files . Organisation of credentials by entry and in group trees. Allows opening and…
read the full KeePassDX overview →
More in Security & Privacy
Related comparisons
More Identity & Access Management (IAM) projects
Compare either of these against the rest of the Identity & Access Management (IAM) field.
Frequently asked questions
Is oauth2-proxy or KeePassDX more popular?
oauth2-proxy has 15,319 GitHub stars and KeePassDX has 7,613. oauth2-proxy has the larger community by that measure.
Are oauth2-proxy and KeePassDX free?
Both are open source. oauth2-proxy is licensed under MIT and KeePassDX under GPL-3.0. Neither carries a licence fee.
What is the difference between oauth2-proxy and KeePassDX?
oauth2-proxy is written in Go and KeePassDX in Kotlin. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, oauth2-proxy or KeePassDX?
Choose oauth2-proxy if you want the larger community (15,319 stars) or its MIT licence terms. Choose KeePassDX if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.