VPN traffic increases CPU and network load even though idle memory remains tiny.
Multi-user remote access.Firefly Hardware Requirements: RAM, CPU, Storage & Deployment
Plan Firefly WireGuard server hardware for RAM, CPU, VPN throughput, UDP ports and Docker networking, with direct ZimaOS App Store guidance.
Firefly requirements at a glance
Firefly is a lightweight Go-based WireGuard VPN server. Upstream publishes no numerical host CPU/RAM minimum; ZimaOS lists 32 MB minimum memory, while VPN throughput and public network access drive sizing.
- Upstream RAM minimum
- No numerical whole-host minimum published.
- ZimaOS package memory
- Current official ZimaOS listing: 32 MB minimum memory.
- CPU
- No numerical official core minimum. Encryption and VPN throughput determine practical CPU use.
- Ports
- Default Firefly ports are UDP 50120 for WireGuard, TCP 50121 for web management and TCP 50122 for relay.
- Docker networking
- The official Compose file uses host networking, /dev/net/tun, NET_ADMIN and SYS_MODULE.
- Best Zima starting point
- ZimaBoard 2 832 is more than enough for normal household VPN use; WAN speed and routing matter more than RAM.
From official requirements to the right setup
Size Firefly from the real workload and deployment topology rather than generic server assumptions.
-
Official requirements
Install Firefly from the official ZimaOS App Store.
-
Confirm your needs
Forward/open UDP 50120 for normal WireGuard access when the ZimaOS host sits behind a router/NAT; manage TCP 50121/50122 according to your deployment.
-
Leave room to grow
Keep the Firefly configuration directory persistent and protect the web UI with a strong password and HTTPS when exposed remotely.
-
Run it on ZimaOS
Treat VPN throughput as a network/encryption workload: benchmark your WAN and client count before adding hardware.
Check every playback client
- 32 MB package memory
- UDP 50120
- TCP 50121/50122
- Public IP/port forward
- /dev/net/tun
- NET_ADMIN
- VPN client count
- WAN throughput
Official minimum requirements
Firefly upstream documents a compact Go binary and Docker networking but no numerical host-hardware minimum; ZimaOS publishes a 32 MB package memory value.
The 32 MB value is package metadata. Real VPN capacity depends on encryption throughput, WAN speed, client count and routing/NAT conditions.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Upstream host RAM minimum | No numerical minimum published | Project is a compact Go service. |
| ZimaOS package minimum memory | 32 MB | Current public App Store metadata. |
| WireGuard UDP port | 50120 | Current Firefly default. |
| Web management port | 50121/TCP | Current Firefly default. |
| TCP relay port | 50122/TCP | Current Firefly default. |
| Container privileges | NET_ADMIN + SYS_MODULE + /dev/net/tun | Current official Compose pattern. |
When to upgrade your hardware
Scale Firefly when these workload signals appear.
More clients push encrypted throughput
WAN bandwidth becomes the bottleneck
Advanced relay/routing features are enabled
Internet upload/download often caps throughput before server CPU.
Remote file access.Additional TCP relay and routing work can increase processing and complexity.
Advanced VPN deployments.Plan hardware growth with confidence
Scale Firefly only where the workload justifies additional resources.
Keep normal VPN use on ZimaBoard 2 832
The app is tiny and dual 2.5GbE already provides strong local networking.
ZimaBoard 2 832.Focus on router/port configuration
Correct public IP, NAT and UDP forwarding matter more than extra RAM.
Use your existing Zima/router network path.Use 16 GB only for broader host workloads
Extra memory does not materially improve a small Firefly VPN server.
ZimaBoard 2 1664.Use faster platform for very high local/VPN throughput
More CPU/network headroom may help when Firefly is part of a larger high-throughput gateway.
ZimaCube 2 Pro.Can it run on ZimaOS?
Firefly deployment on ZimaOS should follow the verified route below.
Install Firefly from the ZimaOS App Store
Install Firefly directly from ZimaOS, then configure clients and ensure the required WireGuard UDP port is reachable from the internet when remote access is needed.
Install Firefly from the ZimaOS App Store โReview Firefly upstream deployment
Use upstream documentation to understand ports, persistence and feature-specific requirements.
Review Firefly upstream repository โKeep persistent data outside disposable containers
Map configuration, database or uploaded-file paths to durable ZimaOS storage where the app uses persistent state.
Review ZimaOS download and app platform โChoose Zima hardware for Firefly
Firefly is tiny at idle; VPN encryption throughput, WAN bandwidth and routing determine actual capacity.
Which Firefly workload are you running?
Normal household VPN
Use ZimaBoard 2 832 and focus on port forwarding/security.
- Best starting pointZimaBoard 2 832
High-throughput gateway / broader server
Use stronger CPU/network only if measured VPN workload justifies it.
- Higher-headroom platformZimaCube 2 Pro
The 32 MB ZimaOS package value is not a throughput guarantee.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Normal Firefly home VPN. | Several clients, WireGuard routing and remote Zima access. |
|
WAN/router limits usually matter before hardware. | Get Now |
| ZimaCube 2 Pro | High-throughput VPN plus broader services. | More CPU/network headroom and other server workloads. |
|
Do not expect 10GbE LAN to overcome WAN or ISP limits. | 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 cover Firefly RAM, CPU, storage and ZimaOS deployment.
How much RAM does Firefly need?
Upstream does not publish a numerical whole-host minimum; the current ZimaOS package lists 32 MB minimum memory.
Which ports does Firefly use?
Defaults are UDP 50120 for WireGuard, TCP 50121 for the web UI and TCP 50122 for relay.
Does Firefly need /dev/net/tun?
Yes. The official Docker Compose uses /dev/net/tun plus NET_ADMIN and SYS_MODULE.
What usually limits Firefly VPN speed?
WAN bandwidth, encryption throughput, routing/NAT and client count.
Does Firefly need a GPU?
No.
Can ZimaBoard 2 run Firefly?
Yes. The 8 GB model is far above the application's memory needs.
Do I need port forwarding?
Usually yes when the ZimaOS host is behind a router and clients must reach the WireGuard UDP port from the public internet.
Is Firefly in the ZimaOS App Store?
Yes. A public official ZimaOS App Store page is available.
What sources informed this Firefly hardware guide?
Current Firefly ZimaOS listing, upstream repository/Compose file and Zima product pages.
