MDB Q2 2027 Earnings Analysis: Revenue Reaccelerates, but Atlas Stalls at 29%

1. Core Earnings Breakdown

Revenue and Profitability Analysis

MongoDB’s fiscal second quarter ended July 31, 2026, delivered the strongest headline growth rate the company has posted in several years. Total revenue reached $771.8 million, up 30% year over year from $591.4 million. Subscription revenue was $747.1 million, up 31%, while services revenue was $24.6 million, up 29%. Subscription revenue represented approximately 96.8% of total revenue, calculated from company-reported figures as $747.1 million divided by $771.8 million.

• Atlas revenue was $565.9 million, up approximately 29% year over year and equal to about 73.3% of total revenue, calculated from company-reported figures as $565.9 million divided by $771.8 million. Investment view: Atlas remains the core economic engine and is still adding record absolute revenue dollars, but the fifth straight quarter near 29% makes the slope of future acceleration more important than the current growth rate itself.
• Enterprise Advanced and other revenue was $181.2 million, up approximately 36% year over year and equal to about 23.5% of total revenue, calculated from company-reported figures as $181.2 million divided by $771.8 million. Investment view: this is strategically important because demand for self-managed deployments, data sovereignty and hybrid environments is expanding MongoDB’s addressable market without management seeing evidence that EA is displacing Atlas.
• Services revenue was $24.6 million, up 29% year over year and equal to about 3.2% of revenue, calculated from company-reported figures as $24.6 million divided by $771.8 million. Investment view: services remain intentionally small, which supports a software-like margin structure and suggests customer adoption is not dependent on a large consulting layer.

Profitability improved even faster than revenue. GAAP gross margin was 74%, up from 71% a year ago, while non-GAAP gross margin was 76%, up from 74%. GAAP operating income was $28.4 million, compared with a $65.3 million operating loss in the prior-year quarter. Non-GAAP operating income more than doubled to $185.9 million, producing a 24% non-GAAP operating margin versus 15% a year earlier. GAAP diluted EPS was $0.50 and non-GAAP fully diluted EPS was $1.90.

Cash generation also improved meaningfully. Operating cash flow was $141.9 million and free cash flow was $137.6 million, versus $72.1 million and $69.9 million, respectively, a year earlier. The quarterly free-cash-flow margin was approximately 17.8%, calculated from company-reported figures as $137.6 million divided by $771.8 million.

Expectations vs. Actual Results

The cleanest way to evaluate Q2 is to separate Street consensus for revenue and EPS from MongoDB’s own prior guidance for operating margin, because publicly available operating-margin consensus data is not consistently reported on the same basis.

• Revenue: actual $771.8 million versus approximately $735.0 million consensus. Result: ✅ beat by about $36.8 million, or roughly 5.0%.
• Non-GAAP EPS: actual $1.90 versus approximately $1.62 consensus. Result: ✅ beat by $0.28, or roughly 17%.
• Non-GAAP operating margin: actual 24.0% versus an implied midpoint of approximately 21.1% from the prior company guide of $152 million-$156 million in non-GAAP operating income on $729 million-$734 million of revenue. Result: ✅ beat by roughly 300 basis points versus the midpoint.

The revenue beat was not a single-deal artifact. On the call, CFO Mike Berry said Atlas exceeded the company’s growth guidance by about 300 basis points, with consumption producing a third consecutive beat and record year-over-year Atlas dollar growth of about $127 million. Enterprise Advanced was also stronger than expected and broad based across financial services, the public sector and technology. That combination matters: Atlas delivered the recurring consumption upside investors want, while EA supplied additional revenue and gross-margin leverage.

The market, however, cared less about the fact that Atlas beat management’s own guide than about whether Atlas growth was accelerating beyond the high-20s. Atlas grew approximately 29% for the fifth consecutive quarter. That is a healthy rate, but after MDB had rallied sharply into the print, the buyside hurdle had moved above official guidance. MarketWatch reported that Morgan Stanley viewed the 29% result as disappointing for investors looking for 30% growth. In other words, the stock was priced for an acceleration narrative, not merely a beat-and-raise quarter.

