head to head · open source
oauth2-proxy vs Hexclave
oauth2-proxy has 15,325 GitHub stars, 2,261 forks, 285 open issues and last shipped yesterday. Hexclave has 6,887 stars, 528 forks, 65 open issues and last shipped yesterday. oauth2-proxy leads on adoption by 123% (15,325 vs 6,887 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%. 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 | Hexclave | |
|---|---|---|
| GitHub stars | ★ 15K | ★ 6.9K |
| License | MIT | Custom / other |
| Written in | Go | TypeScript |
| Last push | 2026-11-04 | 2026-11-04 |
| Forks | ⑂ 2.3K | ⑂ 528 |
| 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 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 Hexclave
Hexclave The user infrastructure platform. Hexclave handles everything around your users: authentication, teams, payments, emails, analytics, and much more. Get started with our AI prompt below. Website · Docs · Dashboard · Discord Get started Setting up Hexclave is one prompt. Paste this into your coding agent of choice: For AI agents If you're an AI coding agent, use your web fetch tool or curl the skill documentation for up to date integration instructions: What's included Hexclave ships as a catalog of apps you switch on as your product needs them. Each one is built on the same user model, and new apps land…
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 15,325 GitHub stars and Hexclave has 6,887. 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 (15,325 stars) or its MIT licence terms. Choose Hexclave if its feature set, stack or Custom / other licence fits better. Both are self-hostable.