Pageviews, events and downloads all add load. Crossing from the 100K class toward 1M moves the official recommendation from 2 CPU/2 GB/50 GB SSD to 4 CPU/8 GB/250 GB SSD.
Sites with growing traffic or more tracked properties.متطلبات أجهزة Matomo: وحدة المعالجة المركزية، وذاكرة الوصول العشوائي، وSSD وحركة المرور
حدّد متطلبات Matomo On-Premise من حيث المعالج وذاكرة RAM وSSD وMySQL أو MariaDB وحركة المرور الشهرية، مع توصيات عملية للتثبيت المخصص على ZimaOS بدءًا من 100 ألف إلى مليون مشاهدة للصفحات.
Matomo requirements at a glance
Matomo On-Premise sizes primarily by monthly tracked actions/pageviews. The official recommendations start at 2 CPU, 2 GB RAM and 50 GB SSD for up to 100,000 pageviews per month, then increase to 4 CPU, 8 GB RAM and 250 GB SSD for up to 1 million.
- Up to 100K pageviews/month
- Official recommendation: 2 CPU, 2 GB RAM, 50 GB SSD on one server for app plus database.
- Up to 1M pageviews/month
- Official recommendation: 4 CPU, 8 GB RAM, 250 GB SSD; one server can still be sufficient.
- Above 1M actions/month
- Matomo generally recommends separating the database and app/report-processing roles rather than only scaling one box.
- Database
- Current Matomo 6 requirements use MySQL 8.0+ or MariaDB 10.6+ with PHP 8.1+.
- GPU
- No GPU is required for standard Matomo tracking, reporting or archiving workloads.
- Best Zima starting point
- ZimaBoard 2 832 with an added 50–250 GB+ SSD suits small analytics; ZimaCube 2 Standard aligns closely with Matomo's 1M-pageview memory/storage class, but traffic and archive jobs still need monitoring.
From official requirements to the right setup
Matomo sizing should start with tracked actions per month, then account for sites, segments, archive frequency, database growth and backup retention.
-
Official requirements
Map monthly tracked actions to Matomo's official tiers. Use 2 CPU/2 GB/50 GB SSD for up to 100K pageviews and 4 CPU/8 GB/250 GB SSD for up to 1M as starting recommendations, not guaranteed throughput.
-
Confirm your needs
Count more than pageviews. Events, downloads and other tracked actions add to the request volume, while more websites and segments increase report-processing work.
-
Leave room to grow
Plan database and archive storage growth. Matomo stores analytics in MySQL/MariaDB, and archive/report processing benefits from RAM and SSD-backed I/O.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with the official Matomo Docker setup. Persist the database and Matomo config/data, add cron archiving for medium/high traffic, and monitor database CPU, archive duration and free SSD space before moving to a larger tier.
Check every playback client
- Monthly tracked pageviews/actions
- Number of tracked websites
- Number of custom segments
- Archive frequency and cron setup
- MySQL or MariaDB persistence
- SSD capacity for database growth
- Backup retention and restore plan
- Other ZimaOS apps sharing the host
Official minimum requirements
Matomo publishes traffic-based server sizing rather than one universal host minimum. The figures below are official recommended configurations for specific monthly traffic classes.
Use the smallest 2 CPU/2 GB/50 GB SSD tier only for up to roughly 100,000 monthly pageviews/actions. At 1 million per month, the official recommendation rises to 4 CPU/8 GB/250 GB SSD, and beyond that Matomo increasingly recommends separate application and database servers.
| Requirement | Official minimum | What this supports |
|---|---|---|
| ≤100K pageviews/month | 2 CPU, 2 GB RAM, 50 GB SSD | One server is sufficient for both application and database in Matomo's official sizing guidance. |
| ≤1M pageviews/month | 4 CPU, 8 GB RAM, 250 GB SSD | One server can still be sufficient, but database and report-processing demand is much higher. |
| ≤10M pageviews/month | Two servers recommended | Matomo recommends a separate app tier and database tier at this scale; a single home-server box should not be presented as equivalent. |
| PHP | PHP 8.1+ for Matomo 6 | Current Matomo 6 system requirement. |
| Database | MySQL 8.0+ or MariaDB 10.6+ | Current Matomo 6 requirement. |
| Storage type | SSD in official server-sizing tiers | Matomo's published traffic tiers explicitly use SSD-backed server configurations. |
When to upgrade your hardware
Matomo should scale when monthly tracked actions, archive processing or database resource use moves beyond the official tier you selected.
Tracked actions approach the next official tier
Archive jobs fall behind schedule
Database CPU or SSD usage stays high
Matomo recommends CLI/cron archiving for medium and high traffic. Slow archive completion is a sign that CPU, memory or database I/O needs more headroom.
Analytics instances with many segments, sites or reports.Matomo is database-heavy. Sustained database CPU pressure, slow reports or rapidly growing tables are stronger upgrade signals than the PHP app container alone.
Long-running installations with high event volume and retention.Plan hardware growth with confidence
Scale Matomo in the order its own architecture suggests: protect SSD-backed database performance, automate archiving, then separate the app and database roles as traffic grows.
Use SSD-backed database storage
Matomo's own server-sizing tiers specify SSD storage, and database/report workloads benefit from predictable I/O.
Add a 50–250 GB+ SSD to ZimaBoard 2 or use ZimaCube 2 SSD storage rather than depending on onboard eMMC.Automate report archiving with cron
Medium/high traffic deployments should not rely on browser-triggered archiving. CLI archiving reduces unpredictable request-time work and makes bottlenecks easier to observe.
No special hardware is required, but CPU and RAM headroom help archive jobs finish within schedule.Move to 8 GB / 4-core-class resources near 1M actions
Matomo's official ≤1M tier uses 4 CPU and 8 GB RAM, so this is a natural point to move beyond very small hosts.
ZimaBoard 2 832 or ZimaCube 2 Standard can match the memory/core class when paired with appropriate SSD capacity.Split app and database beyond 1M actions
Matomo generally recommends separate application/report and database servers after 1M actions rather than endlessly scaling one box.
Use separate systems or external database infrastructure once traffic clearly exceeds the single-server tier.Can it run on ZimaOS?
Matomo is not currently presented in the public ZimaOS hardware catalog as a one-click ZimaOS App Store app. It can still be deployed through Install Custom App using Matomo's official Docker image and a separate MySQL/MariaDB service.
Custom install Matomo in ZimaOS
Use Install Custom App with a multi-container Compose setup for Matomo plus MySQL or MariaDB. Persist the Matomo config and database volumes, set database credentials, expose the web port through HTTPS, and configure cron archiving for production analytics.
Custom install Matomo in the ZimaOS app ↗Use Matomo's recommended multi-container Docker layout
Matomo's Docker guide recommends a multi-container setup for most use cases, separating the application and required database/archiving services rather than treating one test container as production.
Review Matomo Docker installation ↗Size by actions per month, not account count
Matomo explicitly ties server sizing to tracked requests per month, number of websites and segments. This is the correct basis for deciding whether a Zima host is still appropriate.
Review Matomo capacity planning ↗Choose Zima hardware for Matomo
Matomo maps cleanly to traffic tiers: small sites fit ZimaBoard 2 with added SSD, while the 1M-pageview class aligns more closely with 8 GB RAM, 4-core-class CPU and 250 GB SSD capacity.
Are you tracking up to about 100K actions per month, or approaching the 1M-action single-server tier?
Up to roughly 100K pageviews/actions per month
A ZimaBoard 2 has ample RAM/CPU over Matomo's 2 CPU/2 GB recommendation; add at least 50 GB of SSD-backed persistent storage.
- Best compact starting pointZimaBoard 2 832
Approaching roughly 1M pageviews/actions per month
Target at least the 4 CPU/8 GB/250 GB SSD class and watch archive/database behavior carefully.
- Integrated storage platformZimaCube 2 Standard
- More CPU headroomZimaCube 2 Pro
These recommendations use Matomo's official traffic tiers as a starting point, not a guaranteed pageview ceiling. Events, downloads, number of sites, segments, retention, archive frequency and other ZimaOS workloads can change resource use.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Matomo installations in the small-traffic tier with an added SSD. | Up to roughly 100K monthly pageviews/actions, one database, cron archiving and a few other light ZimaOS services. |
|
Matomo's official ≤100K tier calls for 50 GB SSD, so add SSD storage; the 32 GB eMMC does not satisfy that published storage recommendation by itself. | Get Now |
| ZimaCube 2 Standard | Matomo near the 1M-pageview single-server tier with integrated storage expansion. | Matomo app plus database, archive processing and roughly 250 GB SSD-class active storage. |
|
This is close to Matomo's 4 CPU/8 GB/250 GB SSD class on paper, but traffic shape, archive load and database I/O must still be measured; >1M actions generally points toward split servers. | Get Now |
| ZimaCube 2 Pro | Matomo with heavier archive/database CPU demand or additional analytics services. | Higher sustained tracking load, more segments, reports, databases and co-hosted services while remaining within a single-server design. |
|
A stronger single box does not replace Matomo's multi-server recommendation at higher traffic tiers; split app and database roles when the workload crosses that architectural boundary. | 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 Matomo CPU, RAM, SSD, database and traffic tiers using Matomo's own monthly-action sizing guidance.
How much RAM does Matomo need?
Matomo sizes RAM by monthly tracked actions. Up to 100,000 pageviews per month, it recommends 2 GB RAM. Up to 1 million, it recommends 8 GB RAM. Larger deployments move to multi-server designs with more memory.
How many CPU cores does Matomo need?
Matomo recommends 2 CPU for up to 100,000 monthly pageviews and 4 CPU for up to 1 million. At around 10 million monthly pageviews, its documented architecture uses separate application and database servers with larger CPU allocations.
How much storage does Matomo need?
The official tiers use 50 GB SSD for up to 100,000 pageviews and 250 GB SSD for up to 1 million. Database retention, more sites and longer analytics history can increase real storage needs beyond those starting recommendations.
Does Matomo require MySQL or MariaDB?
Yes. Current Matomo 6 requirements specify MySQL 8.0+ or MariaDB 10.6+ and PHP 8.1+.
Does Matomo need an SSD?
Matomo's published server-sizing tiers explicitly use SSD storage. Analytics is database-heavy, so SSD-backed MySQL/MariaDB storage is the practical baseline for predictable reporting and archive performance.
Does Matomo need a GPU?
No. Standard Matomo tracking, reporting and archiving do not require GPU acceleration. CPU, RAM, database I/O and SSD capacity are the relevant hardware dimensions.
Can ZimaBoard 2 run Matomo?
Yes for small analytics workloads. Its 4-core Intel N150 and 8 GB RAM exceed Matomo's ≤100K monthly tier, but you should add at least 50 GB of SSD-backed storage because the onboard 32 GB eMMC alone does not meet Matomo's published storage recommendation.
When should Matomo move beyond one server?
Matomo says that above about 1 million user actions per month, it generally recommends at least two servers: one for the database and one for tracking/API/UI/report processing.
What sources informed this Matomo hardware guide?
The guide uses Matomo's current On-Premise requirements, capacity-planning and Docker documentation for official sizing and deployment claims. Current Zima product pages are used only for Zima hardware specifications.
