Ubiquiti explicitly cautions that hundreds of devices across multiple sites can create high load and performance degradation unless the Network Application is tuned.
Large homelabs, schools, offices and multi-site deployments.UniFi Network Application Hardware Requirements: CPU, RAM & Device Scale
Check UniFi Network self-hosting requirements for x86-64 CPU, 2 GB RAM, storage, device scale and suitable ZimaOS hardware.
UniFi Network requirements at a glance
Ubiquiti's current self-hosting documentation publishes a concrete hardware baseline: an x86-64 processor, at least 2 GB RAM, 100 Mbps wired Ethernet and at least 10 GB free storage. For larger deployments, especially hundreds of UniFi devices across multiple sites, Ubiquiti separately documents memory, MongoDB and inform-thread tuning because device count and database activity can push resource needs far above the entry baseline.
- CPU
- Official baseline: x86-64 processor. Ubiquiti does not publish a specific core count or clock speed for ordinary self-hosting.
- RAM
- Official minimum: 2 GB RAM. High-device-count deployments may need larger UniFi memory allocations and more host RAM.
- Network
- Official baseline: 100 Mbps wired Ethernet. Practical network needs depend on controller-to-device communication, backups, remote management and the rest of the host workload rather than client data-plane throughput.
- Storage
- Official baseline: at least 10 GB free. Database growth, backups, logs and long retention justify additional free space.
- Large deployments
- Ubiquiti warns that hundreds of UniFi devices across multiple sites can create high load. The default application XMX/XMS memory setting is 1 GB and may need to be increased to 2 GB, 4 GB or more at scale.
- Best Zima starting point
- ZimaBoard 2 832 is far above the 2 GB RAM and 100 Mbps baseline and is a strong fit for a typical home/small-office UniFi controller. Choose more memory or ZimaCube hardware when the whole network-management and self-hosting stack becomes larger.
From official requirements to the right setup
UniFi sizing starts with the official self-hosted baseline, then scales by adopted devices, sites and database/application memory pressure.
-
Official requirements
Confirm the deployment model first. ZimaOS currently provides a UniFi Network Application package, while Ubiquiti now positions UniFi OS Server as the new standard for self-hosting. Treat the Ubiquiti baseline as hardware guidance, but do not assume the ZimaOS package has the same host-level Podman/systemd requirements as UniFi OS Server.
-
Confirm your needs
Meet the official hardware floor: x86-64 CPU, 2 GB RAM, wired networking and at least 10 GB free storage.
-
Leave room to grow
Estimate adopted device and site count. Ubiquiti specifically warns that hundreds of devices across multiple sites can create high load, and its tuning guide recommends increasing application memory before assuming that more CPU alone is the fix.
-
Run it on ZimaOS
Install UniFi Network Application from the ZimaOS App Store, adopt representative devices, retain realistic statistics/backups, then observe application memory, CPU, database activity and inform/heartbeat stability during normal operation.
Check every playback client
- x86-64 host CPU
- At least 2 GB available host memory for the official baseline
- At least 10 GB free persistent storage
- Number of adopted access points, switches and gateways
- Number of managed sites
- Statistics/log retention and backup frequency
- Inform/heartbeat stability
- Other ZimaOS networking and monitoring apps sharing the host
Official minimum requirements
Ubiquiti currently publishes explicit self-hosting hardware specifications. These values are a valid minimum baseline for the UniFi Network control plane, but they are not a sizing guarantee for hundreds of devices or multi-site management.
For a new ZimaOS hardware page, use 2 GB RAM, x86-64, 100 Mbps wired Ethernet and 10 GB free storage as the official floor. Then size upward from actual device count, memory pressure, database behavior and the rest of the host workload.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU | x86-64 processor | Ubiquiti's current published self-hosting hardware requirement. |
| RAM | Minimum 2 GB | This is the official baseline, not the recommended amount for very large device counts. |
| Network | 100 Mbps wired Ethernet | The controller manages devices; ordinary client data traffic does not necessarily traverse the Network Application host. |
| Storage | At least 10 GB free | Leave additional space for database growth, logs, updates and backups. |
| Ports | Required UniFi ports must be reachable; Ubiquiti examples include TCP 8080 and UDP 3478 | Correct discovery/adoption/inform networking is a compatibility requirement, not a compute requirement. |
| Current self-hosting direction | UniFi OS Server replaces the legacy UniFi Network Server | ZimaOS still lists UniFi Network Application, so deployment semantics should be kept separate from Ubiquiti's newer host-level OS Server installer. |
When to upgrade your hardware
Upgrade UniFi controller hardware when device scale and database/application pressure become measurable.
Hundreds of devices are managed across multiple sites
UniFi application memory is repeatedly hitting its ceiling
Mongo/database activity and backups are stressing the host
Ubiquiti says the default XMX/XMS allocation is 1 GB and documents increasing it to 2 GB, 4 GB, 8 GB or more depending on scale before simply replacing the CPU.
Growing controllers with high CPU, garbage-collection or UI responsiveness issues.Large installations can require Mongo cache and connection tuning or even independent database scaling. Database pressure can therefore justify more memory, CPU and reliable storage.
Long-running controllers with substantial device history and management data.Plan hardware growth with confidence
Scale UniFi by increasing application memory and storage headroom in response to device scale rather than buying hardware from a generic 'controller' label.
Increase UniFi memory allocation before replacing the CPU
Ubiquiti's high-device-count guide explicitly recommends raising XMX/XMS and checking whether CPU pressure falls before moving to a larger machine.
Choose enough host RAM to leave room for a larger UniFi heap plus ZimaOS and any companion services.Keep controller data on reliable persistent storage
Device history, Mongo data, logs and backups accumulate over time even though the official floor is only 10 GB.
Use reliable SSD/eMMC/NVMe application storage with comfortable free space and regular backups.Monitor device heartbeat/inform concurrency
Ubiquiti documents a default 200 simultaneous inform connections and separate tuning for very large deployments.
Treat missed heartbeats and high CPU as operational scaling signals rather than blindly increasing thread counts.Upgrade the server for the broader network stack
DNS, VPN, reverse proxy, monitoring, logging and other services may consume more resources than UniFi itself in a home server.
Move to 16 GB or ZimaCube tiers when the combined networking/self-hosting workloadโnot the controller aloneโneeds it.Can it run on ZimaOS?
UniFi Network Application is currently listed in the ZimaOS App Store, but Ubiquiti's broader self-hosting product direction has moved toward UniFi OS Server.
Install UniFi Network Application from the ZimaOS App Store
Use the packaged ZimaOS application for the existing Network Application deployment model.
Open UniFi Network Application in the ZimaOS App StoreDo not confuse the ZimaOS package with UniFi OS Server
Ubiquiti now calls UniFi OS Server the new self-hosting standard and states that it replaces the legacy Network Server. Its host-level installation requirements should not automatically be mapped onto a containerized ZimaOS app.
Read Ubiquiti self-hosting guidanceTune only when device scale proves it is necessary
For hundreds of devices or multiple sites, use Ubiquiti's memory, Mongo and inform-thread tuning guidance and monitor the real controller before changing hardware.
Read UniFi high-device-count tuningChoose Zima hardware for UniFi Network Application
The official UniFi self-hosting baseline is modest. Choose more Zima hardware for device scale, database/history load and other networking services rather than because the controller UI itself is demanding.
Is this a normal home/small-office controller or a high-device-count multi-site controller?
Home or small-office deployment
ZimaBoard 2 already exceeds the official controller baseline by a wide margin.
- Typical UniFi controllerZimaBoard 2 832
- Controller plus more network/monitoring appsZimaBoard 2 1664
Larger controller plus substantial storage/self-hosting stack
Move up for database headroom, integrated storage and the rest of the server workload.
- Large all-in-one network/storage serverZimaCube 2 Standard
- Heavier multi-service environment and 10GbE workflowZimaCube 2 Pro
Meeting the 2 GB / x86-64 / 10 GB baseline does not guarantee a specific maximum number of devices. Site count, statistics retention, database size, inform concurrency, backups and co-hosted services can materially change resource needs.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | A home or small-office UniFi Network Application controller. | Managing UniFi APs/switches and ordinary device history with light companion services. |
|
Very large multi-site/device deployments can require larger UniFi memory allocations and additional database/CPU headroom. | Get Now |
| ZimaBoard 2 1664 | A larger network-management host running UniFi plus DNS, VPN, monitoring and other services. | More controller history, more network apps and additional containers on one compact host. |
|
16 GB is for whole-server headroom; UniFi's official baseline is still 2 GB. | Get Now |
| ZimaCube 2 Standard | An all-in-one NAS/network platform where UniFi is one component. | Larger controller deployment plus multi-drive storage and self-hosted services. |
|
Choose it for application/storage consolidation, not because UniFi alone requires a Core i3. | Get Now |
| ZimaCube 2 Pro | A large all-in-one network/storage environment with higher local throughput needs. | Many services, controller database/history, backups and 10GbE-capable local workflows. |
|
10GbE is a whole-server/storage feature; UniFi's controller traffic does not inherently require it. | 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 use Ubiquiti's current self-hosting baseline while keeping ZimaOS's Network Application package distinct from the newer UniFi OS Server product.
How much RAM does UniFi Network need?
Ubiquiti's current self-hosting requirements list a minimum of 2 GB RAM. Large deployments may need a larger UniFi application memory allocation and more total host RAM.
What CPU does a self-hosted UniFi controller require?
Ubiquiti lists an x86-64 processor but does not specify a minimum core count or clock speed for ordinary self-hosting.
How much storage does UniFi Network need?
Ubiquiti currently lists at least 10 GB free. Long device history, logs, updates and backups justify additional headroom.
Can ZimaBoard 2 832 run UniFi Network Application?
Yes. Its x86-64 Intel N150, 8 GB RAM, 32 GB eMMC and dual 2.5GbE are comfortably above the published 2 GB RAM, 10 GB storage and 100 Mbps network baseline.
Does UniFi Network need a GPU?
No. Controller, database, device management and networking workloads do not require a dedicated GPU.
How many UniFi devices can one server manage?
Ubiquiti does not publish one universal device-count limit for the baseline hardware. Its tuning guide specifically warns that hundreds of devices across multiple sites can create high load and require memory/database/thread tuning.
Why can UniFi use more than 2 GB in a large deployment?
The 2 GB figure is a host baseline. Ubiquiti documents raising the Network Application's default 1 GB XMX/XMS allocation to 2 GB, 4 GB or more when scale requires it.
Is UniFi OS Server the same thing as the ZimaOS UniFi Network Application app?
No. Ubiquiti now calls UniFi OS Server the new self-hosting standard replacing the legacy Network Server. ZimaOS currently lists UniFi Network Application, so the packaging and host-level installation model are not identical even though the controller workload is related.
What sources and further reading informed this UniFi Network hardware guide?
Ubiquiti's current Self-Hosting UniFi page is the primary source for the x86-64, 2 GB RAM, 100 Mbps Ethernet and 10 GB free-storage baseline and for the current transition to UniFi OS Server. Ubiquiti's high-device-count tuning guide explains memory, MongoDB and inform-thread scaling. The required-ports reference covers controller/device connectivity. The ZimaOS App Store confirms the current UniFi Network Application package. A 2026 HostiFi article independently restates the same published baseline but is secondary to Ubiquiti.
