Short answer: choose self-hosting when someone owns operations
Self-hosted NetBird suits operators who want central access policies and control of their networking infrastructure; Cloud suits those who want NetBird to operate the servers and relays. Our source build succeeded in 5 seconds, while the test command failed after 897 seconds. The adoption decision starts with who will maintain the network, manage configuration changes and restore access after a failure. Compilation supplies a contributor-facing result; deployment ownership supplies the reason to choose self-hosting.
NetBird connects enrolled devices through WireGuard tunnels and manages access centrally. Routing peers extend access to internal resources without installing the client on every destination. The optional reverse proxy supplies another access path: selected internal resources become reachable from the internet. Decide whether you need private device access, browser access to an application, or both. The routing-peer onboarding guide and proxy setup instructions describe these separate roles.
GitHub activity and release identity
GitHub recorded 31,057 stars, 786 combined open issues and pull requests, and a last push on November 17, 2026. The latest-release record names v0.83.1, published November 13, 2026. Its changelog records a Windows user-lookup fallback fix. The queue includes pull requests as well as issues. The release identity also differs from the October source checkout used for our build and test measurements, so those results belong beside their recorded commit.
The NetBird repository warns that its main branch may be unstable or broken during development and directs users to releases for stable versions. Keep the chosen release and configuration together in deployment records. The v0.83.1 release page supplies the release identity. The October run used commit aa0f569; the November module probe records checkout 332fb1cfc7b1 and an installed module version of v0.83.1.
What people use NetBird for
Users describe NetBird deployments for home services, LAN gateways and distributed homelab machines. A routing peer connects resources behind a participating machine, while a cloud-hosted management deployment places coordinating infrastructure outside the home. These accounts help readers compare network layouts: the important choices include where management runs, which machine bridges the LAN and whether access uses a client or a public application endpoint. Each example below retains its reporter and source.
| Who reported it | Use case | Reported outcome and source |
|---|---|---|
| sf_frankie on r/selfhosted | NetBird with its reverse proxy on a free Oracle VPS | Described setup as very easy. Oracle VPS deployment account |
| Serious_Ship7011 on r/homelab | Dedicated cloud server for NetBird and Authentik, another VPS for reverse proxying, and a LAN bridge for AI workers and CI runners | Described this as their running topology. Distributed homelab account |
| moserpjm on GitHub | Patched FreeBSD client and OPNsense plugin as a LAN gateway | Reported gateway operation after disabling custom routing and making the client identify as Linux. FreeBSD gateway issue #2200 |
| robdeweese on GitHub | Community client on pfSense ARM and OPNsense x86-64 | Reported operation on both, including egress. Community build follow-up |
ElectronicMeaning973 reported a Hetzner VPS deployment, and ObjectiveSort described running NetBird in a cloud region of their choice in the homelab discussion. NetBird employee victorialslocum described sharing internal software with teams or individuals through access policies without a public link. That employee account of internal use illustrates another application of private reachability: access can follow team membership rather than possession of a public URL.
What happened when we ran it
Our October 21, 2026 sandbox installed source dependencies in 149 seconds, built commit aa0f569 in 5 seconds and returned a failed test command after 897 seconds. We measured 57 passing and 1 failing result out of 58 recorded Go results. The command exited with status 1 and did not time out. The complete recorded duration was 1,061 seconds. These are the results of our source-checking run, kept separate from the November module probe.
| Recorded step | Outcome | Duration |
|---|---|---|
| Install | Succeeded; 740 dependencies recorded | 149 seconds |
| Build | Succeeded | 5 seconds |
| Tests | Failed, exit 1; 57 passed and 1 failed out of 58 recorded results | 897 seconds |
The sandbox configuration listed 3 CPUs, 8 GB RAM and image golang:1.24-bookworm. The checkout contained 3,368 files, approximately 628,938 source lines and 29.6 MB. Its scan recorded 27 CI workflow files, no Dockerfile and no tests directory. Those last two entries describe scanner output for this checkout. The test command produced Go results, and the self-hosting documentation uses published containers through Docker Compose.
The failing tail names Test_S3HandlerGetUploadURL, followed by FAIL for github.com/netbirdio/netbird/upload-server/server. The same tail records successful results for tools/idp-migrate, trustedproxy, util, utility subpackages and version before the final FAIL. The useful contributor outcome is therefore a successful compilation and a named failing test and package. Keeping both outcomes visible prevents the five-second build result from being mistaken for an overall passing test run.
The separate November 17 probe identifies checkout 332fb1cfc7b1 and recipe quickstart-lib. It used a fresh unprivileged golang:1.24-bookworm container configured with 2 CPUs and 4 GB RAM, without published ports or secrets. Installation fetched NetBird from the Go module proxy. The recorded snippet failure concerns the recipe's search for a Go example in the README; the table preserves that failed step alongside installation and teardown.
| Probe step | Recorded outcome | Source |
|---|---|---|
| Clone | Recipe quickstart-lib in 3 seconds | Clone record |
| Install | go get github.com/netbirdio/netbird@latest in a new module installed v0.83.1 in 17.9 seconds | Module installation record |
| Installed size | 670.4 MB on disk after installation, described as the module cache | Module-cache size record |
| Dependency count | 354 packages besides github.com/netbirdio/netbird installed | Package-count record |
| Snippet | Failed because the README has no Go code block to run | Failed snippet record |
| Finding | no-snippet: the README has no Go code block to run | Named finding |
| Teardown | Recorded as ok | Teardown record |
Where people get stuck: identity, roaming and proxy paths
Issue #2454 records a macOS recovery improvement in 0.29.3 followed by paularlott's regression report for 0.30.2. Other threads describe Android battery use, authentication trouble and browser-session failures. Platform, version and reporter matter when using these histories for troubleshooting: a workaround described for an older client is a specific report with a specific context. The table separates user symptoms from the responses and recovery actions recorded in each discussion.
| Report | What users reported | Response or workaround recorded |
|---|---|---|
| Android battery issue #1354 | Pounii25 described drain with private DNS; Ginner described heat and drain after WiFi/mobile changes | Pounii25 reported relief after more than 2 hours without DNS forwarding. Ginner used restart or logout/login. |
| macOS recovery issue #2454 | Connected status with unusable peer access after sleep or network changes | Recovery was reported in 0.29.3, then regression in 0.30.2; reconnecting or restarting the service was used. |
| Browser RDP and SSH issue #4580 | Session attempts returned users to the management interface | Maintainers requested management, signal and dashboard updates and revised proxy templates; later users continued reporting failures. |
| Authentik issue #2941 | Dashboard access failed after an Authentik upgrade | Users reported recovery through API scopes, redirect changes and a management restart. |
| Simultaneous-network issue #446 | Users wanted access to isolated networks from one device | Maintainers described separate Linux configurations; nazarewk reported one systemd service per network. |
The Android resource-loading report #2158 names Android client 0.0.23 on a Pixel 7 Pro running Android 14. A maintainer offered an updated APK for testing. Battery consumption and resource loading are separate reported problems, so they call for separate observations. Likewise, the FreeBSD gateway account records a client patch, while the current README separately lists FreeBSD, pfSense and OPNsense among its platforms.
The resource troubleshooting guide separates DNS, routes, policy, forwarding and the destination handshake. A service running on the routing peer itself needs a peer-to-peer policy; userspace peers also need NB_ENABLE_LOCAL_FORWARDING enabled. A destination on another LAN machine uses the forwarding path instead. In the guide's RDP gateway example, the TCP handshake completed, but the gateway rejected the session because its registered upstream destination was incorrect.
Self-hosting makes an external identity provider optional
NetBird supports local user management, so self-hosting does not require a separate identity provider. The Cloud and self-hosted comparison describes creating and managing users directly in NetBird, with external providers available when wanted. For a homelab operator, local accounts provide a documented route without adding a separate identity service solely for this network. An existing organisation can instead consider how external identity fits its account administration.
The current self-hosting quickstart requires a Linux VM, a public domain, Docker Compose, curl and jq. With built-in Traefik, public TCP 443 handles certificates through TLS-ALPN-01, and UDP 3478 must also be reachable. TCP 80 must be free locally because Traefik binds it. Choose the reverse proxy before preparing certificates and firewall rules: the quickstart distinguishes the default Traefik certificate path from other proxy choices.
The deployment comparison assigns maintenance, backups and relay setup to self-hosters. It also lists provisioning, traffic-event logging, event streaming, EDR integrations and peer approval as available with an Enterprise Commercial License for self-hosted deployments. MSP functionality is Cloud-only. List the administrative features your deployment needs before selecting the community deployment, so infrastructure control and the required management features inform the same decision.
Security starts with the policy you leave enabled
The onboarding guide says a default policy allows connections between all your devices. Its demonstration disables that policy to make ping fail, then restores it to restore connectivity. The policy demonstration gives a concrete starting point for understanding groups and permitted resources. For a shared deployment, enrollment and access policy are separate decisions: adding a device establishes its participation, while policy determines the connections that participation permits.
NetBird staff member ashley-netbird described the control-plane trust model in a selfhosted risk discussion. According to that reply, device keys stay local, while a compromised control plane could manipulate topology, modify access policies or potentially add peers. The reply identifies valid setup keys or identity-provider compromise as enrollment routes. This distinction connects encrypted payloads with a separate administrative question: who can change the network and its access rules?
NetBird vs Tailscale, Headscale, Pangolin and WireGuard
Headscale implements a self-hosted Tailscale control server, while NetBird supplies its own management service and clients. Decide whether you want to retain a Tailscale-based network or adopt NetBird's enrollment and policy workflow. Community discussions add application-access and identity preferences as reasons to compare products. Starting with the access path and account requirements gives the comparison a concrete job: selecting a workflow that matches the network you intend to operate.
| Choice | Evidence-backed distinction | Decision to make |
|---|---|---|
| NetBird vs Tailscale | Spare-Ad-1429 cited self-hosting and identity preferences in the Tailscale migration discussion | Name the requirement that warrants replacing working access. |
| NetBird vs Headscale | Headscale is a self-hosted implementation of the Tailscale control server, according to the Headscale repository | Investigate it when retaining a Tailscale-based network is the goal. |
| NetBird vs Pangolin | Participants described both proxy and private tunnel capabilities in the Pangolin discussion | Compare the browser-to-application and device-to-network workflows you need. |
| NetBird vs plain WireGuard | NetBird documents automated keys, addresses and public-key distribution in its architecture comparison | Decide whether central management justifies the additional services. |
The Pangolin discussion centres on an iPhone already using another always-on VPN and an operator wanting selected application access. Participants also discuss retaining Authelia and Caddy. Draw that browser-to-application path before comparing configuration screens. Separately, NetBird's quickstart describes an optional proxy that selectively exposes internal resources through dashboard controls. These are useful details for comparing application access with device networking, beyond whether a product lists VPN and proxy features.
What the other reviews get wrong
Default built-in Traefik needs public TCP 443 and UDP 3478; endpoint language about avoiding open ports therefore needs a server-side distinction. The inspected examples here are vendor pages, a self-hosting video and older documentation. The homepage's deployment language and current quickstart requirements concern different parts of the network. Keeping a home resource private can still involve publicly reachable coordinating infrastructure on a VM.
NetBird uses encrypted relay fallback when direct connectivity fails. The README architecture explanation describes this path after unsuccessful NAT traversal, so direct peer connections and relays both belong in a deployment design. The self-hosting video's public-port-80 requirement also needs the current Traefik qualification: the written quickstart uses port 443 for certificate issuance and renewal, while retaining a local port-80 binding. Proxy choice determines the relevant certificate instructions.
The November onboarding guidance requires sudo or root for ordinary headless enrollment, with an exception for an administrator-assigned profile owner. It also places setup keys under Settings and describes Users and Groups separately. Follow the current onboarding guidance when matching instructions to the interface. The older onboarding page uses different dashboard destinations, which explains why older walkthroughs can send a new user to the wrong location.
FAQ
NetBird is a WireGuard-based private networking platform with centrally managed access policies. Client installation joins an existing deployment; self-hosting creates the management infrastructure that clients join. The questions below address downloads, enrollment, account access and deployment choices. Keeping those two installation tasks separate helps a first-time user choose the right instructions before downloading a package or preparing a server.
What is NetBird, and how does its architecture work?
NetBird agents manage WireGuard, receive network state from management and negotiate connections through a signal service. The README architecture description explains ICE and STUN connection discovery and relay fallback when direct connectivity fails. A routing peer adds access to resources without their own client, as described in the remote-network onboarding flow. These components connect device enrollment, connection negotiation and access to resources behind another machine.
Where can I download the NetBird VPN client?
The README directs client downloads to the official NetBird installer page. Its platform list includes Linux, Windows, macOS, Android and iOS, alongside other targets. The installation overview says a client joins a pre-existing deployment and points to platform-specific methods. Choose the instructions for the device being enrolled, then select Cloud or the address of the self-hosted deployment during connection.
How do I install NetBird and connect my first devices?
The desktop installation flow opens a browser for authentication after you select Connect and choose Cloud or your self-hosted deployment URL. The installation overview describes that sequence. The onboarding guide then demonstrates traffic between peers and the policy permitting it. Follow both parts so your setup records include the enrolled device, a working connection and the intended access rule.
How do I self-host the entire NetBird platform?
The README requires a Linux VM with at least 1 CPU and 2 GB memory, a public domain and Docker Compose v2 or higher. The current quickstart supplies proxy-specific networking requirements and installation instructions. Prepare the domain and choose the reverse proxy before enrolling clients. For built-in Traefik, the public certificate path uses TCP 443, with UDP 3478 reachable and TCP 80 free locally.
What changed in NetBird's simplified setup, and can it now expose public services?
Local user management makes an external identity provider optional, according to the deployment comparison. The proxy setup instructions separately describe enabling the optional NetBird Proxy service with built-in Traefik and adding wildcard DNS. Dashboard controls select which internal resources are exposed to the internet. Local accounts govern user administration; proxy configuration determines which applications receive a public access path.
How do I log in to NetBird and open its dashboard?
The README directs Cloud users to sign up with Google, Microsoft, GitHub or an email address and open the NetBird admin interface. A self-hosted deployment uses its own address. The installation guide describes selecting the deployment in the desktop client, which opens browser authentication for the device. The chosen deployment address therefore matters both for administration and for connecting the client.
How do I update NetBird?
The quickstart points to separate backup and upgrade instructions and treats Traefik and CrowdSec updates separately from NetBird. Use the quickstart maintenance guidance for the selected deployment. In the browser-client issue, maintainers requested updates to management, signal and dashboard together. That historical instruction illustrates why an update can involve several components and why deployment-specific guidance matters.
How do I change or recover my NetBird password?
Self-hosted local user management provides NetBird-managed accounts, while external identity-provider accounts use their provider's account system. The deployment comparison establishes those choices, and the self-hosting quickstart includes an admin-password recovery topic. Start by identifying the account system used by the deployment. Local account recovery and recovery through an external identity provider follow different administrative paths.
How do I uninstall NetBird?
On Windows, Add/Remove programs removes the NetBird client and service, according to the Windows installation guide. The installer creates both a UI client and a daemon service, so the documented removal procedure covers those two installed components. This gives Windows users a concrete operating-system procedure for removing the package. Other devices have their own platform-specific installation instructions in the client documentation.
Is switching from Tailscale to NetBird worthwhile for everyday homelab use?
Self-hosting control and identity preferences are reasons participants gave in the Tailscale-to-NetBird discussion. Keep working access unless a specific requirement makes migration useful. sf_frankie's Oracle VPS account supplies one concrete NetBird deployment example. Compare that topology with the servers, resources and account system you intend to operate, then identify which requirement the replacement would satisfy before planning the move.
How does NetBird compare with Headscale?
Headscale is an open source, self-hosted implementation of the Tailscale control server. Its repository describes a narrow scope aimed at a single tailnet for personal use or a small open-source organisation. NetBird supplies its own management service and clients. Start with Headscale when retaining a Tailscale-based network is the requirement, then compare its documented scope with the users and resources your deployment needs to connect.
What we have not tested yet
Our measurements cover source preparation, compilation, a failing test command and a separate module-fetch probe. They exclude deployment of the full server stack, client enrollment, policy denial and a successful VPN session. The failed test's assertion is absent from the recorded tail, leaving its cause unresolved. Sandbox image labels record configuration rather than actual toolchain versions. The October result belongs to aa0f569 rather than the v0.83.1 release, and the module probe contains no executed application example.
Current Android idle battery use, private DNS, WiFi/mobile transitions and resource-loading behaviour need direct testing. So do macOS sleep recovery, simultaneous isolated networks on Windows, current FreeBSD routing and browser RDP or SSH behind self-hosted proxies. Historical workarounds, issue closure and README platform listings answer different questions. Profile switching, simultaneous connections and Cloud-only MSP management also require separate evaluation against the operator's intended workflow.
The records contain no independent comparative throughput measurement, relay-capacity result, fleet-size limit or availability measurement. NetBird's benchmark announcement supplies no usable results table for ranking alternatives, and historical login preferences do not settle Tailscale's current authentication requirements. The Authelia, Caddy and iPhone design is unfinished in the discussion. The module probe includes no known-answer application task or screenshot records, and no independently timed full installation establishes the five-minute setup promise.
The supplied evidence does not establish a logout procedure for any platform. Ginner's historical Android logout/login workaround appears in troubleshooting above; it supplies no instructions for locating or operating logout controls. Password-recovery execution also needs direct checks. Community deployment accounts and the staff security explanation are attributed reports rather than our reliability measurements or an independent security assessment. Rendered layout, resolved evidence links, recommendation modules and other template behaviour fall outside this text review. Before relying on NetBird as the only route into a network, exercise allowed and denied connections, sleep recovery and phone roaming on the actual devices.


