head to head · open source
frp vs tsdproxy
frp has 110,686 GitHub stars, 15,330 forks, 48 open issues and last shipped 11 days ago. tsdproxy has 1,735 stars, 84 forks, 29 open issues and last shipped 8 days ago. frp leads on adoption by 6,280% (110,686 vs 1,735 stars). frp is written in Go under Apache-2.0; tsdproxy is written in Go under MIT. frp has attracted 14% as many forks as stars, tsdproxy 5%. tsdproxy was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 3 topic tags (go, proxy, reverse-proxy), 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
| frp | tsdproxy | |
|---|---|---|
| GitHub stars | ★ 111K | ★ 1.7K |
| License | Apache-2.0 | MIT |
| Written in | Go | Go |
| Last push | 2026-11-10 | 2026-11-13 |
| Forks | ⑂ 15K | ⑂ 84 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick frp if
- You weight community size — 111K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Go
- You value the larger contributor base for long-term maintenance
pick tsdproxy if
- You want the tsdproxy feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Go
- You evaluated both and tsdproxy fits your workflow better
About frp
frp README 中文文档 Sponsors frp is an open source project with its ongoing development made possible entirely by the support of our awesome sponsors. If you'd like to join them, please consider sponsoring frp's development. Gold Sponsors High performance residential and ISP proxies for developers 90M+ residential IPs worldwide. Rotating IPs, sticky sessions, and traffic that never expires. From $0.55/GB. Use RAPID10 for 10% off. Try it for free. The complete IDE crafted for professional Go developers The sovereign cloud that puts you in control An open source, self hosted alternative to public clouds, built for…
About tsdproxy
TSDProxy Tailscale Docker Proxy The easiest way to expose Docker containers on your Tailscale network. One label. Zero sidecars. Quick Start Get running in under a minute. One compose file, one label. Step 1: Create docker compose.yml Step 2: Start it up TSDProxy creates a default config at /config/tsdproxy.yaml on first run. Open the dashboard at click the proxy card, and authenticate with Tailscale. Your container is now available at .ts.net with automatic HTTPS. For automated (headless) setup, configure an AuthKey or OAuth before adding services. Key Features How It Works Under the hood: 1. Container Scanning…
read the full tsdproxy overview →
More in Infrastructure & Operations
Related comparisons
More Networking & Connectivity projects
Compare either of these against the rest of the Networking & Connectivity field.
Frequently asked questions
Is frp or tsdproxy more popular?
frp has 110,686 GitHub stars and tsdproxy has 1,735. frp has the larger community by that measure.
Are frp and tsdproxy free?
Both are open source. frp is licensed under Apache-2.0 and tsdproxy under MIT. Neither carries a licence fee.
What is the difference between frp and tsdproxy?
frp is written in Go and tsdproxy 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, frp or tsdproxy?
Choose frp if you want the larger community (110,686 stars) or its Apache-2.0 licence terms. Choose tsdproxy if its feature set, stack or MIT licence fits better. Both are self-hostable.