Check Your Supported Node.js and MongoDB Versions

Prev Next

Rocket.Chat is built on Node.js and requires a compatible MongoDB database. This guide explains how to check the supported versions of both for your Rocket.Chat deployment.

If you deploy using the recommended methods, Node.js is managed automatically, and you don’t need to worry about its version. The only time you may need to check Node.js is when debugging rare cases or using manual installation, which is not recommended. On the contrary, MongoDB is different because ensuring your database runs a supported version is your responsibility and must be actively managed as you upgrade Rocket.Chat over time.

Before proceeding, keep the following in mind about MongoDB support:

  • Supported MongoDB versions are defined per release and can change across major versions. Refer to the MongoDB version requirements for the full list.

  • MongoDB support is never dropped without notice. A version marked for removal is first deprecated, and as a workspace admin you will see a deprecation warning in your Rocket.Chat logs along with a notice banner on your workspace.


Rocket.Chat defines compatible Node.js and MongoDB versions per release. You can retrieve this information in two main ways: GitHub release notes and the releases API.

Option A: Using GitHub release notes

  1. Go to the Rocket.Chat releases page.

  2. Select your target Rocket.Chat version (e.g., 8.1.0, 8.2.0).
    Alternatively, you can use the following template link to inspect the release notes, replacing <VERSION> with your target release number: https://github.com/RocketChat/Rocket.Chat/releases/<VERSION> .

  3. Locate the “Engine versions” section, which lists all relevant version requirements in one place.

Supported Engine Versions for a Release

Supported Engine Versions

From here you can determine the compatible MongoDB and Node.js versions for your release.

Option B: Using the releases API

This option is faster and particularly useful if you need to retrieve version information programmatically, such as in a script or automation pipeline.

Start by running the following command in your terminal, replacing <VERSION> with your target release number:

curl https://releases.rocket.chat/<VERSION>/info -s | jq '.'

For example, to check version 8.2.0 specifically:

curl https://releases.rocket.chat/8.2.0/info -s | jq '.'

It returns a full JSON response like this:

{
  "tag": "8.2.0",
  "commit": "f2a05ceed2086266fa3e36cf575c1794f68f00ab",
  "key": "build/rocket.chat-8.2.0.tgz",
  "etag": "6a13ead87a64cfae66037e5cac9c8f0b-33",
  "count": 1201,
  "nodeVersion": "22.16.0",
  "denoVersion": "1.43.5",
  "compatibleMongoVersions": [
    "8.0"
  ],
  "lts": false
}

The two fields you’ll be looking out for are nodeVersion and compatibleMongoVersions.