Next-quarter guidance reinforced that tension. For Q3 FY2027, MongoDB expects revenue of $756 million-$761 million, non-GAAP operating income of $152 million-$156 million, and non-GAAP EPS of $1.57-$1.61. At the high end, the operating-margin guide is about 20.5%. The revenue range implies 20%-21% year-over-year growth and a sequential decline from Q2’s $771.8 million. Management described Q3 as the toughest Atlas comparison of the year and continues to use a prudent consumption-based forecasting framework, but investors still have to underwrite a visible headline deceleration.

For the full fiscal year, revenue guidance increased to $2.99 billion-$3.03 billion from $2.92 billion-$2.96 billion previously. Non-GAAP operating-income guidance rose to $616.3 million-$636.3 million, and non-GAAP EPS guidance increased to $6.39-$6.58 from $5.95-$6.14. Management said the second-half raise is mainly due to Atlas. On the call, it guided to approximately 27% full-year Atlas growth and approximately 11% full-year EA and other revenue growth.

The post-earnings stock reaction therefore diverged sharply from the surface-level results. MDB closed at $434.21 on September 1, before the earnings release, and fell to $375.40 on September 2, a 13.5% one-day decline. By September 11, the stock closed at $362.22, about 16.6% below the September 1 close. This was primarily a multiple-compression event driven by the Atlas growth bar and the forward growth cadence, not by a revenue miss, a margin miss, a new acquisition-dilution shock or an unexpected capital-allocation problem.

Earnings Call Highlights

“Management emphasized that Atlas remained a durable growth engine: about 29% growth for a fifth straight quarter, with a record roughly $127 million increase in revenue dollars.”
💡 Reading Between the Lines: The absolute-dollar growth is arguably healthier than the flat percentage headline suggests, because the base is larger. But the market will likely keep demanding evidence that AI workloads and upmarket consumption can lift Atlas above the high-20s rather than simply sustain it there.

“Management stressed that Enterprise Advanced strength is not coming at the expense of Atlas, and that run-anywhere deployment is a competitive advantage.”
💡 Reading Between the Lines: MongoDB is trying to own the application data layer regardless of whether a workload sits in public cloud, private cloud or on-premises infrastructure. That expands the strategic moat, although EA revenue can remain lumpy because multi-year license duration affects reported revenue timing.

“Voyage customer count nearly doubled quarter over quarter for a second consecutive quarter, while Vector Search adoption continued to outgrow the rest of the company.”
💡 Reading Between the Lines: AI is becoming a credible customer-acquisition funnel rather than only a feature upsell. However, management repeatedly described monetization as early, so investors should not yet model Voyage, Vector Search or MCP as a separate material revenue engine without further disclosure.

“Management raised full-year Atlas growth expectations to about 27% and EA and other revenue growth to about 11%, while keeping a prudent forecasting approach beyond one quarter.”
💡 Reading Between the Lines: The guide leaves room for execution upside if consumption stays strong, but it also embeds a clear slowdown from Q2’s 30% total growth. A sustained premium multiple will require either repeated guidance beats or a new source of acceleration from AI and platform cross-sell.

“MongoDB expects roughly 21% non-GAAP operating margin at the high end of FY2027 guidance and a Rule-of-44 profile at the high end of its outlook.”
💡 Reading Between the Lines: The investment case is no longer only about revenue growth; operating leverage is becoming a second pillar. That improves downside support, but the quality of non-GAAP profitability should still be evaluated alongside stock-based compensation and dilution.

2. Deep Business Insights

Hidden Metrics That Matter

One underappreciated signal is the gap between contracted demand and recognized revenue. Remaining performance obligations reached $1.519 billion, up 91% year over year, while current RPO reached $797.3 million, up 73%. Current RPO was approximately 1.03 times quarterly revenue, calculated from company-reported figures as $797.3 million divided by $771.8 million. That is a strong visibility signal because cRPO growth is running far ahead of reported revenue growth.

