head to head · open source

oauth2-proxy vs tinyauth

oauth2-proxy has 15,325 GitHub stars, 2,261 forks, 285 open issues and last shipped 2 days ago. tinyauth has 8,471 stars, 289 forks, 41 open issues and last shipped yesterday. oauth2-proxy leads on adoption by 81% (15,325 vs 8,471 stars). oauth2-proxy is written in Go under MIT; tinyauth is written in Go under AGPL-3.0. oauth2-proxy has attracted 15% as many forks as stars, tinyauth 3%. tinyauth was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (oidc, sso), 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.

oauth2-proxy ★ 15K tinyauth ★ 8.5K category Security & Privacy

← all 20902 open source comparisons

Side by side

oauth2-proxy tinyauth
GitHub stars ★ 15K ★ 8.5K
License MIT AGPL-3.0
Written in Go Go
Last push 2026-11-04 2026-11-05
Forks ⑂ 2.3K ⑂ 289
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

full oauth2-proxy profile →

pick tinyauth if

  • You want the tinyauth feature set and don't need the biggest community
  • You prefer the AGPL-3.0 license terms
  • Your stack matches Go
  • You evaluated both and tinyauth fits your workflow better

full tinyauth profile →

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 tinyauth

Tinyauth The tiniest OpenID Certified™ authorization and authentication server you have ever seen. Tinyauth is the simplest and tiniest authentication and authorization server you have ever seen. It is designed to both work as an authentication middleware for your apps, offering support for OAuth, LDAP and access controls, and as a standalone authentication server. It supports all the popular proxies like Traefik, Nginx and Caddy. [!WARNING] Tinyauth is in active development and configuration may change often. Please make sure to carefully read the release notes before updating. [!NOTE] This is the main…

read the full tinyauth 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 tinyauth more popular?

oauth2-proxy has 15,325 GitHub stars and tinyauth has 8,471. oauth2-proxy has the larger community by that measure.

Are oauth2-proxy and tinyauth free?

Both are open source. oauth2-proxy is licensed under MIT and tinyauth under AGPL-3.0. Neither carries a licence fee.

What is the difference between oauth2-proxy and tinyauth?

oauth2-proxy is written in Go and tinyauth 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 tinyauth?

Choose oauth2-proxy if you want the larger community (15,325 stars) or its MIT licence terms. Choose tinyauth if its feature set, stack or AGPL-3.0 licence fits better. Both are self-hostable.