MongoDB Version EOL (2026)

MongoDB uses a dual-track release model with Rapid releases (quarterly) and LTS releases (approximately annually). Each major version receives roughly 3 to 4 years of support for on-premise deployments, while MongoDB Atlas — MongoDB’s managed cloud service — handles upgrades automatically and often supports versions beyond their on-premise EOL. Understanding the MongoDB release cycle is critical for planning upgrades in self-managed environments, as MongoDB enforces an N-1 upgrade requirement — you cannot skip more than one major version during upgrades. MongoDB’s shift from SSPL licensing and the emergence of community forks like FerretDB have added new considerations to lifecycle planning.

MongoDB Version Support Table

MongoDB Support Policy

MongoDB’s support model differs between self-managed deployments and MongoDB Atlas.

• Rapid releases: Feature releases every quarter. These are not LTS — they receive support only until the next Rapid release ships.
• LTS releases: Released approximately once per year. Each LTS version receives 3–4 years of support from the initial GA date.
• Atlas support: MongoDB Atlas automatically manages version upgrades within your maintenance window. Atlas typically supports versions beyond their on-premise EOL to give you time to schedule upgrades.
• Upgrade requirement: MongoDB supports upgrading only from the previous major version (N-1). To skip more than one version, you must upgrade incrementally.
• MongoDB 5.0 status: 5.0 reached EOL in January 2025. If you are still on 5.0, you must upgrade to 6.0 (and then to 7.0 if desired).

How to Check Your MongoDB Version

mongod --version

From within a mongosh session:

db.version()

FAQ

Related Schedules

• PostgreSQL Version EOL
• Redis Version EOL