head to head · open source
oauth2-proxy vs gokey
oauth2-proxy has 15,327 GitHub stars, 2,261 forks, 285 open issues and last shipped yesterday. gokey has 2,440 stars, 110 forks, 8 open issues and last shipped 4 months ago. oauth2-proxy leads on adoption by 528% (15,327 vs 2,440 stars). oauth2-proxy is written in Go under MIT; gokey is written in Go under BSD-3-Clause. oauth2-proxy has attracted 15% as many forks as stars, gokey 5%. 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 | gokey | |
|---|---|---|
| GitHub stars | ★ 15K | ★ 2.4K |
| License | MIT | BSD-3-Clause |
| Written in | Go | Go |
| Last push | 2026-11-05 | 2026-07-10 |
| Forks | ⑂ 2.3K | ⑂ 110 |
| 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 gokey if
- You want the gokey feature set and don't need the biggest community
- You prefer the BSD-3-Clause license terms
- Your stack matches Go
- You evaluated both and gokey 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 gokey
gokey A simple vaultless password manager in Go gokey is a password manager, which does not require a password vault. Instead of storing your passwords in a vault it derives your password on the fly from your master password and supplied realm string (for example, resource URL). This way you do not have to manage, backup or sync your password vault (or trust its management to a third party) as your passwords are available immediately anywhere. example options o by default gokey outputs generated data to stdout P path to master password file which will be used to generate other passwords/keys or to encrypt seed…
read the full gokey 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 gokey more popular?
oauth2-proxy has 15,327 GitHub stars and gokey has 2,440. oauth2-proxy has the larger community by that measure.
Are oauth2-proxy and gokey free?
Both are open source. oauth2-proxy is licensed under MIT and gokey under BSD-3-Clause. Neither carries a licence fee.
What is the difference between oauth2-proxy and gokey?
oauth2-proxy is written in Go and gokey in Go. 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 gokey?
Choose oauth2-proxy if you want the larger community (15,327 stars) or its MIT licence terms. Choose gokey if its feature set, stack or BSD-3-Clause licence fits better. Both are self-hostable.