NetBird prefers direct P2P WireGuard but uses relay when NAT/connectivity prevents a direct path. Relayed traffic shares relay bandwidth and adds latency, so the relay server's network and CPU path become meaningful at scale.
Networks with restrictive NAT, mobile clients or many remote sites.متطلبات أجهزة NetBird: وحدة المعالجة المركزية وذاكرة الوصول العشوائي والمرحل وحجم شبكة VPN
تحقّق من متطلبات الاستضافة الذاتية لـ NetBird لمعالج واحد، وذاكرة وصول عشوائي بسعة 2 غيغابايت، والمنافذ، والمرحّلات، وتوسّع قاعدة البيانات، وأجهزة ZimaOS المناسبة.
NetBird requirements at a glance
NetBird's current self-hosted Quickstart publishes a clear infrastructure baseline: a Linux VM with at least 1 CPU and 2 GB RAM, public TCP 80/443, UDP 3478 and a public domain. NetBird's newer combined architecture is lighter than older releases, but the Quickstart still uses 2 GB as the recommended installation floor. Larger deployments scale mainly through relay bandwidth, peer/network topology, database concurrency and high-availability needs.
- CPU
- Official Quickstart baseline: at least 1 CPU for the self-hosted Linux VM.
- RAM
- Official Quickstart baseline: at least 2 GB memory. NetBird separately says newer local-user deployments can use roughly 1 GB versus 2–4 GB in the older architecture.
- Ports
- Quickstart requires public TCP 80 and 443 plus UDP 3478, along with a public domain resolving to the server.
- Database
- The default combined deployment uses SQLite. NetBird says SQLite is suitable for smaller teams and recommends PostgreSQL when larger deployments need better concurrency or a dedicated DB host.
- Relay scaling
- Peers prefer direct P2P WireGuard connections. When direct paths fail, traffic is relayed, adding latency and sharing relay bandwidth. Relay capacity can therefore become more important than Management CPU.
- Best Zima starting point
- ZimaBoard 2 832 comfortably exceeds the 1 CPU / 2 GB baseline and is a strong self-hosted starting point. Choose larger hardware or split services when relay bandwidth, database scale, proxy load or co-hosted apps demand it.
From official requirements to the right setup
NetBird sizing starts with the official single-server baseline, then branches into peer connectivity, relay load and database architecture.
-
Official requirements
Meet the current Quickstart baseline: Linux host, at least 1 CPU, 2 GB RAM, public TCP 80/443, UDP 3478 and a resolvable public domain.
-
Confirm your needs
Use the modern combined deployment unless you specifically need the older advanced architecture. NetBird says built-in user management reduced the number of containers and lowered resource requirements to roughly 1 GB in many cases, but the official Quickstart still asks for 2 GB.
-
Leave room to grow
Measure how many connections are direct P2P versus relayed. Relayed traffic traverses your relay server, adds latency and shares relay bandwidth, so heavy relay usage changes the hardware/network requirement much more than idle dashboard activity.
-
Run it on ZimaOS
Install NetBird from ZimaOS, add representative peers/routes/exit-node traffic, observe relay and management load, then move relay services or the database to separate hosts only when availability or scale requires it.
Check every playback client
- Linux host with Docker Compose v2+
- At least 1 CPU and 2 GB RAM
- Public TCP 80/443 and UDP 3478
- Public DNS name pointing to the host
- Number of peers and routes
- Percentage of P2P versus relayed connections
- Relay bandwidth and exit-node traffic
- SQLite versus PostgreSQL and co-hosted services
Official minimum requirements
NetBird's August 2026 Quickstart gives a current, explicit self-hosted infrastructure baseline. A separate architecture comparison explains why newer releases often consume less memory than the older multi-container stack.
Use 1 CPU and 2 GB RAM as the safe current self-hosted baseline. The roughly 1 GB figure describes the reduced resource footprint of the newer architecture, not a replacement for the Quickstart's stated infrastructure requirement.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU | At least 1 CPU | Current official Quickstart infrastructure requirement. |
| RAM | At least 2 GB | Current official Quickstart infrastructure requirement. |
| Public TCP ports | 80 and 443 | Needed by the standard self-hosted deployment/reverse-proxy path. |
| Public UDP port | 3478 | Used for STUN in the default self-hosted architecture. |
| Domain | Public domain resolving to the host IP | Required by the Quickstart for TLS and service access. |
| New architecture footprint | About 1 GB RAM in many deployments | NetBird documents this as a reduction from the older 2–4 GB architecture, not the Quickstart's formal infrastructure floor. |
When to upgrade your hardware
Upgrade NetBird when relay/data-plane traffic or management/database scale becomes the real bottleneck.
Many connections fall back to relay
SQLite concurrency becomes limiting
You need higher availability or service separation
NetBird says the default SQLite store works well for smaller setups but recommends PostgreSQL when larger deployments need better concurrency or a dedicated database host.
Growing teams, larger peer inventories and automation-heavy deployments.NetBird's scaling guide supports extracting relay services, moving PostgreSQL to a dedicated machine and optionally separating Signal. This is an architecture/topology upgrade rather than simply adding RAM to one box.
Business-critical or geographically distributed self-hosted networks.Plan hardware growth with confidence
Scale NetBird by preserving direct P2P paths and splitting components only when the single-server deployment proves insufficient.
Keep peers direct whenever possible
Direct P2P WireGuard avoids routing user traffic through the relay. NetBird troubleshooting notes that relayed traffic is slower and shares relay bandwidth.
Fix NAT/connectivity before buying a larger relay server when direct connectivity should be possible.Move relays out when data-plane traffic grows
NetBird's 2026 scaling guide recommends external relay servers as the most common first split from a single-server deployment.
Give relay hosts enough network bandwidth and place them where latency and availability make sense.Migrate SQLite to PostgreSQL for larger management workloads
NetBird explicitly says SQLite is suitable for smaller teams and PostgreSQL adds better concurrency and operational tooling for larger deployments.
Use a separate DB host only when scale/operations justify the added complexity.Benchmark exit-node throughput before resizing
NetBird's current exit-node guidance says relayed connections and userspace WireGuard can perform well below kernel-mode P2P, and recommends checking connection type, CPU load and MTU before resizing hardware.
Upgrade CPU/network only after confirming the path is already direct/kernel-mode and the exit node is the actual bottleneck.Can it run on ZimaOS?
NetBird is currently listed in the ZimaOS App Store as a WireGuard-based overlay networking platform.
Install NetBird from the ZimaOS App Store
The ZimaOS listing provides NetBird for secure peer networking with SSO/MFA/access-control features.
Open NetBird in the ZimaOS App StoreUse the modern single-server architecture first
The current Quickstart generates a combined deployment with Traefik, Dashboard and netbird-server, using built-in identity management by default.
Read NetBird self-hosting QuickstartSplit relay/database services only when scale requires it
NetBird's scaling documentation describes external relays, PostgreSQL migration and optional Signal separation for reliability and performance.
Read NetBird scaling guidanceChoose Zima hardware for self-hosted NetBird
NetBird's baseline is small. Choose more hardware from relay traffic, database scale, exit-node throughput and other networking services rather than the Dashboard itself.
Is this a personal/small-team NetBird deployment or a larger relay/database-heavy network?
Personal, homelab or small-team deployment
ZimaBoard 2 comfortably clears the self-hosted Quickstart baseline.
- Normal self-hosted NetBirdZimaBoard 2 832
- More network/security apps and service headroomZimaBoard 2 1664
Larger all-in-one server or relay/storage workload
Use ZimaCube for the wider server stack, while considering separate relays/PostgreSQL if NetBird itself must scale beyond one host.
- Large all-in-one network/storage hostZimaCube 2 Standard
- High local throughput and 10GbE service stackZimaCube 2 Pro
The 1 CPU / 2 GB Quickstart requirement does not guarantee a peer count or VPN throughput. P2P versus relayed paths, WAN bandwidth, WireGuard mode, MTU, exit-node use, database concurrency and co-hosted services can change the practical limit.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | A self-hosted NetBird server for a homelab, family or small team. | Management, dashboard, relay/STUN and ordinary peer connectivity on one host. |
|
Heavy relay or exit-node traffic can become a network/data-plane bottleneck even though management memory remains low. | Get Now |
| ZimaBoard 2 1664 | NetBird plus more VPN, proxy, DNS, monitoring and security applications. | Larger network stack and additional ZimaOS containers. |
|
Extra RAM helps the whole host; NetBird's official baseline remains 2 GB. | Get Now |
| ZimaCube 2 Standard | A multi-drive self-hosting server that also runs NetBird. | NetBird management plus storage, applications and broader home-server workloads. |
|
Choose it for application/storage consolidation rather than because NetBird requires a Core i3. | Get Now |
| ZimaCube 2 Pro | A large all-in-one network/storage platform with fast local data workflows. | NetBird plus many services, exit-node/relay use and 10GbE-capable local networking. |
|
10GbE does not fix relayed or userspace WireGuard bottlenecks by itself; validate the tunnel path first. | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”Read full review
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”Read full review
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”Read full review
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”Read full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
★★★★★
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
★★★★★
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
★★★★★
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
★★★★★
Avaliação ZimaBoard 2
Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.
Frequently asked questions
These answers separate NetBird's current self-hosting baseline from lower observed usage and larger scaling architectures.
How much RAM does self-hosted NetBird need?
The current NetBird Quickstart requires at least 2 GB of memory. NetBird also says the newer architecture can use around 1 GB compared with 2–4 GB previously, but the safe documented Quickstart baseline remains 2 GB.
How many CPU cores does NetBird need?
The official self-hosted Quickstart requires at least 1 CPU.
What ports does self-hosted NetBird require?
The current Quickstart requires public TCP ports 80 and 443 plus UDP 3478, along with a public domain resolving to the host.
Can ZimaBoard 2 832 run NetBird?
Yes. Its 4-core Intel N150, 8 GB RAM and dual 2.5GbE substantially exceed NetBird's 1-CPU/2-GB baseline.
Does NetBird need a GPU?
No. WireGuard networking, management, relay and database workloads do not require a dedicated GPU.
When does NetBird need PostgreSQL instead of SQLite?
NetBird says SQLite works well for smaller setups. PostgreSQL becomes useful when larger deployments need better concurrency, a separate database host or stronger operational/backup tooling.
Why can NetBird relay performance be slower than P2P?
Relayed traffic goes through an intermediary relay and shares its bandwidth, while direct P2P traffic flows directly between peers. NetBird therefore recommends diagnosing relayed connections before treating the server CPU as the problem.
When should I choose ZimaCube 2 for NetBird?
Choose it when NetBird is part of a larger multi-drive self-hosting stack or when the whole server needs stronger CPU/network/storage headroom. Large NetBird deployments may benefit more from splitting relays or PostgreSQL onto separate hosts than from one oversized server.
What sources and further reading informed this NetBird hardware guide?
NetBird's August 2026 Self-Hosting Quickstart is the authority for the 1 CPU / 2 GB RAM baseline, required public ports and domain. The self-hosted-versus-cloud guide documents the newer architecture's roughly 1 GB footprint and reduced container count. The scaling and PostgreSQL guides explain when to split relays or migrate beyond SQLite, and the relayed-connection guidance explains the bandwidth/latency penalty of relay paths. The ZimaOS App Store confirms NetBird remains packaged for ZimaOS.
