متطلبات أجهزة ZTnet: ذاكرة الوصول العشوائي، ووحدة المعالجة المركزية، والتخزين، وشبكات ZeroTier
خطّط لأجهزة ZTnet من حيث ذاكرة RAM ووحدة المعالجة المركزية وشبكات ZeroTier وحالة وحدة التحكم وشبكات Docker وتوصيات عملية لنشر ZimaOS.
ZTnet hardware requirements at a glance
Size ZTnet from verified upstream requirements first, then add headroom for workload and persistent data.
- RAM
- No numerical official minimum published
- CPU
- No numerical official minimum published
- Storage
- Persist ZTnet database/configuration and ZeroTier controller identity/state
- Networking
- ZeroTier itself may require /dev/net/tun and elevated network capabilities in containers
- Project status
- Upstream labels ZTnet as BETA
- Best Zima starting point
- ZimaBoard 2 832
From official requirements to the right setup
Start with current upstream facts for ZTnet, 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
- Network count
- Member/node count
- Organizations/users
- Controller identity backup
- /dev/net/tun access
- Container capabilities
- Mail/integration services
- Other network apps
Official minimum requirements
ZTnet publishes its self-hosted controller architecture and Docker deployment but does not publish a numerical whole-host CPU, RAM, or disk minimum.
The ZimaOS App Store's 256 MB memory label is catalog metadata, not an upstream ZTnet official minimum. Network scale and controller state are the relevant sizing variables.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical official minimum published | Scale with networks, members, users, and API/controller work. | |
| No numerical official minimum published | Depends on deployment scale and co-located services. | |
| Dockerized self-hosted ZeroTier controller + web UI | The repository includes Docker/Compose assets. | |
| Next.js/Prisma-based application | Relevant to app/database state, not a hardware floor. | |
| May require NET_ADMIN, SYS_ADMIN, and /dev/net/tun | Needed for ZeroTier networking in Docker scenarios. | |
| BETA | Backups and upgrade testing are important. | |
| Not required | No GPU workload. |
When to upgrade your hardware
Network/member growth
Database/state growth
Networking complexity
Plan hardware growth with confidence
SSD controller state
Keep ZTnet and ZeroTier state on reliable SSD storage.
SSDMore RAM
Useful for larger organizations and a consolidated network-services host.
ZimaBoard 2 1664Backup capacity
Keep controller identity and database backups outside the app volume.
Backup storageStronger shared-host CPU
Useful when many network services run together.
ZimaCube 2 ProCan it run on ZimaOS?
Install ZTnet from the ZimaOS App Store
A specific public ZTnet App Store page is verified, so this page uses the one-click route.
Open ZTnet in the ZimaOS App Store ↗Use the upstream ZTnet project
The project is a self-hosted ZeroTier controller with multi-user and organization support and is currently labeled beta.
Open ZTnet source ↗Preserve ZeroTier networking requirements
Containerized ZeroTier can require elevated network capabilities and /dev/net/tun access.
Open ZeroTier Docker guidance ↗Zima hardware for ZTnet
ZTnet is a networking/control-plane workload; application state, member scale, and container network privileges matter more than raw storage capacity.
Choose by workload
Use ZimaBoard 2 832 with reliable persistent state and backups.
Add RAM/CPU based on measured controller and host-wide load.
Do not treat the ZimaOS App Store's 256 MB catalog label as an upstream official minimum.
| 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 |
| ZimaCube 2 Pro | CPU-heavier, database-heavier, and higher-concurrency workloads | Larger SQL/search workloads, many users, or broader server consolidation |
|
16 GB RAM can still constrain very large AI or enterprise workloads | 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 ZTnet need?
Upstream does not publish a numerical whole-host RAM minimum.
How many CPU cores does ZTnet need?
No numerical official CPU minimum is published.
Is the ZimaOS 256 MB value an official ZTnet minimum?
No. It is ZimaOS catalog metadata, not an upstream ZTnet hardware requirement.
What does ZTnet manage?
It provides a self-hosted ZeroTier controller web UI with multi-user and organization support.
Does containerized ZeroTier need special privileges?
ZeroTier's Docker guidance can require network capabilities and access to /dev/net/tun.
Can ZimaBoard 2 832 run ZTnet?
Yes for a small controller workload.
Does ZTnet need a GPU?
No.
When should I use larger Zima hardware?
When network/member count or the wider networking stack creates real CPU/RAM pressure.
![Unifi-controller [legacy]](http://shop.zimaspace.com/cdn/shop/files/Unifi-controller_legacy.webp?v=1790688426&width=1000)
