head to head · open source
caddy vs tsdproxy
caddy has 79,324 GitHub stars, 5,296 forks, 286 open issues and last shipped 2 days ago. tsdproxy has 1,735 stars, 84 forks, 29 open issues and last shipped 8 days ago. caddy leads on adoption by 4,472% (79,324 vs 1,735 stars). caddy is written in Go under Apache-2.0; tsdproxy is written in Go under MIT. caddy has attracted 7% as many forks as stars, tsdproxy 5%. caddy was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 3 topic tags (go, https, 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
| caddy | tsdproxy | |
|---|---|---|
| GitHub stars | ★ 79K | ★ 1.7K |
| License | Apache-2.0 | MIT |
| Written in | Go | Go |
| Last push | 2026-11-19 | 2026-11-13 |
| Forks | ⑂ 5.3K | ⑂ 84 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick caddy if
- You weight community size — 79K 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 caddy
a project Every site on HTTPS Caddy is an extensible server platform that uses TLS by default. Releases · Documentation · Get Help Powered by Special thanks to: Warp, built for coding with multiple AI agents Available for MacOS, Linux, & Windows Menu Features Install Build from source For development With version information and/or plugins Quick start Overview Full documentation Getting help About Features Easy configuration with the Caddyfile Powerful configuration with its native JSON config Dynamic configuration with the JSON API Config adapters if you don't like JSON Automatic HTTPS by default ZeroSSL and…
read the full caddy overview →
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 caddy or tsdproxy more popular?
caddy has 79,324 GitHub stars and tsdproxy has 1,735. caddy has the larger community by that measure.
Are caddy and tsdproxy free?
Both are open source. caddy is licensed under Apache-2.0 and tsdproxy under MIT. Neither carries a licence fee.
What is the difference between caddy and tsdproxy?
caddy 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, caddy or tsdproxy?
Choose caddy if you want the larger community (79,324 stars) or its Apache-2.0 licence terms. Choose tsdproxy if its feature set, stack or MIT licence fits better. Both are self-hostable.