head to head · open source

oauth2-proxy vs FileRise

oauth2-proxy has 15,390 GitHub stars, 2,272 forks, 285 open issues and last shipped 2 days ago. FileRise has 1,029 stars, 55 forks, 7 open issues and last shipped 3 days ago. oauth2-proxy leads on adoption by 1,396% (15,390 vs 1,029 stars). oauth2-proxy is written in Go under MIT; FileRise is written in JavaScript under MIT. oauth2-proxy has attracted 15% as many forks as stars, FileRise 5%. oauth2-proxy was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (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 FileRise ★ 1.0K category Security & Privacy

← all 20902 open source comparisons

Side by side

oauth2-proxy FileRise
GitHub stars ★ 15K ★ 1.0K
License MIT MIT
Written in Go JavaScript
Last push 2026-11-18 2026-11-17
Forks ⑂ 2.3K ⑂ 55
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 FileRise if

  • You want the FileRise feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches JavaScript
  • You evaluated both and FileRise fits your workflow better

full FileRise 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 FileRise

FileRise FileRise is a self hosted web file manager and storage hub with WebDAV, sharing, and per folder ACLs. Drag & drop uploads, OnlyOffice integration, and optional folder level encryption at rest — all in one PHP app you control. Quick links: Website • Docs • Live demo • Install • FileRise Pro Built for: anyone who wants a fast, self hosted file manager, storage hub, client portal, and AI workflow workspace on their own infrastructure. Core (MIT): full open source FileRise feature set (ACLs, folder and file sharing, uploads, tags/search, PDF previews, and more), plus multiple local roots and WebDAV sources…

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

oauth2-proxy has 15,390 GitHub stars and FileRise has 1,029. oauth2-proxy has the larger community by that measure.

Are oauth2-proxy and FileRise free?

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

What is the difference between oauth2-proxy and FileRise?

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

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