head to head · open source
nginx vs landscape
nginx has 32,114 GitHub stars, 8,395 forks, 468 open issues and last shipped 4 days ago. landscape has 1,598 stars, 125 forks, 29 open issues and last shipped yesterday. nginx leads on adoption by 1,910% (32,114 vs 1,598 stars). nginx is written in C under BSD-2-Clause; landscape is written in Rust under GPL-3.0. nginx has attracted 26% 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.
← all 20902 open source comparisons
Side by side
| nginx | landscape | |
|---|---|---|
| GitHub stars | ★ 32K | ★ 1.6K |
| License | BSD-2-Clause | GPL-3.0 |
| Written in | C | Rust |
| Last push | 2026-11-09 | 2026-11-12 |
| Forks | ⑂ 8.4K | ⑂ 125 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick nginx if
- You weight community size — 32K stars and counting
- You want the BSD-2-Clause license terms
- Your stack matches C
- You value the larger contributor base for long-term maintenance
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
About nginx
NGINX (pronounced "engine x" or "en jin eks") is the world's most popular Web Server, high performance Load Balancer, Reverse Proxy, API Gateway and Content Cache. NGINX is free and open source software, distributed under the terms of a simplified 2 clause BSD like license. Enterprise distributions, commercial support and training are available from F5, Inc. [!IMPORTANT] The goal of this README is to provide a basic, structured introduction to NGINX for novice users. Please refer to the full NGINX documentation for detailed information on installing, building, configuring, debugging, and more. These…
read the full nginx overview →
About landscape
Landscape routes traffic by domain—not just IP. Each flow gets its own DNS server. DNS answers populate kernel eBPF maps. Packets are steered at XDP/TC. No userspace datapath. No iptables. Built with Rust / eBPF. 简体中文 English Documentation Screenshot Architecture Landscape separates traffic steering into two planes: DNS plane (userspace). A flow is a policy group that devices join by IP or MAC. Each flow gets its own isolated Hickory DNS server with independent cache, upstream (UDP/DoH/DoT/DoQ), and rules. DNS answers populate per flow eBPF maps in the kernel. Data plane (kernel). XDP and TC hooks read these…
read the full landscape 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 nginx or landscape more popular?
nginx has 32,114 GitHub stars and landscape has 1,598. nginx has the larger community by that measure.
Are nginx and landscape free?
Both are open source. nginx is licensed under BSD-2-Clause and landscape under GPL-3.0. Neither carries a licence fee.
What is the difference between nginx and landscape?
nginx is written in C 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, nginx or landscape?
Choose nginx if you want the larger community (32,114 stars) or its BSD-2-Clause licence terms. Choose landscape if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.