head to head · open source
oauth2-proxy vs Logto
oauth2-proxy has 15,324 GitHub stars, 2,260 forks, 285 open issues and last shipped yesterday. Logto has 14,842 stars, 1,210 forks, 183 open issues and last shipped yesterday. oauth2-proxy leads on adoption by 3% (15,324 vs 14,842 stars). oauth2-proxy is written in Go under MIT; Logto is written in TypeScript under MPL-2.0. oauth2-proxy has attracted 15% as many forks as stars, Logto 8%. Logto was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (oauth2), so they are genuine substitutes rather than adjacent tools.
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 | Logto | |
|---|---|---|
| GitHub stars | ★ 15K | ★ 15K |
| License | MIT | MPL-2.0 |
| Written in | Go | TypeScript |
| Last push | 2026-11-04 | 2026-11-04 |
| Forks | ⑂ 2.3K | ⑂ 1.2K |
| 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 Logto if
- You want the Logto feature set and don't need the biggest community
- You prefer the MPL-2.0 license terms
- Your stack matches TypeScript
- You evaluated both and Logto 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 Logto
Logto Logto is the modern, open source auth infrastructure for SaaS and AI apps. It takes the pain out of OIDC and OAuth 2.1 and makes it easy to build secure, production ready auth with multi tenancy, enterprise SSO, and RBAC. website • cloud • docs • api • blog • auth wiki • newsletter Why Logto? Built for teams scaling SaaS, AI, and agent based platforms without the usual auth headaches. With Logto, you get: Multi tenancy, enterprise SSO, and RBAC : ready to use, no workarounds. Pre built sign in flows , customizable UIs, and SDKs for 30+ frameworks. Full support for OIDC, OAuth 2.1, and SAML without the…
read the full Logto 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 Logto more popular?
oauth2-proxy has 15,324 GitHub stars and Logto has 14,842. oauth2-proxy has the larger community by that measure.
Are oauth2-proxy and Logto free?
Both are open source. oauth2-proxy is licensed under MIT and Logto under MPL-2.0. Neither carries a licence fee.
What is the difference between oauth2-proxy and Logto?
oauth2-proxy is written in Go and Logto 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 Logto?
Choose oauth2-proxy if you want the larger community (15,324 stars) or its MIT licence terms. Choose Logto if its feature set, stack or MPL-2.0 licence fits better. Both are self-hostable.