--- title: "System Requirements" slug: "system-requirements" description: "Check Rocket.Chat system requirements to ensure smooth deployment. Learn supported platforms, hardware, and software needs for reliable performance." updated: 2026-06-18T17:55:12Z published: 2026-06-18T17:55:12Z canonical: "docs.rocket.chat/system-requirements" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.rocket.chat/llms.txt > Use this file to discover all available pages before exploring further. # System Requirements 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. > [!NOTE] > - 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 premium workspaces ([Commercial](/v1/docs/our-plans#commercial-plan), [Government](/v1/docs/our-plans#government-plan), [Defense](/v1/docs/our-plans#defense-plan)) or specialized setups like Chat Engine, consult [Rocket.Chat Sales](https://www.rocket.chat/sales-contact) for tailored recommendations. --- ## Software requirements Rocket.Chat requires specific software components for the server runtime and database. The required versions for each component vary by Rocket.Chat release. The table below applies to the latest [Rocket.Chat 8.5 release](https://github.com/RocketChat/Rocket.Chat/releases/tag/8.5.0). If you are on a different release, [check the dependency requirements for your version](/v1/docs/check-your-supported-nodejs-and-mongodb-versions). > [!NOTE] > If you deploy using the official [Docker image](/v1/docs/deploy-with-docker-docker-compose) or [Helm chart](/v1/docs/deploy-with-kubernetes), 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. | Component | Supported version | Comments | | --- | --- | --- | | **MongoDB** | 8.0 | Required for Rocket.Chat 8.2 and later. See [MongoDB version requirements](/v1/docs/support-prerequisites#mongodb-version-requirements) for the full compatibility table. | | **Node.js** | 22.22.3 | Included in the official Docker image and Helm chart. Manual installs must match this version. | | **Deno** | 2.3.1 | Used by the [Apps-Engine](https://developer.rocket.chat/docs/rocketchat-apps-engine) runtime. Included in the official Docker image and Helm chart. Manual installs must match this version. | > [!WARNING] > 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](/v1/docs/guidelines-for-updating-rocketchat#3-review-and-update-mongodb) for step-by-step instructions. --- ## Hardware specifications The hardware requirements for Rocket.Chat varies depending on the expected user load and workspace [plan](/v1/docs/our-plans). | Scenario: [Starter](/v1/docs/our-plans#starter-workspaces) - 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: [Commercial](/v1/docs/our-plans#commercial-plan) \| [Government](/v1/docs/our-plans#government-plan) \| [Defense](/v1/docs/our-plans#defense-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 > [!NOTE] > 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](/v1/docs/our-plans). --- ## 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. > [!NOTE] > Always verify that your deployment uses a [supported MongoDB version](/v1/docs/support-prerequisites#mongodb-version-requirements). --- ## 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, refer to our [recommendations for file uploads](/v1/docs/recommendations-for-file-upload). --- ## Network ports requirements Rocket.Chat deployments primarily expose a minimal set of ports externally. These ports are exposed to the users or the public internet (unless in an air-gapped environment). Additional ports may be required internally depending on the features you're using. | Port | Protocol | Purpose | | --- | --- | --- | | 443 | TCP | The primary entry point. It handles all HTTPS traffic from web, desktop, and mobile clients. | | 80 | TCP | Used for initial HTTP connection. It redirects immediately to 443 (SSL). | > [!NOTE] > For desktop and mobile apps software requirements, refer to [Requirements for Client Apps](/minimum-requirements-for-client-apps).