Who Provides Support for End-of-Life MongoDB 4.x, 5.0 and 6.0?

The short answer

For MongoDB Enterprise Advanced customers, MongoDB itself sells an Extended Lifecycle Support add-on that gives up to two more years of technical support for one minor version after it reaches end of life. For self-managed MongoDB Community Server 4.2, 4.4, 5.0 and 6.0, OSSeva publishes patched builds under a contract, including 4.2 and 4.4 builds for CPUs without AVX. Percona sells 24x7 MongoDB support and its own Percona Server for MongoDB, which follows MongoDB's end-of-life dates and gets only best-effort builds after them. Perforce OpenLogic sells MongoDB technical support. MongoDB Atlas no longer runs 6.0 or earlier.

The question that decides most cases is whether you hold an Enterprise Advanced subscription. Without one, MongoDB's own extended support is not available, and the choice is between upgrading and a third party.

Which MongoDB versions are still supported

MongoDB publishes one end-of-life date per major version. In September 2025 it lengthened the window to four years for 7.0 and five years for 8.0 and later.

Two constraints keep estates on old versions. Upgrades go one major version at a time, with featureCompatibilityVersion raised at each step, so 4.4 to 7.0 is three upgrades. And from 5.0, MongoDB on x86_64 needs a CPU with AVX, which holds some hardware on 4.4. MongoDB also says drivers released more than three years after a server's end of life will not be compatible with it, so an old server slowly constrains the applications too. The MongoDB end-of-life chart tracks every line, and MongoDB vulnerabilities by version lists the advisories.

MongoDB support providers compared

Each row reflects what the provider publishes on its own site as of 6 October 2026.

The MongoDB row is easy to misread. The add-on is described as technical support for a minor version, bought on top of Enterprise Advanced, so it does not reach Community Server estates and it covers one minor release rather than a whole major line.

How the providers differ

MongoDB

If you already run Enterprise Advanced, MongoDB's Extended Lifecycle Support add-on is the most direct answer: up to two more years on a chosen minor version, with the vendor's own support engineers. With 7.0 now running to August 2027 and 8.0 to 2029, the longer standard lifecycles also mean that getting to 8.0 buys several years without any add-on. On Atlas, the question answers itself: MongoDB gives at least six months' notice before a version's end of life and then upgrades the cluster.

Percona

Percona is an independent open source database company. For MongoDB it sells 24x7 support for daily operations, scaling and recovery, consulting on architecture and migrations, and its own Percona Server for MongoDB, a drop-in compatible build released under SSPL like upstream. Its lifecycle page matches MongoDB's end-of-life dates, and it says builds after end of life are best effort and not guaranteed, with upgrading as its recommendation. That makes Percona a strong choice for running and upgrading MongoDB, and a weaker one for staying on 4.4 or 5.0. See OSSeva vs Percona.

Perforce OpenLogic

OpenLogic lists MongoDB among more than 400 supported technologies at all three support levels, which suits teams that want one contract across the stack. It does not publish patched MongoDB builds. See OSSeva vs OpenLogic.

OSSeva

OSSeva for MongoDB patches self-managed Community Server on the version you run, so a replica set or sharded cluster can stay on 4.4, 5.0 or 6.0 while the featureCompatibilityVersion steps are planned and tested. The 4.2 and 4.4 builds also cover hardware that cannot run 5.0 because it lacks AVX. Patch delivers backported fixes for mongod, mongos and the bundled tools as signed packages and images with SBOMs. Assure adds an authentication, TLS and network exposure review, a featureCompatibilityVersion upgrade plan, a driver compatibility audit and a SOC 2 and PCI DSS evidence pack. Operate adds 24/7 replica set and cluster monitoring, a 15-minute P1 response, a named MongoDB engineer and executed major upgrades, and patches Critical CVEs (CVSS 9.0 and above) within 48 hours and High within 7 days. OSSeva does not support Atlas. Pricing is per replica set or cluster.

A note on licensing

MongoDB Community Server releases from 16 October 2018 onward, including later patch releases of older versions, are under the Server Side Public License. MongoDB's FAQ says Section 13 applies when you offer MongoDB to third parties as a service, and that running it as a service internally or for subsidiaries is not offering it to a third party. That obligation is the same whoever supports or patches your build, including Percona's and OSSeva's.

How to choose

Our MongoDB 4.4 to 7.0 upgrade guide covers the steps, and the MongoDB AVX requirement covers the hardware question.

Where OSSeva fits

OSSeva covers self-managed MongoDB 4.2 to 6.0 with contracted security fixes, which suits Community Server estates held back by hardware, drivers or certification. MongoDB extended support covers that in more detail, MongoDB 4.4 on non-AVX hardware covers the hardware case, and the extended support vendor roundup compares OSSeva across other technologies.

Frequently asked questions

Which companies offer MongoDB support besides the original vendor?

Percona sells 24x7 MongoDB support, consulting and its own Percona Server for MongoDB. Perforce OpenLogic sells MongoDB technical support. OSSeva ships patched builds of self-managed MongoDB 4.2 to 6.0 with optional 24/7 operations.

What are the alternatives to MongoDB's Extended Lifecycle Support add-on?

Upgrading to 7.0 or 8.0, whose lifecycles now run to August 2027 and October 2029. Moving to Atlas, where MongoDB handles upgrades. Or, for self-managed Community Server, contracted patched builds from OSSeva. Percona offers support but describes post-EOL builds as best effort.

Who supports MongoDB Community Server versions that MongoDB no longer supports?

OSSeva publishes patched Community Server 4.2, 4.4, 5.0 and 6.0 builds. Percona and OpenLogic sell support for running MongoDB, without guaranteed fixes for retired versions. MongoDB's own extended support requires Enterprise Advanced.

Who provides CVE patches for MongoDB after end of life?

MongoDB, for Enterprise Advanced customers with the Extended Lifecycle Support add-on, and OSSeva, for self-managed Community Server 4.2 to 6.0. Percona says post-EOL builds of Percona Server for MongoDB are best effort and not guaranteed.

Is there commercial support for MongoDB 6.0 after end of life?

Yes. MongoDB 6.0 reached end of life on 31 July 2025. Enterprise Advanced customers can buy MongoDB's Extended Lifecycle Support add-on, and OSSeva ships patched 6.0 builds for self-managed clusters. Atlas no longer runs 6.0.

Who offers extended support for MongoDB 5.0?

OSSeva ships patched builds of MongoDB 5.0, which reached end of life on 31 October 2024. MongoDB's add-on covers a minor version for up to two years past its end of life, so ask MongoDB whether a 5.0 minor still qualifies.

Top providers for mongodb lifecycle support

MongoDB for Enterprise Advanced and Atlas customers, Percona for independent operational support and upgrades, OpenLogic for a broad support contract, and OSSeva for patched builds of self-managed versions past end of life.