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.

Editor

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
PriceFree + PaidFree
LicenceBSD-3-Clause / AGPL-3.0AGPL-3.0
Web UIYesYes
iOSYes–
AndroidYes–
WindowsYes–
macOSYes–
LinuxYes–
DockerYesYes
Linux packageYes–
Tech stackGoNode
Docker Containers3 (app + Dashboard, Traefik)1 (app only)
DatabaseSQLiteSQLite
Minimum hardware1 CPU · 2 GB RAMNot stated
Architecturex86 + ARMx86 + ARM

Common questions

Sources: NetBird docs and wg-easy docs.

Updated