head to head · open source
oauth2-proxy vs Hexclave
oauth2-proxy has 14,982 GitHub stars, 2,196 forks, 285 open issues and last shipped 2 days ago. Hexclave has 6,863 stars, 522 forks, 65 open issues and last shipped yesterday. oauth2-proxy leads on adoption by 118% (14,982 vs 6,863 stars). oauth2-proxy is written in Go under MIT; Hexclave is written in TypeScript under a custom or non-standard licence. oauth2-proxy has attracted 15% as many forks as stars, Hexclave 8%. Hexclave 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 | Hexclave | |
|---|---|---|
| GitHub stars | ★ 15K | ★ 6.9K |
| License | MIT | Custom / other |
| Written in | Go | TypeScript |
| Last push | 2026-09-18 | 2026-09-19 |
| Forks | ⑂ 2.2K | ⑂ 522 |
| 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 Hexclave if
- You want the Hexclave feature set and don't need the biggest community
- You prefer the Custom / other license terms
- Your stack matches TypeScript
- You evaluated both and Hexclave fits your workflow better
About oauth2-proxy
OAuth2 Proxy is an open source, MIT licensed reverse proxy and middleware written in Go that puts OAuth2 and OpenID Connect authentication in front of web applications, aimed at operators and platform teams who need single sign on without adding auth code to every app.
read the full oauth2-proxy overview →
About Hexclave
Hexclave is an open source user infrastructure platform written in TypeScript and distributed under a license the repository metadata lists as NOASSERTION, while the README badge states MIT / AGPLv3. It describes itself as handling everything around a product's users: authentication, teams, payments, emails, analytics, and more. The project lives in the JavaScript and TypeScript ecosystem, shipping SDKs for Next.js, React, and plain JavaScript, and it is positioned against hosted identity and user management services such as Auth0 and Clerk, both of which appear in its topic list.
read the full Hexclave 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 Hexclave more popular?
oauth2-proxy has 14,982 GitHub stars and Hexclave has 6,863. oauth2-proxy has the larger community by that measure.
Are oauth2-proxy and Hexclave free?
Both are open source. oauth2-proxy is licensed under MIT, and Hexclave has no licence declared in this registry. Both are free to self-host.
What is the difference between oauth2-proxy and Hexclave?
oauth2-proxy is written in Go and Hexclave in TypeScript. 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 Hexclave?
Choose oauth2-proxy if you want the larger community (14,982 stars) or its MIT licence terms. Choose Hexclave if its feature set, stack or Custom / other licence fits better. Both are self-hostable.