This document provides an overview of the system requirements for various Rocket.Chat deployment scenarios. It helps system administrators select the right hardware, storage, and database configurations to ensure a stable and high-performing Rocket.Chat environment.
Requirements vary based on your organization’s size, usage patterns, and deployment method. Regularly review and adjust your specifications as your workspace grows to maintain optimal performance.
For Enterprise or specialized workspaces (e.g. Chat Engine), consult Rocket.Chat Sales for tailored recommendations.
Hardware specifications
The hardware requirements for Rocket.Chat varies depending on the expected user load and workspace plan.
Scenario: Starter or Pro plan - No high availability - Concurrent users ≤ 500 | |||||
|---|---|---|---|---|---|
Hardware resources | vCPU/Cores | CPU Clock Speed (GHz) | Memory (GiB) | Storage (GiB) | Number of MongoDB replicas |
Rocket.Chat | 2 | 3.5 - 5.0 | 4 | 20 | N/A |
MongoDB | 2 | 3.0 | 4 | 10 | 3 |
MongoDB Atlas equivalent(AWS):M30 | |||||
Scenario: Enterprise plan - High availability - Concurrent users ≥ 500 - Microservices | |||||
|---|---|---|---|---|---|
Hardware resources | vCPU/Cores | CPU Clock Speed (GHz) | Memory (GiB) | Storage (GiB) | Number of MongoDB replicas |
Rocket.Chat | 4 | 4.0 - 5.0 | 8-12 | 20 | N/A |
MongoDB | 2 | 3.0 | 8-16 | 20-80 | 3 |
MongoDB Atlas equivalent(AWS):M30 | |||||
For deployments exceeding 5,000 concurrent users, we recommend a more robust configuration:
Rocket.Chat: 16 vCPU, 12 GiB Memory, 40 GB Storage
MongoDB (per replica): 4 vCPU, 16 GiB Memory, 80 GB Storage
The specifications above are minimum requirements for your Enterprise workspace. Exact specifications depend on your expected concurrent users and workload. More accurate recommendations can be provided during negotiation when purchasing a plan.
Database recommendations
For high availability, a MongoDB replica set of 3 members is strongly recommended. This setup ensures that if one server fails, the others can take over, preventing downtime. You can either self-manage this or use a managed service like MongoDB Atlas to monitor and adjust storage regularly based on usage.
Always verify that your deployment uses a supported MongoDB version.
File storage recommendations
Rocket.Chat recommends using object storage services like Amazon S3, Google Cloud Storage (GCS), or MinIO for file uploads. GridFS is not recommended.
To estimate your storage needs, consider the average file size and upload frequency of your users. For example:
If you have 100 concurrent users, and each user uploads an average of 5 MB of attachments per month, your minimum yearly storage would be:
100 users × 5 MB/user/month × 12 months = 6,000 MB or 6 GB
For more information, refer to our recommendations for file uploads. For deployments above 5,000 concurrent users, request a tailored consultation from Rocket.Chat Sales.
For desktop and mobile apps software requirements, refer to Requirements for Client Apps.