System Requirements
- Print
- DarkLight
- PDF
System Requirements
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
This document provides an overview of the system requirements for various Rocket.Chat deployment scenarios. The specifications guide system administrators in selecting appropriate hardware and storage capacities for a stable and efficient Rocket.Chat environment.
It is essential to customize these requirements based on your specific needs and usage patterns.
Regular reviews and adjustments to your system specifications are recommended to ensure optimal performance.
For deployments with special requirements (such as Omnichannel, Chat Engine) or enterprise-grade setups, please consult with Rocket.Chat representatives for tailored advice.
Hardware specifications
The hardware requirements for Rocket.Chat vary depending on the expected load and deployment scenario. Below are the specifications for different use cases:
Scenario: Starter plan - No high availability - Concurrent users ≤ 25 | ||||
|---|---|---|---|---|
Hardware resources | vCPU | Memory(GiB) | Storage(40) | Number of MongoDB replicas |
Rocket.Chat | 1 | 2 | 40 | N/A |
MongoDB | 2 | 2 | 10 | 1 |
MongoDB Atlas equivalent(AWS):M10 | ||||
Scenario: Pro plan - High availability - Concurrent users < 500 | ||||
|---|---|---|---|---|
Hardware resources | vCPU | Memory(GiB) | Storage(40) | Number of MongoDB replicas |
Rocket.Chat | 2 | 4 | 40 | N/A |
MongoDB | 2 | 4 | 20 | 3 |
MongoDB Atlas equivalent(AWS):M20 | ||||
Scenario: Enterprise plan - High availability - Concurrent users 500 to 5000 - Microservices | ||||
|---|---|---|---|---|
Hardware resources | v(CPU) | Memory(GiB) | Storage(40) | Number of MongoDB replicas |
Rocket.Chat | 4-16 | 4-12 | 40 | N/A |
MongoDB | 2-8 | 4-16 | 20-80 | 3 |
MongoDB Atlas equivalent(AWS):M20 - M40 | ||||
File storage requirements
Rocket.Chat recommends using object storage services such as Amazon S3, GCS, or MinIO for file uploads. GridFS is not recommended for production environments, and therefore, the storage estimation is not considered. Depending on your use case, factor in the average MB/month/user to provide a realistic estimation of your storage size per year.
Example calculation:
If each user sends an average of 5 MB in attachments per month, and there are 100 concurrent users, the minimum yearly storage needed is:
100 users * 5 MB * 12 months = 6,000 MB or approximately 6 GB
Custom consultations are recommended for deployments of over 5000 concurrent users. For more information, visit recommendations for file upload.
MongoDB considerations
A MongoDB replica set of 3 members is advised for high-availability scenarios to ensure sufficient space and resilience.
Suggested MongoDB Atlas instance for HA: Consider the base storage offered in the tier and adjust it on a regular basis according to utilization.
Rocket.Chat specifications for large deployments
For use cases exceeding 5000 concurrent users, the specifications are:
vCPU: 16
Memory: 12 GiB
Storage: 40 GB
MongoDB specifications per replica:
vCPU: 4
Memory: 16 GiB
Storage: 80 GB
Number of MongoDB replicas needed: 3
File storage (S3, GCS):
5000 users 2 MB 12 months = 120,000 MB or 120 GB/year (minimum)
These are minimum requirements, and we recommend considering a buffer for growth.
Was this article helpful?