Interactive CRM use and reporting increase PHP/database demand.
Growing sales/support teams.Configuration matérielle requise pour EspoCRM : RAM, processeur et stockage
Plan matériel EspoCRM pour la RAM, le CPU, MariaDB ou PostgreSQL, les services cron/daemon et le stockage, avec des recommandations pratiques pour une installation personnalisée de ZimaOS.
EspoCRM requirements at a glance
EspoCRM publishes current PHP and database requirements plus an official Docker stack, but no universal CPU, RAM or disk minimum. Practical sizing must include the CRM app, database and background daemon.
- RAM
- No numerical official minimum published; app, database and daemon/background jobs share whole-host memory.
- CPU
- No numerical official core minimum; reports, workflows, email sync and imports can increase demand.
- Storage
- No universal official minimum; database, attachments, email files, logs and backups determine capacity.
- PHP
- Current server configuration supports PHP 8.3–8.5.
- Database
- Current supported databases: MySQL 8.0+, MariaDB 10.3+ or PostgreSQL 15.
- Best Zima starting point
- ZimaBoard 2 832 is comfortable for a small CRM; 16 GB or ZimaCube 2 Pro adds headroom.
From official requirements to the right setup
Size EspoCRM from its real service stack and persistent data rather than using a guessed one-size-fits-all server number.
-
Official requirements
Start with current software support: PHP 8.3–8.5 and MySQL 8+, MariaDB 10.3+ or PostgreSQL 15.
-
Confirm your needs
Estimate active users, record count, reports, workflows, email sync and imports.
-
Leave room to grow
Persist database, data/custom/client-custom volumes and back them up; the official Docker setup separates database, app and daemon services.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with EspoCRM's official Compose path and configure HTTPS plus the background daemon.
Check every playback client
- Active users
- Record/contact volume
- Email sync
- Reports/workflows
- Database engine
- Attachment growth
- Daemon/cron workload
- Backup retention
Official minimum requirements
EspoCRM publishes software requirements but no numerical server hardware minimum.
Do not invent a fixed 2 GB or 4 GB official minimum. A practical deployment still needs headroom for the SQL database and daemon.
| Requirement | Official minimum | What this supports |
|---|---|---|
| RAM minimum | No numerical official minimum published | Depends on app, database and background services. |
| CPU minimum | No numerical official minimum published | Concurrency, reports, email and workflows influence demand. |
| Storage minimum | No numerical official minimum published | Database, attachments and backups determine capacity. |
| PHP | PHP 8.3–8.5 | Current server configuration support. |
| MySQL / MariaDB | MySQL 8.0+ / MariaDB 10.3+ | Current supported versions. |
| PostgreSQL | PostgreSQL 15 | Current documented support. |
When to upgrade your hardware
Upgrade EspoCRM when measured workload, storage growth or background processing outgrows the current host.
More concurrent users and reports
Email sync and workflows expand
Attachments and history grow
Background daemon tasks create sustained work even when the UI is quiet.
Automation-heavy installations.Files, email attachments and backups can dominate storage.
Long-running CRM systems.Plan hardware growth with confidence
Scale EspoCRM by addressing the actual bottleneck—database, storage, processing or concurrency—before simply buying a larger server.
Use SSD-backed database storage
CRM responsiveness depends heavily on database latency.
SATA/NVMe on ZimaBoard 2 or SSD tiers on ZimaCube 2.Move to 16 GB for automation/database cache
Extra RAM helps PHP, database and daemon jobs coexist.
ZimaBoard 2 1664.Use larger storage for attachments/backups
Customer files and emails can grow significantly.
ZimaCube 2 Standard.Use stronger CPU for reports/workflows
Heavier reports and automation benefit from more CPU.
ZimaCube 2 Pro.Can it run on ZimaOS?
EspoCRM is not currently confirmed as a public official one-click ZimaOS App Store page in the sources checked for this guide. It can still be deployed through Install Custom App.
Custom install EspoCRM in ZimaOS
Use Install Custom App with the official EspoCRM Docker Compose pattern, persist app/database volumes and run the daemon container.
Custom install EspoCRM in the ZimaOS app ↗Use EspoCRM's official Docker image
EspoCRM maintains an official Docker image and recommends Docker Compose for production-style management.
Review EspoCRM Docker installation ↗Match current PHP/database requirements
Current support is PHP 8.3–8.5 with MySQL 8+, MariaDB 10.3+ or PostgreSQL 15.
Review EspoCRM server configuration ↗Choose Zima hardware for EspoCRM
Choose Zima hardware for the complete EspoCRM workload, including its database, storage and background services.
Is this a small CRM or a heavier automation/reporting deployment?
Small team / light automation
Use ZimaBoard 2 with SSD-backed SQL storage.
- Best starting pointZimaBoard 2 832
- More headroomZimaBoard 2 1664
More workflows, reporting and attachments
Use stronger CPU/storage expansion.
- Higher-headroom platformZimaCube 2 Pro
These are practical workload recommendations, not official throughput or user-count guarantees.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Small EspoCRM teams. | EspoCRM, MariaDB/PostgreSQL, daemon and normal CRM activity. |
|
Add SSD-backed SQL storage. | Get Now |
| ZimaBoard 2 1664 | More email, workflows and co-hosted apps. | Larger DB cache, daemon/background jobs and business services. |
|
16 GB is host headroom, not an official minimum. | Get Now |
| ZimaCube 2 Pro | Heavier reports, workflows and broader consolidation. | EspoCRM, larger SQL workload, automation and other business containers. |
|
Large organizations may still benefit from separated database/app infrastructure. | 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 cover EspoCRM RAM, CPU, storage, Docker and ZimaOS deployment.
How much RAM does EspoCRM need?
EspoCRM does not publish a numerical official server RAM minimum.
How many CPU cores does EspoCRM need?
There is no numerical official core minimum.
Which PHP version does EspoCRM support?
Current documentation lists PHP 8.3 through 8.5.
Which databases does EspoCRM support?
MySQL 8.0+, MariaDB 10.3+ and PostgreSQL 15.
How much storage does EspoCRM need?
No universal official disk minimum; database, attachments and backups determine capacity.
Does EspoCRM need a GPU?
No dedicated GPU is required.
Can ZimaBoard 2 run EspoCRM?
Yes. The 8 GB model is a comfortable small-team starting point with durable SQL storage.
Does EspoCRM have an official Docker image?
Yes. EspoCRM maintains an official Docker image and Docker Compose documentation.
What sources informed this EspoCRM hardware guide?
Current EspoCRM server configuration and official Docker docs plus current Zima product pages.
