head to head · open source

caddy vs landscape

caddy has 76,129 GitHub stars, 5,010 forks, 286 open issues and last shipped 2 days ago. landscape has 1,558 stars, 121 forks, 29 open issues and last shipped today. caddy leads on adoption by 4,786% (76,129 vs 1,558 stars). caddy is written in Go under Apache-2.0; landscape is written in Rust under GPL-3.0. caddy has attracted 7% as many forks as stars, landscape 8%. landscape was the more recently maintained of the two, and both are self-hostable with no licence fee.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

caddy ★ 76K landscape ★ 1.6K category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

caddy landscape
GitHub stars ★ 76K ★ 1.6K
License Apache-2.0 GPL-3.0
Written in Go Rust
Last push 2026-09-26 2026-09-28
Forks ⑂ 5.0K ⑂ 121
Self-hosting Yes Yes
Data ownership Your server Your server

pick caddy if

  • You weight community size — 76K 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

full caddy profile →

pick landscape if

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

full landscape profile →

About caddy

Caddy is a Go based, Apache 2.0 licensed HTTP/1.1, HTTP/2, and HTTP/3 web server and reverse proxy that obtains and renews TLS certificates automatically by default, built for operators and teams who want every site on HTTPS without maintaining a separate certificate workflow.

read the full caddy overview →

About landscape

Landscape is an open source router platform that configures a standard Linux distribution as a router by steering traffic by domain rather than IP alone, built in Rust with eBPF and aimed at self hosters who want policy routing on hardware and distributions they already control.

read the full landscape overview →

More in Infrastructure & Operations

kubernetes ★ 128K Immich ★ 115K frp ★ 110K Uptime Kuma ★ 92K worldmonitor ★ 87K mall ★ 85K

Related comparisons

frp vs caddy caddy vs traefik frp vs traefik frp vs adguardhome frp vs nginx frp vs algo frp vs nginx-proxy immich vs openvpn n8n vs huginn uptime-kuma vs worldmonitor uptime-kuma vs netdata uptime-kuma vs grafana worldmonitor vs netdata worldmonitor vs grafana uptime-kuma vs prometheus netdata vs grafana n8n vs kestra langchain vs haystack kubernetes vs rancher ansible vs compose ansible vs conductor ansible vs xxl-job ansible vs gitleaks ansible vs kestra

More Networking & Connectivity projects

Compare either of these against the rest of the Networking & Connectivity field.

caddy vs frp caddy vs traefik caddy vs AdGuardHome caddy vs nginx caddy vs algo caddy vs nginx-proxy caddy vs goproxy caddy vs openvpn-install caddy vs cloudflared caddy vs amnezia-client caddy vs OpenVPN caddy vs coredns

Frequently asked questions

Is caddy or landscape more popular?

caddy has 76,129 GitHub stars and landscape has 1,558. caddy has the larger community by that measure.

Are caddy and landscape free?

Both are open source. caddy is licensed under Apache-2.0 and landscape under GPL-3.0. Neither carries a licence fee.

What is the difference between caddy and landscape?

caddy is written in Go and landscape in Rust. 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 landscape?

Choose caddy if you want the larger community (76,129 stars) or its Apache-2.0 licence terms. Choose landscape if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.