More realtime connections increase Node.js, Deno Apps Engine and MongoDB activity.
Growing teams and public communities.Hardwarevereisten voor Rocket.Chat: RAM, CPU, MongoDB en opslag
Plan Rocket.Chat-hardware voor CPU, RAM, MongoDB, uploads en gelijktijdige gebruikers, met praktische aanbevelingen voor aangepaste installatie op ZimaOS.
Rocket.Chat requirements at a glance
Rocket.Chat is a collaboration platform whose sizing depends heavily on concurrent users and the MongoDB topology.
- Starter app tier
- For up to 500 concurrent users, Rocket.Chat publishes 2 vCPU, 4 GiB RAM and 20 GiB storage for the Rocket.Chat application tier.
- MongoDB tier
- The same Starter reference budgets 2 vCPU, 4 GiB RAM and 10 GiB storage for MongoDB; high availability uses multiple MongoDB replicas.
- Current database version
- Rocket.Chat 8.x requires MongoDB 8.0 or newer; current 8.8 docs say it is verified with MongoDB 8.2.
- CPU clocks
- The Starter table references roughly 3.5–5.0 GHz for Rocket.Chat and 3.0 GHz for MongoDB, so low-power CPUs may hit CPU limits before RAM.
- File storage
- Rocket.Chat recommends object storage such as S3, GCS or MinIO for uploads at scale.
- Best Zima starting point
- ZimaBoard 2 1664 is the safer compact single-host option for small teams; ZimaCube 2 Pro is better when concurrency and MongoDB load grow.
From official requirements to the right setup
Size Rocket.Chat and MongoDB as separate services even when both run on one Zima host.
-
Official requirements
Choose the expected concurrent-user tier. The current Starter reference for up to 500 concurrent users assigns 2 vCPU/4 GiB/20 GiB to Rocket.Chat and 2 vCPU/4 GiB/10 GiB to MongoDB.
-
Confirm your needs
Use a supported MongoDB 8.x release. Do not size only the Rocket.Chat container; database cache, indexes and replica topology are a separate resource layer.
-
Leave room to grow
Plan persistent MongoDB data plus file uploads. For larger deployments, move uploads to object storage rather than growing the application filesystem indefinitely.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with Rocket.Chat's official Docker Compose deployment, persist MongoDB data, configure a domain, and keep enough RAM/CPU headroom for both services.
Check every playback client
- Concurrent users
- MongoDB 8.x
- MongoDB replicas
- Upload storage
- Domain/HTTPS
- CPU clock/headroom
- Backup retention
- Other ZimaOS services
Official minimum requirements
Rocket.Chat publishes deployment scenarios rather than one universal server minimum.
For small single-host deployments, do not collapse the Rocket.Chat and MongoDB rows into a misleading one-container minimum. Both tiers need resources and MongoDB becomes increasingly important as concurrency grows.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Starter Rocket.Chat CPU | 2 vCPU | Up to 500 concurrent users. |
| Starter Rocket.Chat RAM | 4 GiB | Up to 500 concurrent users. |
| Starter Rocket.Chat storage | 20 GiB | Application-tier reference. |
| Starter MongoDB CPU/RAM | 2 vCPU / 4 GiB | Database-tier reference. |
| Starter MongoDB storage | 10 GiB | Database-tier reference; real history may require more. |
| MongoDB version | 8.0+ | Rocket.Chat 8.x requirement; 8.8 is verified with MongoDB 8.2. |
| >5,000 concurrent users | Microservices on Kubernetes | Current docs move very large deployments to a different architecture. |
When to upgrade your hardware
Rocket.Chat should scale when concurrency, MongoDB working set or uploads exceed the compact single-host profile.
Concurrent users approach hundreds
MongoDB cache and indexes become memory-bound
Uploads and media grow
Database history, search and active working set can consume more RAM than the app tier itself.
Long-running workspaces.Local file storage can become a capacity and backup bottleneck; object storage is the scalable path.
File-heavy collaboration.Plan hardware growth with confidence
Scale Rocket.Chat by giving MongoDB memory/storage headroom and moving heavier workloads off the smallest host.
Use 16 GB for a compact all-in-one deployment
This leaves more practical room for the app, MongoDB and OS than an 8 GB host.
ZimaBoard 2 1664.Use SSD-backed MongoDB storage
Low-latency durable storage benefits MongoDB indexes, journals and backups.
Use SATA/NVMe with ZimaBoard 2 or SSD tiers on ZimaCube 2.Move to stronger CPU for larger concurrency
Rocket.Chat's published CPU clock references are relatively high for the Starter tier.
ZimaCube 2 Pro.Use object storage for large uploads
Keep media growth from competing with MongoDB and application storage.
ZimaCube storage or an external S3-compatible service such as MinIO.Can it run on ZimaOS?
A ZimaOS community discussion shows Rocket.Chat has existed as an app in the ecosystem, but no current public official one-click App Store detail page was verified for this guide. Use the Custom Install route unless a concrete current listing is confirmed at publish time.
Custom install Rocket.Chat in ZimaOS
Use Install Custom App with Rocket.Chat's official Docker Compose configuration, persist MongoDB data, configure a production domain, and size both app and database services.
Custom install Rocket.Chat in the ZimaOS app ↗Use Rocket.Chat's official Docker Compose method
The current guide requires Docker, Docker Compose v2 and Git and points back to the current system requirements.
Review Rocket.Chat Docker deployment ↗Verify current MongoDB compatibility
Rocket.Chat 8.x requires MongoDB 8.0+ and release-specific compatibility should be checked before upgrades.
Review Rocket.Chat system requirements ↗Choose Zima hardware for Rocket.Chat
Rocket.Chat's published Starter profile makes 16 GB the safer compact all-in-one target once MongoDB and OS headroom are included.
Is this a small single-host workspace or a larger realtime collaboration workload?
Small team / single host
Use 16 GB with SSD-backed MongoDB rather than squeezing both app and DB into 8 GB.
- Best compact choiceZimaBoard 2 1664
More users, heavier MongoDB or larger uploads
Use stronger CPU and expandable SSD/storage.
- Higher-headroom platformZimaCube 2 Pro
- Storage-first alternativeZimaCube 2 Standard
These mappings are for small single-host deployments and do not reproduce Rocket.Chat's HA reference architectures.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 1664 | Small single-host Rocket.Chat workspaces. | Rocket.Chat plus MongoDB with moderate concurrency and uploads. |
|
The N150's low-power CPU can become the first limit as realtime concurrency grows. | Get Now |
| ZimaCube 2 Pro | Larger single-host Rocket.Chat deployments. | More realtime users, heavier MongoDB, uploads and co-hosted services. |
|
A single physical host still does not provide Rocket.Chat's recommended HA topology. | Get Now |
| ZimaCube 2 Standard | Storage-oriented Rocket.Chat deployments. | Larger local uploads and backups with moderate app load. |
|
8 GB RAM is tighter for combined Rocket.Chat + MongoDB than the 16 GB options. | 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 Rocket.Chat RAM, CPU, MongoDB, uploads and ZimaOS deployment.
How much RAM does Rocket.Chat need?
For a Starter deployment up to 500 concurrent users, current docs allocate 4 GiB to the Rocket.Chat tier and 4 GiB to MongoDB as separate resources.
How many CPU cores does Rocket.Chat need?
The Starter reference allocates 2 vCPU to Rocket.Chat and 2 vCPU to MongoDB.
Which MongoDB version does Rocket.Chat require?
Rocket.Chat 8.x requires MongoDB 8.0 or newer; current 8.8 documentation says MongoDB 8.2 is verified.
How much storage does Rocket.Chat need?
The Starter reference lists 20 GiB for Rocket.Chat and 10 GiB for MongoDB, but uploads and message history can require much more.
Should Rocket.Chat uploads stay on local disk?
For larger deployments, Rocket.Chat recommends object storage such as S3, GCS or MinIO.
Does Rocket.Chat need a GPU?
No dedicated GPU is part of the standard Rocket.Chat hardware requirements.
Can ZimaBoard 2 run Rocket.Chat?
Yes. The 16 GB model is the safer compact option for running both Rocket.Chat and MongoDB on one host.
When should I choose ZimaCube 2 Pro?
When realtime concurrency, MongoDB activity or broader service consolidation makes stronger CPU and storage useful.
What sources informed this Rocket.Chat hardware guide?
Current Rocket.Chat system requirements and Docker deployment documentation plus current Zima product pages.
