head to head · open source
openGym vs oauth2-proxy
openGym has 15,277 GitHub stars, 2,008 forks, 109 open issues and last shipped yesterday. oauth2-proxy has 15,253 stars, 2,243 forks, 285 open issues and last shipped 2 days ago. openGym leads on adoption by 0% (15,277 vs 15,253 stars). openGym is written in JavaScript under AGPL-3.0; oauth2-proxy is written in Go under MIT. openGym has attracted 13% as many forks as stars, oauth2-proxy 15%. openGym 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
| openGym | oauth2-proxy | |
|---|---|---|
| GitHub stars | ★ 15K | ★ 15K |
| License | AGPL-3.0 | MIT |
| Written in | JavaScript | Go |
| Last push | 2026-10-24 | 2026-10-23 |
| Forks | ⑂ 2.0K | ⑂ 2.2K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick openGym if
- You weight community size — 15K stars and counting
- You want the AGPL-3.0 license terms
- Your stack matches JavaScript
- You value the larger contributor base for long-term maintenance
pick oauth2-proxy if
- You want the oauth2-proxy feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Go
- You evaluated both and oauth2-proxy fits your workflow better
About openGym
A self hosted gym & body weight tracker you actually own. Plan your week, run guided workouts, track every set and your body weight over time — on your phone, synced across devices, behind your own passkey login. No account on someone else's server, no subscription, no ads. Just docker compose up . Home — today's workout & weight Guided workout — animated demos & sets Stats — heatmap, charts & PRs 🌐 opengym.duarte santos.ch · 📦 Source on GitHub · 🦊 GitLab mirror Screenshots, docs and the APK download live on the site. Want to poke at it first? The in browser demo is the real app with example data — no…
read the full openGym overview →
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 →
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 openGym or oauth2-proxy more popular?
openGym has 15,277 GitHub stars and oauth2-proxy has 15,253. openGym has the larger community by that measure.
Are openGym and oauth2-proxy free?
Both are open source. openGym is licensed under AGPL-3.0 and oauth2-proxy under MIT. Neither carries a licence fee.
What is the difference between openGym and oauth2-proxy?
openGym is written in JavaScript and oauth2-proxy 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, openGym or oauth2-proxy?
Choose openGym if you want the larger community (15,277 stars) or its AGPL-3.0 licence terms. Choose oauth2-proxy if its feature set, stack or MIT licence fits better. Both are self-hostable.