There is an important caveat. RPO includes multi-year contracts and future installment payments, and MongoDB’s EA business can have meaningful duration effects. Investors should therefore treat RPO as evidence of customer commitment and future revenue coverage, not as a one-for-one proxy for near-term Atlas consumption. The more durable operating signal is that the total-company net ARR expansion rate rose to 122% from 121% in the prior quarter and 119% a year ago, with strength in both Atlas and EA.

A second hidden metric is the relationship between stock-based compensation and free cash flow. Q2 stock-based compensation expense was $148.9 million, while free cash flow was $137.6 million. SBC therefore equaled approximately 108% of quarterly free cash flow and 19.3% of revenue, calculated from company-reported figures as $148.9 million divided by $137.6 million and $148.9 million divided by $771.8 million, respectively. This does not make free cash flow invalid, but it means dilution economics remain material when valuing the business on non-GAAP earnings or FCF.

MongoDB is taking steps to offset dilution. The company repurchased $100.0 million of stock during Q2 and had approximately $399.7 million remaining under its repurchase authorization at July 31. Repurchases do not economically cancel SBC expense dollar for dollar, but they show that management is allocating capital to control share-count growth while maintaining a $2.4 billion liquidity position.

Why do customers choose MongoDB? The differentiation is increasingly architectural rather than simply brand-driven. MongoDB combines a flexible document data model with operational database capabilities, search, vector search, embeddings and real-time data functions. More importantly, customers can deploy across Atlas in public clouds or Enterprise Advanced in self-managed and private environments using the same core platform and developer skills. For regulated banks, governments and enterprises with data-sovereignty constraints, that run-anywhere model can reduce migration friction and avoid forcing every workload into a single cloud architecture.

The attach-rate data supports the platform argument. Among Atlas customers generating at least $100,000 in ARR, 48% were using two or more platform features, up from 42% a year earlier, with management attributing much of the increase to Vector Search and text search adoption. If that trend continues, MongoDB can monetize the same customer through a broader workload footprint rather than relying only on database-seat expansion.

Industry Chain Reactions

• ✅ Benefit — Amazon (NASDAQ: AMZN): MongoDB’s 10-Q discloses non-cancelable cloud-infrastructure commitments with third-party providers, and Atlas is fundamentally consumption based. Continued Atlas dollar growth and AI retrieval workloads should create incremental hyperscaler infrastructure demand. The read-through to AWS is indirect because MongoDB is multi-cloud and does not disclose cloud-provider-specific economics, so investors should not assign the entire benefit to Amazon.
• ❌ Face Pressure — Elastic (NYSE: ESTC): MongoDB is integrating text search, Vector Search, embeddings and retrieval directly into the operational database across Atlas and Enterprise Advanced. The rise in multi-feature adoption among large Atlas customers suggests some enterprises may prefer a unified data-and-retrieval stack instead of adding a separate search or vector layer. Elastic remains broader than this overlap, especially across observability and security, so the competitive pressure is workload-specific rather than existential.

Valuation Framework and Key Risks

MDB closed at $362.22 on September 11, 2026. Using the 80.556 million shares outstanding disclosed as of August 28, 2026, the implied equity value is approximately $29.18 billion, calculated as $362.22 multiplied by 80.556 million shares. Against the midpoint of FY2027 revenue guidance of $3.01 billion, that equals roughly 9.7 times current-year sales. This ratio is calculated from the latest verified market price plus company-reported share count and revenue guidance.

Using the midpoint of non-GAAP EPS guidance of $6.485, the stock trades at approximately 55.9 times FY2027 non-GAAP EPS, calculated as $362.22 divided by $6.485. A simplified enterprise-value proxy that subtracts the roughly $2.4 billion of cash, cash equivalents, short-term investments and restricted cash from the approximate equity value gives about $26.8 billion, or roughly 8.9 times FY2027 revenue. That simplified EV calculation ignores lease liabilities and other balance-sheet adjustments and should be treated as a valuation shortcut, not a precise transaction-value measure.

