MongoDB's SSPL trades AGPL litigation for a wider disclosure duty

The workload

MongoDB relicensed its server code from the AGPL to its own Server Side Public License in October 2018. Verified: the change applied to 'all subsequent versions and patch releases to prior versions of MongoDB made after October 16th, 2018,' per the company's own dated announcement. For a founder, the workload SSPL creates is a scoping exercise: deciding whether a product 'makes the functionality of the Program or a modified version available to third parties as a service,' the trigger section 13 of the license text names, and if so, preparing to publish the full service stack the clause defines.

What the documents show

Verified: section 13 states that anyone offering the covered program 'as a service' must make the 'Service Source Code available via network download to everyone at no charge.' The license defines that term expansively, as the Corresponding Source for the program plus the source for 'all programs that you use to make the Program or modified version available as a service, including, without limitation, management software, user interfaces, application program interfaces, automation software, monitoring software, backup software, storage software and hosting software.' Self-reported: MongoDB's own announcement, byline Eliot Horowitz, says the change was meant 'to ensure we can continue to invest in building MongoDB for our users rather than in costly litigation over enforcing the AGPL,' and points to large cloud vendors offering the database as a managed service while 'contributing little or nothing back.' Verified: the Open Source Initiative's approved-license list, as retrieved 16 September 2026, does not include SSPL, a documented dispute over whether the license meets the Open Source Definition rather than a settled question either way.

The operating cost

The license names no fee; its cost is the scope of disclosure it would require if triggered. Estimated: publishing an entire management, monitoring, backup and hosting stack as open source is a materially larger undertaking than publishing one modified file, closer to open-sourcing an internal platform than to complying with a notice requirement, though the license states no dollar figure and this analysis does not supply one.

The stop condition

The obligation attaches only while the service offering continues under a modified or unmodified copy of the covered program; per the text, it would end if the offering stopped or the dependency were replaced. Whether any specific company's use of MongoDB actually crosses the 'as a service' line is not something the license text or this entry settles; that determination depends on facts the text alone cannot supply.

• Does the product let third parties use the database's functionality as a distinct offering, or only as internal storage behind another service?
• If SSPL applies, is the full management, monitoring and hosting stack it names something the business could publish?
• Would a commercial license from MongoDB cost less than the disclosure the free license would require?

SSPL's obligation is specific and textual, not a vague warning about 'open source drama.' Reading section 13 against an actual deployment, rather than against its reputation, is the only way to know whether it applies.