Wymagania sprzętowe Erxes: RAM, procesor, pamięć masowa, MongoDB i Redis CRM
Zaplanuj sprzęt Erxes pod kątem pamięci RAM, CPU, zestawów replik MongoDB, Redis, wtyczek, przesyłania plików i praktycznych zaleceń dotyczących wdrożenia ZimaOS.
Erxes hardware requirements at a glance
Size Erxes from verified upstream requirements first, then add headroom for workload and persistent data.
- RAM
- No tested current official minimum published
- CPU
- No tested current official minimum published
- Storage
- No tested current official minimum published
- Database
- MongoDB replica set required
- Cache/queues
- Redis required and should be persistent with noeviction
- Best Zima starting point
- ZimaCube 2 Pro for a small serious deployment
From official requirements to the right setup
Start with current upstream facts for Erxes, then size the real 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
- Concurrent users
- MongoDB workload
- Plugin count
- Redis queues
- Uploads
- Automations
- Logs retention
- Backup/replica-set design
Official minimum requirements
Current Erxes deployment documentation explicitly says the repository does not establish a tested minimum CPU, RAM, or disk size.
Older Erxes documentation published fixed figures such as 2 GB RAM or 4-core/8 GB examples, but the current deployment guide supersedes that approach and instructs operators to budget the whole stack and measure staging.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No tested minimum published | Budget all Node services, Redis, and DB workload. | |
| No tested minimum published | Measure a staging deployment. | |
| x86-64 Linux for core published images | Most core images are amd64. | |
| MongoDB replica set required | Plugins use sessions/transactions. | |
| Persistent Redis required | Used for queues, sessions, service discovery. | |
| Nginx + HTTPS | Reference deployment publishes UI/gateway on loopback. | |
| Not required | No GPU baseline. |
When to upgrade your hardware
Plugin/service growth
MongoDB pressure
Automation/upload growth
Plan hardware growth with confidence
Fast DB/storage
Use SSD/NVMe for MongoDB and app state.
SSD/NVMeMore RAM
Useful for the multi-service stack and MongoDB/Redis.
16 GB+Separate MongoDB
Move DB to dedicated/managed nodes as scale grows.
Dedicated DBStronger CPU
Useful for plugins, automations, gateway, and workers.
ZimaCube 2 Pro or strongerCan it run on ZimaOS?
Custom install Erxes in ZimaOS
No specific public ZimaOS Erxes per-app page was verified, so use Custom Install.
Custom install Erxes in the ZimaOS app ↗Follow current self-hosting docs, not legacy minima
Current docs explicitly state no tested CPU/RAM/disk minimum.
Open Erxes self-hosting docs ↗Provision MongoDB replica set separately
The reference Compose stack manages Redis and Erxes services but not MongoDB.
Open Erxes operations overview ↗Zima hardware for Erxes
Erxes is a multi-service CRM/experience platform, so a fixed home-server minimum would be misleading.
Choose by workload
Use a strong single host and a properly configured MongoDB replica set.
Separate stateful services and scale based on observed bottlenecks.
Use current docs over older legacy deployment pages when values conflict.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaCube 2 Pro | CPU-heavier, database-heavy, and higher-concurrency services | Larger CRM/helpdesk/mail/platform workloads |
|
16 GB RAM can still be low for large enterprise stacks | 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
What is Erxes's current official RAM minimum?
The current self-hosting docs state that no tested minimum has been established.
Does Erxes require MongoDB?
Yes, a MongoDB replica set.
Does Erxes require Redis?
Yes; Redis is used for queues, sessions, plugin lists, and service discovery.
Do older Erxes docs list hardware numbers?
Yes, but current self-hosting guidance no longer establishes a tested fixed minimum.
Can a single-node MongoDB replica set work?
Yes for evaluation, but it provides no redundancy.
Can ZimaCube 2 Pro run a small Erxes deployment?
It is a reasonable lab/small-deployment starting point, but production should be validated with staging metrics.
Does Erxes need a GPU?
No baseline GPU requirement is published.
When should MongoDB move off-host?
When database memory, I/O, availability, or backup needs justify separate nodes.
