2009 – 2026
MongoDB Versions
Every release of the MongoDB server — from the 10gen 1.0 release in 2009 through the 8.x line. MongoDB 8.0 (October 2024) is the current major; 8.3 (May 2026) is the latest quarterly Rapid Release on top of it. With ship dates, support/EOL state, and the headline changes per major version — the storage-engine arc (MMAPv1 → WiredTiger), the transactions arc (replica-set then sharded ACID), and the October 2018 relicensing from AGPL to the SSPL that this page exists to explain.
The 2009 origin at 10gen and the document model
MongoDB began inside 10gen, a New York startup founded in 2007 by Dwight Merriman, Eliot Horowitz, and Kevin Ryan — veterans of the ad-tech company DoubleClick. Their original plan was a platform-as-a-service; MongoDB was the database component, and when the platform didn't take off the database did. The name comes from “humongous.” Version 1.0 shipped in August 2009.
The core idea was the document model: instead of rows in fixed-schema tables, MongoDB stores BSON (binary JSON) documents with a flexible schema, so a record can be a nested object that maps cleanly onto how application code already represents data. Combined with built-in horizontal sharding and replica sets (both production-ready by 1.6 in 2010), that model made MongoDB the default face of the “NoSQL” movement of the early 2010s. 10gen renamed itself MongoDB, Inc. in 2013, and the company went public on NASDAQ (ticker MDB) in October 2017.
The storage-engine arc — MMAPv1 to WiredTiger
For its first six years MongoDB ran on MMAPv1, a storage engine built on memory-mapped files. It was simple and fast for reads, but its concurrency model was its defining limit: a single global write lock at first, relaxed to database-level locking in 2.2 and never finer than that. Under write-heavy, multi-collection workloads, MMAPv1 became the bottleneck everyone hit.
In December 2014 MongoDB acquired WiredTiger Inc., whose founders Keith Bostic and Michael Cahill had previously built Berkeley DB. WiredTiger shipped as an option in 3.0 (March 2015) and became the default in 3.2 (December 2015). It brought document-level concurrency control and native compression, frequently a 7–10× improvement on contended write workloads. WiredTiger is the reason 3.0 is treated as the boundary between legacy and modern MongoDB.
MMAPv1 was deprecated in 4.0 and removed entirely in 4.2 (August 2019). Today the on-disk engine is always WiredTiger; MongoDB Enterprise additionally offers an in-memory engine for latency-sensitive workloads. An old deployment that “behaved differently after upgrading” almost always crossed the MMAPv1 → WiredTiger line.
The transactions arc — replica-set then sharded ACID
For most of its first decade, MongoDB's answer to “does it have transactions?” was “single-document operations are atomic, design your documents so you don't need more.” That was a real constraint, and a frequent reason teams chose a relational database instead.
MongoDB 4.0 (June 2018) changed the answer with multi-document ACID transactions across a replica set, built on the client-sessions machinery added in 3.6. 4.2 (August 2019) extended transactions to sharded clusters, completing the story. The feature was deliberately staged — replica-set first, then distributed — and it removed the single most-cited objection to using MongoDB for systems of record. (Best practice is still to model around the document so transactions are the exception, not the rule.)
The 5.0 versioning-scheme change and Rapid Releases
Through 4.x, MongoDB shipped a new numbered release every roughly 12–18 months. MongoDB 5.0 (July 2021) replaced that with a faster, more predictable cadence: one yearly Major Release (5.0, 6.0, 7.0, 8.0) plus quarterly Rapid Releases (5.1, 5.2, 5.3…) that deliver incremental features between majors and then fold into the next major.
Rapid Releases were originally available only inside MongoDB Atlas, MongoDB's managed cloud service — not as downloadable server builds. That changed with 8.2 (September 2025), after which Rapid Releases are downloadable for self-managed Community and Enterprise deployments too. So as of mid-2026 the current major line is 8.0 (long-term supported through October 2029), while the current downloadable tip is the 8.3 Rapid Release (May 2026). The practical upshot: the “current version” number drifts roughly every quarter, faster than a once-a-year database like PostgreSQL.
The October 2018 SSPL relicensing
By 2018, MongoDB's biggest commercial threat wasn't another database — it was cloud providers offering MongoDB as a managed service and capturing the revenue without contributing to the project. The server had been licensed under the GNU Affero GPL v3, whose Section 13 was meant to cover exactly the network-service case, but MongoDB argued its scope was ambiguous and untested in court.
On October 16, 2018, MongoDB issued the Server Side Public License. SSPL copies most of the AGPL but rewrites Section 13: offer the functionality of the software as a service to third parties, and you must release the complete source of the service you use to make it available — management software, APIs, monitoring, the lot — under SSPL. In practice that is an unmeetable condition for a hyperscaler, which is the point.
MongoDB submitted SSPL to the Open Source Initiative for certification and faced sustained objection on the OSI's license-review list that the condition discriminated against a field of endeavor, violating the Open Source Definition. MongoDB withdrew the submission in 2019; SSPL has never been OSI-approved. The accurate description of MongoDB today is “source-available”, not “open source.” Debian, Fedora, and Red Hat Enterprise Linux removed MongoDB from their package repositories over the license — which is why, to this day, you install MongoDB from MongoDB's own apt/yum repositories rather than your distro's, and why Homebrew serves it from a dedicated mongodb/brew tap rather than core.
Two things are worth keeping straight. First, only the server was relicensed; the official client drivers (PyMongo, and the Node, Java, Go, and C# drivers) remain Apache 2.0, so application code that merely talks to MongoDB is unaffected. Second, the move triggered a competitive response: AWS launched Amazon DocumentDB in January 2019, a service that emulates the MongoDB API on a different engine, sidestepping the license entirely. MongoDB's relicensing became the template a wave of other infrastructure companies followed — Elastic, Redis, HashiCorp, and others all later adopted source-available licenses for similar reasons. For the canonical text and MongoDB's own framing, see the SSPL and its FAQ.
MongoDB Atlas and the cloud-first turn
The same logic that drove the SSPL drove MongoDB's product strategy. In 2016 the company launched MongoDB Atlas, a fully managed database-as-a-service running on AWS, Google Cloud, and Azure. Rather than fight the cloud as a distribution channel, MongoDB became a cloud vendor itself — and Atlas grew into the majority of the company's revenue.
That turn shapes the version story directly. Rapid Releases debuted as an Atlas-only feature; several capabilities land in Atlas before the downloadable server; and features like Atlas Search and Atlas Vector Search were managed-service exclusives before 8.3 brought a self-managed preview of search and vector search in 2026. This page deliberately tracks the Community / Enterprise server version line — the thing you download and run — and treats Atlas, Compass, and Ops Manager as separate product tracks mentioned only where they intersect the server's history.
