Requisitos de hardware del controlador UniFi [legacy]: RAM, CPU, almacenamiento y gestión de dispositivos
Planifica el hardware antiguo de UniFi Controller considerando la RAM, la CPU, el estado de MongoDB, la cantidad de dispositivos, los puertos de red y una implementación práctica en ZimaOS.
![Requisitos de hardware del controlador UniFi [legacy]: RAM, CPU, almacenamiento y gestión de dispositivos](http://shop.zimaspace.com/cdn/shop/files/Unifi-controller_legacy.webp?v=1790688426&width=1800)
UniFi Controller [legacy] hardware requirements at a glance
Size UniFi Controller [legacy] from verified upstream requirements first, then add headroom for workload and persistent data.
- RAM
- No numerical official minimum published by the legacy container project
- CPU
- No numerical official minimum published by the legacy container project
- Storage
- Persist /unifi/data, /unifi/log, certificates, and backups
- Network ports
- 8080/tcp, 8443/tcp, 3478/udp, 10001/udp are the legacy project's minimal working set
- Database
- UniFi uses MongoDB; the legacy project supports embedded or separate Mongo patterns
- Best Zima starting point
- ZimaBoard 2 832 for a small legacy controller
From official requirements to the right setup
Start with current upstream facts for UniFi Controller [legacy], then size the actual workload rather than copying generic container or app-store labels.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- UniFi device count
- Site count
- Statistics retention
- MongoDB compatibility
- Inform host IP
- Port ownership
- Controller backup
- Migration plan
Official minimum requirements
The jacobalberty legacy container project documents ports, volumes, MongoDB integration, and deployment behavior but does not publish a numerical whole-host CPU/RAM minimum.
Do not apply current UniFi OS Server hardware numbers directly to this legacy container as if they were its official minimum. Also do not hide that this is a legacy deployment model.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical official minimum published | Scale with devices, sites, statistics, and host consolidation. | |
| No numerical official minimum published | MongoDB and statistics retention influence memory. | |
| jacobalberty/unifi | Community-maintained legacy packaging. | |
| 8080/tcp, 8443/tcp, 3478/udp, 10001/udp | Documented minimal working set in the legacy repository. | |
| /unifi/data and /unifi/log | Configuration and logs must survive container replacement. | |
| MongoDB integration | Can run in-container or as a separate Mongo service depending on setup. | |
| Not required | No GPU workload. |
When to upgrade your hardware
Device/site growth
Statistics growth
Legacy maintenance risk
Plan hardware growth with confidence
SSD controller data
Keep MongoDB/controller state on SSD.
SSDMore RAM
Useful for larger device counts and a broader network-services host.
ZimaBoard 2 1664Log/backup storage
Expand storage when retaining controller history and backups.
Larger SSD/HDD poolMigration capacity
If moving to a newer supported UniFi model, choose hardware for the current platform rather than the legacy container.
Workload-appropriate current platformCan it run on ZimaOS?
Custom install UniFi Controller [legacy] in ZimaOS
No specific public per-app page for the legacy jacobalberty container was verified. ZimaOS currently has a newer UniFi Network Application package, which is not the same artifact.
Custom install UniFi Controller [legacy] in the ZimaOS app ↗Use the legacy container only when migration is not yet possible
The jacobalberty/unifi image is a legacy/community deployment model with persistent /unifi data and MongoDB considerations.
Open legacy UniFi-in-Docker repository ↗Do not confuse it with current UniFi OS Server
Ubiquiti's current self-hosting direction has moved beyond the legacy Network Server/controller model.
Read current UniFi hardware guidance ↗Zima hardware for UniFi Controller [legacy]
The legacy controller is usually light for a small site, but MongoDB, statistics retention, device scale, and maintenance risk determine whether it remains viable.
Choose by workload
Use modest hardware and prioritize backups plus a migration plan.
Do not solve every legacy problem by adding hardware; migrate to a current supported UniFi deployment model.
This page intentionally does not reuse current UniFi OS Server minimums as the legacy container's official requirements.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Light self-hosted services and small databases | Single-app or small multi-app deployments |
|
8 GB RAM and a 4-core N150 limit larger databases, AI stacks, and heavy multi-service workloads | Get Now |
| ZimaBoard 2 1664 | Memory-heavier services and larger multi-container stacks | Workloads that benefit from 16 GB RAM without needing a much faster CPU |
|
CPU throughput remains the same 4-core N150, so compute-heavy workloads can still be CPU-limited | 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
How much RAM does legacy UniFi Controller need?
The legacy jacobalberty container project does not publish a numerical whole-host RAM minimum.
Which ports are required?
The legacy project documents 8080/tcp, 8443/tcp, 3478/udp, and 10001/udp as the minimal working set.
Where is controller data stored?
The legacy container uses /unifi/data for configuration data and /unifi/log for logs.
Does it use MongoDB?
Yes. MongoDB compatibility is part of the legacy controller stack.
Is this the same as current UniFi OS Server?
No. This page is explicitly about the legacy containerized controller model.
Can ZimaBoard 2 832 run a small legacy controller?
Yes as a practical small-site starting point.
Does it need a GPU?
No.
When should I stop scaling the legacy controller?
When database/runtime compatibility or supportability becomes the main problem, migration is more appropriate than adding hardware.
