A small Monica installation can stay modest, but MariaDB, reverse proxy, backup jobs and other ZimaOS apps consume additional memory. Upgrade when the combined host approaches its RAM ceiling or begins swapping.
For users consolidating Monica with many other always-on self-hosted services.Requisitos de hardware de Monica: RAM, CPU, almacenamiento y base de datos
Conoce los requisitos de hardware de Monica para la RAM, la CPU, MariaDB, el almacenamiento persistente, Docker, las cargas de archivos y el hardware de ZimaOS.
Monica hardware requirements at a glance
Monica is a lightweight self-hosted Personal Relationship Management web application backed by a database. Current upstream documentation does not publish one universal CPU, RAM or disk-capacity minimum for production self-hosting, so hardware should be sized from the application, MariaDB/MySQL, uploads, backups and other services sharing the host.
- CPU
- Monica publishes no universal current production CPU minimum. Normal contact management, notes, reminders and web requests are light. The supplied 2018 Alibaba Cloud tutorial used one CPU core, but that was an old Ubuntu 16.04/PHP 7.2 deployment example rather than a current upstream minimum.
- RAM
- There is no universal current Monica RAM minimum. The current ZimaOS package limits/reserves 256 MB for the Monica application container and reserves 256 MB for its MariaDB container, but those are package-level container settings rather than a whole-server RAM requirement.
- Database
- The current official Monica Docker image requires an external MySQL or MariaDB database. ZimaOS currently deploys Monica 4.1.2 together with MariaDB 11.8.2 and persists the database under the Monica AppData path.
- Storage
- Keep both Monica application storage and MariaDB data on persistent local storage. Capacity grows with contact records, uploaded photos/documents, database history, logs and backups rather than with the application image alone.
- GPU
- Monica does not require a GPU. It is a Laravel/PHP personal CRM and does not perform video transcoding, local model inference or another accelerator-dependent workload.
- Best Zima starting point
- ZimaBoard 2 832 is already far above the current ZimaOS Monica container reservations and is the natural starting point for Monica plus other lightweight home-server apps. Choose 1664 only when a larger multi-app stack needs more RAM; ZimaCube 2 is mainly for broader storage and NAS requirements.
From official requirements to the right setup
Monica sizing starts by separating Monica itself from its database, then checks uploads, persistent data, backups, users and the rest of the ZimaOS stack.
-
Official requirements
Use current Monica/ZimaOS packaging as the baseline rather than old tutorials. The ZimaOS package currently runs Monica 4.1.2 with a separate MariaDB 11.8.2 service.
-
Confirm your needs
Treat application RAM and database RAM separately. The ZimaOS manifest gives the Monica app a 256 MB limit/reservation and MariaDB a 256 MB reservation, but MariaDB, Docker, ZimaOS and other apps still need additional host memory.
-
Leave room to grow
Keep Monica's /var/www/html/storage directory and MariaDB /var/lib/mysql data persistent. Plan space for uploaded photos/documents and backups rather than relying only on container-image size.
-
Run it on ZimaOS
Test actual contact imports, attachment uploads, searches and reminder activity while monitoring app RAM, MariaDB RAM, CPU and storage latency. Upgrade the whole server only when measured workload or other applications justify it.
Check every playback client
- Current Monica/ZimaOS package version
- Number of Monica users and contact records
- Uploaded photos and document volume
- MariaDB database size and backup retention
- Persistent app storage for /var/www/html/storage
- Persistent MariaDB storage for /var/lib/mysql
- Reverse proxy, email/reminder and backup services
- Other ZimaOS containers sharing CPU and RAM
Official minimum requirements
Current Monica upstream documentation describes the application stack and development/runtime dependencies but does not publish a universal production CPU/RAM/disk minimum. The ZimaOS manifest provides concrete package resource settings that should remain clearly distinguished from upstream hardware requirements.
Do not publish 1 core/1.5 GB from the 2018 Alibaba tutorial as the current Monica minimum, and do not turn ZimaOS's 256 MB container settings into a universal whole-server minimum. For a current ZimaOS deployment, size the host for Monica + MariaDB + Docker/ZimaOS + backups + any co-hosted applications.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Upstream CPU minimum | No universal current production minimum published | The current Monica documentation and stable project branch describe software dependencies rather than a fixed production processor requirement. |
| Upstream RAM minimum | No universal current production minimum published | No current Monica source establishes a single whole-server RAM floor for every self-hosted deployment. |
| Stable 4.x PHP | PHP 8.1+ | The current stable 4.x branch composer configuration requires PHP ^8.1. This is a software prerequisite, not a RAM/CPU recommendation. |
| ZimaOS Monica container | 256 MB memory limit and 256 MB reservation | The current ZimaOS manifest applies these values specifically to the Monica application container. |
| ZimaOS MariaDB container | 256 MB memory reservation | The current ZimaOS manifest reserves 256 MB for MariaDB but does not set a matching 256 MB hard limit in the shown configuration. |
| ZimaOS package architecture | amd64 and arm64 | The current ZimaOS manifest lists both architectures and categorizes Monica under Social. |
When to upgrade your hardware
Monica itself is light. Upgrade hardware when the database, attachments, backups or wider home-server stack—not a generic CRM label—creates sustained resource pressure.
MariaDB and other apps create sustained memory pressure
Attachment and backup storage outgrows the system disk
The home server is becoming a broader NAS or application platform
Photos, documents, database backups and container data can grow far beyond the Monica code footprint. Add SSD/HDD capacity when persistent AppData and backups begin consuming meaningful storage.
For long-running personal archives with many uploaded files and retained backups.If Monica shares the machine with Nextcloud, media apps, databases, automation or many Docker services, CPU, RAM and storage requirements should be sized from that combined stack.
For users moving from one personal CRM to an all-in-one home server.Plan hardware growth with confidence
Monica grows cleanly when application data, database data, uploads and backups are treated as separate persistent resources.
Keep Monica and MariaDB data persistent
The current ZimaOS package binds Monica storage and MariaDB data into AppData directories. Preserve both in the backup plan; recreating only the application container does not restore the database or uploaded content.
Use reliable local SSD storage for the active Monica and MariaDB AppData.Add SSD capacity before buying more CPU
For typical Monica workloads, database responsiveness and safe persistent storage matter more than a large processor. SSD capacity also leaves room for Docker images, logs and backups.
Add SATA/NVMe SSD to ZimaBoard 2 when onboard storage becomes tight.Add RAM for the whole multi-app stack
Moving from 8 GB to 16 GB is useful when Monica is only one of many containers or when databases and caches consume more memory. It is not evidence that Monica itself requires 16 GB.
Move from ZimaBoard 2 832 to 1664 when measured system-wide memory pressure justifies it.Move to a multi-drive NAS only when storage requires it
A contact-management app does not need six drive bays, but a broader family data platform, backups and document archive might.
Choose ZimaCube 2 when multi-drive storage, redundancy and other NAS workloads independently matter.Can it run on ZimaOS?
Monica is currently available in the ZimaOS App Store under Social. The current package deploys both the Monica web application and its MariaDB database.
Install Monica from the ZimaOS App Store
The current ZimaOS App Store lists Monica as a self-hosted Personal Relationship Management tool for documenting interactions with family and friends.
Open Monica in the ZimaOS App StoreUnderstand the current two-container package
The current manifest uses monica:4.1.2 plus mariadb:11.8.2. The Monica service exposes its web UI and depends on the separate monica-db service.
Review the ZimaOS Monica manifestBack up both application storage and database storage
ZimaOS persists Monica /var/www/html/storage and MariaDB /var/lib/mysql in separate AppData paths. Protect both to preserve contacts, configuration and uploaded content.
Review the official Monica Docker imageChoose Zima hardware for your Monica workload
Monica itself is a lightweight web/database workload. ZimaBoard 2 832 is the default fit; larger Zima hardware is justified by the rest of the home-server stack or storage requirements rather than Monica alone.
Is Monica mainly a personal CRM with a few other apps, or part of a much larger home-server/NAS stack?
Personal Monica and lightweight self-hosting
Start with ZimaBoard 2 832. Its Intel N150 and 8 GB RAM provide very large headroom compared with the current Monica package's container reservations. Choose 1664 only when additional containers make system memory the constraint.
- Monica plus a few lightweight appsZimaBoard 2 832
- Larger Docker stack with more databases/servicesZimaBoard 2 1664
Broader NAS, document archive or many-service home server
Choose ZimaCube 2 for the broader system rather than Monica. Standard fits storage-first use; Pro adds more CPU/RAM/network headroom. Creator Pack has no Monica-specific advantage.
- Storage-first multi-drive home serverZimaCube 2 Standard
- Heavier multi-service NAS and application stackZimaCube 2 Pro
- Only when separate GPU/AI workloads require itZimaCube 2 Creator Pack
This is a workload guide, not a fixed Monica user-count benchmark. Current upstream Monica does not publish one universal CPU/RAM minimum, and ZimaOS container reservations should not be treated as whole-system requirements.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | The best-value current Zima choice for Monica and a small personal self-hosted stack. | Monica, MariaDB, reverse proxy, backup tasks and several lightweight home-server applications. |
|
The 32 GB eMMC is more likely to become limiting than CPU for a growing multi-app host. Use added SSD rather than upgrading the whole server solely for Monica. | Get Now |
| ZimaBoard 2 1664 | A compact Monica host with more memory for databases and many co-hosted applications. | Monica plus larger Docker stacks, multiple databases, automation and additional always-on services. |
|
Do not claim Monica needs 16 GB. The upgrade is justified only by system-wide memory demand. | Get Now |
| ZimaCube 2 Standard | A storage-first home server where Monica is one small service among backups and document/media storage. | Monica, household storage, backups and moderate self-hosted applications. |
|
Eight GB is already plenty for Monica, but Standard should be chosen for storage/NAS needs rather than the CRM workload itself. | Get Now |
| ZimaCube 2 Pro | A larger all-in-one NAS/application server where Monica shares the host with many heavier services. | Many containers, databases, backups, high-capacity storage and broader home-lab workloads. |
|
Do not recommend Pro based on Monica alone. Choose it when other services, storage or networking justify the platform. | Get Now |
| ZimaCube 2 Creator Pack | A Monica-accessible home server already needed for separate GPU, AI or creator workloads. | Monica plus unrelated local AI, GPU compute or creator applications and large storage. |
|
Extreme overkill for Monica. Never recommend Creator Pack for more contacts, users, reminders or attachments alone. | 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
The supplied sources mix Monica Personal CRM with two unrelated products named Monika and Mnemonica. These answers keep those products separate and preserve older Monica deployment figures only as historical evidence.
How much RAM does Monica need?
Current Monica upstream documentation does not publish one universal production RAM minimum. The current ZimaOS package gives the Monica container a 256 MB memory limit/reservation and MariaDB a 256 MB reservation, but those values describe the packaged containers rather than the whole server.
Is 1.5 GB RAM the official Monica minimum?
No. The supplied Alibaba Cloud tutorial from November 2018 required an ECS instance with at least 1.5 GB RAM and one CPU core, but it was written for Ubuntu 16.04, PHP 7.2 and a much older Monica release. It is historical deployment guidance, not a current upstream minimum.
Why does the ZimaOS Monica package use both Monica and MariaDB containers?
Monica is a Laravel web application backed by a relational database. The current ZimaOS manifest deploys monica:4.1.2 together with mariadb:11.8.2 and keeps their application and database storage persistent in separate AppData paths.
Does Monica need a GPU?
No. Monica handles contacts, notes, reminders, diary entries and uploaded files. It does not perform local LLM inference or video transcoding, so there is no dedicated GPU requirement.
Is the Monika Raspberry Pi guide relevant to Monica Personal CRM?
No. The supplied monika.hyperjump.tech page documents Monika by Hyperjump, an open-source monitoring tool that probes services and sends alerts. Its Node.js and Raspberry Pi instructions are for a completely different application.
Are Mnemonica's system requirements relevant to Monica?
No. The supplied support.mnemonica.com article is for Mnemonica, a browser-based media collaboration/service platform. Its browser, mobile OS and screen-resolution requirements have nothing to do with Monica Personal CRM.
What does the Linux Server Admin Monica page contribute?
It is relevant to Monica Personal CRM and describes a normal self-hosted Linux stack with a web server, PHP and MySQL/MariaDB. It does not establish a universal CPU/RAM minimum, so it is useful for architecture and dependencies rather than numeric hardware sizing.
Can ZimaBoard 2 832 run Monica?
Yes. The current ZimaOS package supports amd64, and ZimaBoard 2 832 provides an Intel N150 and 8 GB RAM—far more host memory than the package's Monica and MariaDB reservations. Add SSD storage as AppData, attachments, backups and other services grow.
What sources and further reading informed this Monica hardware guide?
The Monica developer setup page is an official development reference and establishes Monica as a Laravel application, but it is not a production hardware-sizing table. The supplied Monika Hyperjump Raspberry Pi guide is for an unrelated monitoring tool and is excluded from Monica requirements. The Linux Server Admin Monica page is relevant and describes the PHP/web-server/MySQL-or-MariaDB architecture without publishing a universal CPU/RAM floor. The Mnemonica support article belongs to an unrelated service and is excluded. Alibaba Cloud's 2018 Monica tutorial specifies 1 core and 1.5 GB RAM for its Ubuntu 16.04/PHP 7.2 ECS example; because that stack is obsolete relative to current Monica/ZimaOS packaging, the figure is retained only as historical context and not as the current minimum.