At those multiples, the market still embeds a meaningful premium for MongoDB’s combination of low-to-mid-20s forward growth, expanding margins, net retention above 120%, and an AI-driven optionality layer. The valuation can work if Atlas sustains high-20s growth, AI features increase workload intensity, and operating margin moves structurally above 20%. The main danger is that the company executes well but not fast enough to justify the multiple.

• Growth-duration risk: Q3 revenue guidance implies only 20%-21% year-over-year growth, so the market must believe deceleration is mostly comparison-driven rather than structural.
• Atlas reacceleration risk: five quarters near 29% demonstrate consistency, but investors paying a premium multiple may demand renewed acceleration above 30%.
• AI monetization risk: Voyage, Vector Search and MCP adoption are encouraging, but management has not disclosed a material standalone AI revenue contribution. Product engagement can lead revenue by several quarters.
• EA revenue-quality risk: EA is strategically valuable, but multi-year licensing can create timing volatility. Its approximately 36% Q2 revenue growth was much faster than its roughly 11% ARR growth, so investors should normalize reported growth over a longer period.
• Stock-based compensation risk: SBC remains high relative to both revenue and free cash flow. Buybacks help, but they consume cash that could otherwise fund acquisitions or internal investment.
• Competitive risk: MongoDB competes not only with traditional relational databases but also with hyperscaler-native databases, data platforms, search vendors and specialized vector databases. Integrated AI features narrow architecture complexity, but competitors can respond quickly.

The central valuation debate is therefore not whether MongoDB had a good quarter; it did. The debate is whether a roughly 9.7-times sales and 56-times guided non-GAAP earnings multiple adequately discounts a path where Atlas remains in the high-20s rather than reaccelerating. After the post-earnings correction, expectations are lower than they were before the print, but the stock still requires durable execution rather than merely respectable software growth.

3. Key FAQs

Why did MDB stock fall after MongoDB Q2 2027 earnings despite beating revenue and EPS?

MDB fell because the expectations bar was higher than the official consensus bar. Revenue, EPS and operating margin all beat expectations, and full-year guidance increased. However, Atlas growth remained approximately 29% for the fifth straight quarter, while some investors had expected acceleration to 30% or better. Q3 guidance also implies 20%-21% total revenue growth, materially below Q2’s 30%. The selloff therefore reflected a reset in the forward growth multiple rather than a weak reported quarter.

What were MongoDB Q2 2027 revenue, EPS and operating margin versus expectations?

MongoDB reported $771.8 million of revenue versus approximately $735.0 million consensus, non-GAAP EPS of $1.90 versus approximately $1.62 consensus, and a 24% non-GAAP operating margin. The margin result was about 300 basis points above the roughly 21.1% midpoint implied by MongoDB’s prior Q2 operating-income and revenue guidance.

What is MongoDB’s FY2027 guidance after Q2, and what does it imply for Atlas?

MongoDB now expects FY2027 revenue of $2.99 billion-$3.03 billion, non-GAAP operating income of $616.3 million-$636.3 million, and non-GAAP EPS of $6.39-$6.58. Management said the second-half raise is mainly driven by Atlas and, on the earnings call, raised its full-year Atlas growth expectation to approximately 27%. The investment question is whether that guidance proves conservative enough for Atlas to keep producing the 200-300 basis points of upside management has recently delivered.

---

Primary sources: MongoDB’s official Q2 FY2027 financial-results release, MongoDB’s official Q2 FY2027 earnings-call webcast page, and MongoDB’s Q2 FY2027 Form 10-Q. MongoDB Investor Relations provides the webcast/replay rather than an official written transcript; management-call details were cross-checked against the official replay and a full third-party transcript. Market-reaction context was cross-checked against MarketWatch, and the latest verified September 11 closing price was cross-checked against Business Quant.

Disclaimer: This article/chart is for educational and informational purposes only and does not constitute investment advice of any kind. Past performance is not indicative of future results. Investors should independently evaluate their own risks.