Loading…

MongoDB (MDB) backlog: remaining performance obligations

How much revenue MongoDB already has under contract, how fast it converts, and who it is with.

Data as of .

MongoDB backlog history

$0$1B$2B$3BJul 2020Jan 2021Jul 2021Jan 2022Jan 2024Apr 2025Oct 2025Apr 2026Jul 2026Backlog (RPO)Trailing 12-month revenue
Remaining performance obligations at each quarter end (bars) against trailing twelve-month revenue (line).
Amounts in USD. Source: SEC XBRL filings.
Quarter endBacklog (RPO)TTM revenueCoverageCustomer prepayments
31 Jul 2026$1.52B$2.78B0.5 yrs$448M
30 Apr 2026$1.46B$2.60B0.6 yrs$432M
31 Jan 2026$1.47B$2.46B0.6 yrs$471M
31 Oct 2025$994M$2.32B0.4 yrs$367M
31 Jul 2025$794M$2.22B0.4 yrs$309M
30 Apr 2025$774M$2.10B0.4 yrs$320M
31 Jan 2025$748M$2.01B0.4 yrs$360M
31 Jan 2024$591M$1.68B0.4 yrs$377M
31 Jan 2023$461M$1.28B0.4 yrs$460M
31 Jan 2022$387M$874M0.4 yrs$375M
31 Oct 2021$353M$778M0.5 yrs$298M
31 Jul 2021$281M$702M0.4 yrs$249M

Questions

What is MongoDB's backlog?
MongoDB reported $1.52B of remaining performance obligations at 31 Jul 2026, up 91% from a year earlier and up 4% from the previous quarter. That is 0.5 years of trailing revenue already under contract. Book-to-bill last quarter: 1.08.
How fast does MongoDB's backlog turn into revenue?
Over the last twelve months MongoDB recognised revenue equal to about 249% of the backlog it started each quarter with.

About these numbers

Remaining performance obligations (RPO) are revenue a company has contracted but not yet recognised, as reported in its SEC filings (XBRL tag RevenueRemainingPerformanceObligation). Coverage = backlog ÷ trailing twelve-month revenue. Book-to-bill = (change in backlog + revenue) ÷ revenue. Conversion = revenue recognised ÷ the backlog at the start of each quarter, summed over four quarters. Counterparty values come from company filings and releases.