NetBird vs wg-easy
Editor take
Choose NetBird for direct links between devices and for access policies per group. Choose wg-easy for one container and one open port, and for one-time client links.
Where they differ
Only what is true of one of them and not the other. Each app's weak spots are the other app's strengths.
NetBird
Where NetBird is stronger
- Access policies per groupRules name groups of devices and resources, a protocol, ports and a direction; drop the default all-to-all rule and nothing connects unasked. Every wg-easy client reaches what the host can by default.1
- Devices link to each otherPeers find each other through STUN and ICE and open a WireGuard tunnel directly, with your relay when NAT blocks it; wg-easy sends every client through the server.2
wg-easy
Where wg-easy is stronger
- One container, one open portDocker Compose up, UDP 51820 opened and a public IP instead of a domain; NetBird self-hosted wants a domain, a certificate and three containers.3
- One-time links for new clientsShares a client as a link that works once, sets an expiry date per client and shows a QR code; a NetBird peer joins with a setup key or an SSO login.4
NetBird vs wg-easy: specs side by side
Every spec for both apps in one table, so you can check install options, hardware and client apps before you pick one.
| Spec | ||
|---|---|---|
| Price | Free + Paid | Free |
| Licence | BSD-3-Clause / AGPL-3.0 | AGPL-3.0 |
| Web UI | Yes | Yes |
| iOS | Yes | – |
| Android | Yes | – |
| Windows | Yes | – |
| macOS | Yes | – |
| Linux | Yes | – |
| Docker | Yes | Yes |
| Linux package | Yes | – |
| Tech stack | Go | Node |
| Docker Containers | 3 (app + Dashboard, Traefik) | 1 (app only) |
| Database | SQLite | SQLite |
| Minimum hardware | 1 CPU · 2 GB RAM | Not stated |
| Architecture | x86 + ARM | x86 + ARM |
Common questions
Does NetBird need a public server?
Yes, self-hosted: a public domain with a certificate, TCP 443 open and port 80 kept free for Traefik, plus UDP 3478 for STUN, which the quickstart script sets up. wg-easy needs a public IP or a domain too, but only UDP 51820 open for the tunnel.
Which one can limit what a device reaches?
NetBird. Its policies name groups of devices and resources, ports and a direction, and once the default all-to-all rule is removed nothing connects unasked, so a guest phone can reach one service. Every wg-easy client reaches whatever the host can, with per-client filtering left to an experimental iptables option.
Can I use the stock WireGuard apps with either?
With wg-easy, yes: it writes a standard WireGuard config and a QR code for each client to import. NetBird needs its own client app on each device, which signs in and applies the policies.
Sources: NetBird docs and wg-easy docs.