System Requirements

This document covers the system requirements for each Rocket.Chat deployment scenario. Use it to choose the hardware, storage, and database configuration your workspace needs, and to check what changes as the workspace grows.

Requirements vary with your organization's size, usage patterns, and deployment method. Review your specifications as the workspace grows.

For premium workspaces (Commercial, Government, Defense) or specialized setups like Chat Engine, consult Rocket.Chat Sales for tailored recommendations.

Software requirements

Rocket.Chat requires specific software components for the server runtime and database. The required versions change from release to release. The table below lists the versions for Rocket.Chat 8.8. For any other release, check the dependency requirements for your version.

If you deploy using the official Docker image or Helm chart, Node.js and Deno are bundled and managed automatically. However, MongoDB must be installed and maintained separately to be compatible with your Rocket.Chat release.

To confirm the versions for any release, open the Engine versions section of that release on the Rocket.Chat releases page, or run curl -s https://releases.rocket.chat/<VERSION>/info.

If you are upgrading from Rocket.Chat 7.x, you must upgrade MongoDB to version 8.0 before updating to Rocket.Chat 8.x. Refer to Review and update MongoDB for step-by-step instructions.

Hardware specifications

Hardware requirements vary with the expected user load and the workspace plan. For per-tier deployment topology and scaling guidance, see Reference architectures by workspace size.

MongoDB Atlas equivalent (AWS): M30.

MongoDB Atlas equivalent (AWS): M30.

For deployments above 5,000 concurrent users, run Rocket.Chat as microservices on Kubernetes and size each component as follows:

• 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. 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 details, see recommendations for file uploads.

Network ports requirements

Rocket.Chat deployments expose a minimal set of ports externally. These ports are reachable by users or the public internet, unless the workspace is air-gapped. Components also use internal ports to reach each other, which are covered below the table.

Internal ports are not exposed to users. If MongoDB runs on a separate host, port 27017 must be open between Rocket.Chat and the database. See Configure external MongoDB for Rocket.Chat. Microservices and monitoring setups need further internal ports; check the deployment guide for your setup.

For desktop and mobile apps software requirements, refer to Requirements for Client Apps.

Related topics

• Reference architectures by workspace size

• Check your supported Node.js and MongoDB versions

• Guidelines for updating Rocket.Chat

• Recommendations for file uploads

• Minimum requirements for client apps