message throughput, mailbox retention, spam/antivirus processing and simultaneous clients Time the job and identify CPU, storage or external-service waits before replacing hardware.
Imports, processing and simultaneous users.Requisitos de hardware de Mox: RAM, CPU, almacenamiento y retención y filtrado del buzón de correo
Planifica la RAM, la CPU, el almacenamiento persistente y las dependencias de los servicios de Mox, con recomendaciones de capacidad de ZimaOS según la carga de trabajo, copias de seguridad y opciones de hardware prácticas.
Mox hardware requirements at a glance
Complete e-mail solution with IMAP4, SMTP, SPF, DKIM, DMARC, MTA-STS, DANE and DNSSEC, reputation-based and content-based junk filtering, Internationalization (IDNA), automatic TLS with ACME and Let's Encrypt, account autoconfiguration, and webmail. The README starting example is a personal mail machine with 512 MB RAM, not a guaranteed mailbox/throughput capacity. DNS, reverse DNS, TLS, public mail-port reachability and recoverable mailbox storage remain essential.
- RAM
- The README describes starting a personal mail machine with 512 MB RAM. This is a starting scope, not a universal mailbox or traffic guarantee.
- CPU
- The same starting guidance does not specify a fixed core count; filtering, sessions and traffic still require measurement.
- Storage
- Mailbox content, message queues, indexes, configuration and recoverable backups determine actual disk needs.
- Required services
- Use the supported upstream runtime and complete service topology for the selected release.
- Main sizing variable
- message throughput, mailbox retention, spam/antivirus processing and simultaneous clients
- Practical Zima starting point
- ZimaBoard 2 832 with SSD-backed active state is an editorial starting point for modest use. Include the OS and all companion services; it is not a measured capacity guarantee.
From official requirements to the right setup
Plan the complete Mox workload before selecting a server.
-
Official requirements
Choose the exact edition, stable release and supported container/runtime. Use the supported upstream runtime and complete service topology for the selected release.
-
Confirm your needs
Test a representative busy operation: message throughput, mailbox retention, spam/antivirus processing and simultaneous clients Record peak resident memory, CPU, disk latency and completion time, including other containers.
-
Leave room to grow
Place active state on reliable persistent storage. Persist mailboxes, queue, domains, credentials, keys, aliases and filtering state. Budget working space for an upgrade or import and test recovery before relying on the deployment.
-
Run it on ZimaOS
Follow the supported upstream runtime, operating system and complete service topology for the selected release. On ZimaOS, consider Custom Install only when a maintained compatible amd64 image and every required host capability have been verified. Otherwise use a separately supported Linux environment; this guide does not certify an unverified container deployment. The README starting example is a personal mail machine with 512 MB RAM, not a guaranteed mailbox/throughput capacity. DNS, reverse DNS, TLS, public mail-port reachability and recoverable mailbox storage remain essential.
Check every playback client
- Exact edition and stable release
- Supported upstream runtime and architecture
- All required companion services
- Realistic peak activity
- Persistent data and file ownership
- Free host ports and reachable URLs
- Working space and backup retention
- Successful database/file restore
Official minimum requirements
Reviewed November 2, 2026 against the linked upstream deployment documentation. Numerical values retain their stated minimum, recommendation or example scope; select release-compatible instructions before installation.
The README starting example is a personal mail machine with 512 MB RAM, not a guaranteed mailbox/throughput capacity. DNS, reverse DNS, TLS, public mail-port reachability and recoverable mailbox storage remain essential. Numerical examples above retain their stated deployment scope; co-hosted services and independent backups need additional capacity.
| Requirement | Official minimum | What this supports |
|---|---|---|
| RAM guidance | The README describes starting a personal mail machine with 512 MB RAM. This is a starting scope, not a universal mailbox or traffic guarantee. | Official guidance keeps its original test, recommendation or example scope. |
| CPU guidance | The same starting guidance does not specify a fixed core count; filtering, sessions and traffic still require measurement. | Core counts do not predict a fixed user, device or document capacity. |
| Storage planning | Mailbox content, message queues, indexes, configuration and recoverable backups determine actual disk needs. | Installation space is separate from retained content, working files and backups. |
| Service topology | Use the supported upstream runtime and complete service topology for the selected release. | Include every stateful companion service in the host budget. |
| Persistent state | Persist mailboxes, queue, domains, credentials, keys, aliases and filtering state. | An image rebuild or container replacement is not a backup. |
| Deployment boundary | The README starting example is a personal mail machine with 512 MB RAM, not a guaranteed mailbox/throughput capacity. DNS, reverse DNS, TLS, public mail-port reachability and recoverable mailbox storage remain essential. | Check the linked project instructions for the selected edition and release. |
When to upgrade your hardware
Use observed Mox workload pressure to decide when an upgrade is warranted.
Busy operations exceed the available window
The complete stack runs short of memory
Persistent data approaches available capacity
Inspect the application and each required service for OOM events, sustained swap or growing queues. Reduce unnecessary concurrency before adding capacity.
Shared hosts and background work.Persist mailboxes, queue, domains, credentials, keys, aliases and filtering state. Track primary state and backup retention separately.
Long-lived installations and growing collections.Plan hardware growth with confidence
Address storage, memory, compute and deployment limits separately.
Use suitable active storage
Put latency-sensitive application/database state on durable local SSD storage and keep recoverable copies.
SATA or PCIe SSD according to measured data growth.Add memory for the complete stack
Choose a higher-RAM host when peak application and companion-service usage leaves inadequate OS headroom.
ZimaBoard 2 832 or ZimaBoard 2 1664 according to the measured constraint.Separate capacity from compute
A multi-drive system helps when retained content and backup storage are the problem; it is not automatically a faster application.
ZimaCube 2 when a broader multi-drive workload justifies it.Fix the observed bottleneck
The README starting example is a personal mail machine with 512 MB RAM, not a guaranteed mailbox/throughput capacity. DNS, reverse DNS, TLS, public mail-port reachability and recoverable mailbox storage remain essential.
Check service configuration, I/O and network behavior before selecting a stronger CPU.Can it run on ZimaOS?
Follow the supported upstream runtime, operating system and complete service topology for the selected release. On ZimaOS, consider Custom Install only when a maintained compatible amd64 image and every required host capability have been verified. Otherwise use a separately supported Linux environment; this guide does not certify an unverified container deployment.
Verify the supported upstream deployment
The README starting example is a personal mail machine with 512 MB RAM, not a guaranteed mailbox/throughput capacity. DNS, reverse DNS, TLS, public mail-port reachability and recoverable mailbox storage remain essential. Follow the supported upstream runtime, operating system and complete service topology for the selected release. On ZimaOS, consider Custom Install only when a maintained compatible amd64 image and every required host capability have been verified. Otherwise use a separately supported Linux environment; this guide does not certify an unverified container deployment.
Review upstream deployment guidance ↗Use the official Mox deployment instructions
Keep the selected stable release, persistent paths and companion services aligned with upstream documentation.
Review Mox official installation ↗Check workload-specific deployment details
The README starting example is a personal mail machine with 512 MB RAM, not a guaranteed mailbox/throughput capacity. DNS, reverse DNS, TLS, public mail-port reachability and recoverable mailbox storage remain essential.
Review Mox deployment details ↗Which Zima hardware fits Mox?
Start with the lowest reasonable host for the actual workload. Product specifications were checked against the current product pages.
Which workload best matches your Mox deployment?
Modest Mox deployment
Start with durable active data and a measured whole-stack memory budget.
- Workload optionZimaBoard 2 832
Heavier jobs or more companion applications
Choose added memory or compute only when observed peaks justify the change.
- Workload optionZimaBoard 2 1664
These are practical workload recommendations, not official app requirements, compatibility certification, measured capacity limits or performance guarantees. Include all co-hosted services and independent backups.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Modest Mox workload | message throughput, mailbox retention, spam/antivirus processing and simultaneous clients |
|
This is an editorial host choice, not an official app minimum or a guaranteed user/device capacity. | Get Now |
| ZimaBoard 2 1664 | More processing or shared-service headroom | Use the supported upstream runtime and complete service topology for the selected release. |
|
Size the combined stack and active working set; more RAM does not fix remote API limits or missing dependencies. | 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
Answers to Mox RAM, CPU, storage, Docker, database and ZimaOS sizing questions.
How much RAM should I plan for Mox?
The README describes starting a personal mail machine with 512 MB RAM. This is a starting scope, not a universal mailbox or traffic guarantee. Include ZimaOS, the application and its companion services rather than reserving the entire machine for one container.
What drives the CPU requirement?
The same starting guidance does not specify a fixed core count; filtering, sessions and traffic still require measurement. The workload to test is: message throughput, mailbox retention, spam/antivirus processing and simultaneous clients
Which data must survive a container update?
Persist mailboxes, queue, domains, credentials, keys, aliases and filtering state. Preserve a consistent database/file set and verify that your recovery procedure restores a working application.
What other services belong in the budget?
Use the supported upstream runtime and complete service topology for the selected release.
Does this workload need a dedicated GPU?
A dedicated GPU is not assumed for the core workflow described here. Optional AI, acceleration or media-processing integrations must be evaluated separately against the selected backend.
Can I deploy it on ZimaOS?
Follow the supported upstream runtime, operating system and complete service topology for the selected release. On ZimaOS, consider Custom Install only when a maintained compatible amd64 image and every required host capability have been verified. Otherwise use a separately supported Linux environment; this guide does not certify an unverified container deployment. The README starting example is a personal mail machine with 512 MB RAM, not a guaranteed mailbox/throughput capacity. DNS, reverse DNS, TLS, public mail-port reachability and recoverable mailbox storage remain essential.
What should I check before upgrading hardware?
The README starting example is a personal mail machine with 512 MB RAM, not a guaranteed mailbox/throughput capacity. DNS, reverse DNS, TLS, public mail-port reachability and recoverable mailbox storage remain essential. Measure the same representative operation before and after a configuration or hardware change.
Which Zima device is a practical starting point?
ZimaBoard 2 832 is the editorial starting point for this modest deployment. Choose ZimaBoard 2 1664 for measured memory/processing pressure or broader shared services; retained data determines storage expansion.
What sources informed this Mox hardware guide?
This guide was reviewed against the linked project deployment documentation on November 2, 2026. Zima device choices are editorial workload guidance, separate from upstream requirements and measured performance.
