Good day, and thank you for standing by. Welcome to the MongoDB's Q2 Fiscal Year 2025 Conference Call. At this time, all participants are on a listen-only mode. After the speaker's presentation, there'll be a question-and-answer session. To ask a question during the session, you will need to press star one one on your telephone. You will then hear an automated message advising your hand is raised. To withdraw your question, please press star one one again. Please be advised that today's conference is being recorded. I would now like to turn the call over to your speaker for today, Brian Denyeau. Please go ahead. Thank you, Lisa. Good afternoon, and thank you for joining us today to review MongoDB's Q2 Fiscal 2025 Financial Results, which we announced in our press release issued after the close of market today. Joining me on the call today are Dev Ittycheria, President and CEO of MongoDB, and Michael Gordon, MongoDB's COO and CFO. During this call, we will make forward-looking statements, including statements related to our market and future growth opportunities, our expectations for the macroeconomic environment in fiscal 2025 and the impact of AI, the benefits of our product platform, our competitive landscape, customer behaviors, our financial guidance, and our planned investments and growth opportunities in AI. These statements are subject to a variety of risks and uncertainties, including the results of operations and financial conditions that could cause actual results to differ materially from our expectations. For a discussion of the material risks and uncertainties that could affect our actual results, please refer to the risks described in our quarterly report on Form 10-Q for the quarter ended April thirtieth, 2024, filed with the SEC on 31st May, 2024. Any forward-looking statements made in this call reflect our views only as of today, and we undertake no obligation to update them except as required by law. Additionally, we will discuss non-GAAP financial measures on this conference call. Please refer to the tables in our earnings release on the investor relations portion of our website for a reconciliation of these measures to their most directly comparable GAAP financial measure. With that, I'd like to turn the call over to Dev. Thanks, Brian, and thank you to everyone for joining us today. I'm pleased to report that we had a good quarter and executed well against our large market opportunity. Let's begin by reviewing our Q2 results before giving you a broader company update. We generated revenue of $478 million, a 13% year-over-year increase against a very difficult year-over-year compare and above the high end of our guidance. Atlas revenue grew 27% year-over-year, representing 71% of revenue. We generated non-GAAP operating income of $52.5 million for 11% non-GAAP operating margin, and we ended the quarter with over 50,700 customers. Overall, we were pleased with the performance in the Q2. We had a strong new business quarter, and we saw improving sales productivity year-over-year. We saw strength across the board, with both Atlas and Enterprise Advanced exceeding our expectations, demonstrating the enduring appeal of our Run Anywhere strategy. Our Q2 performance reinforced our belief the slow start to the new business Q1 was purely operational, and we feel good about our new business outlook in the second half of the year. Moving on to Atlas consumption, the quarter played out modestly better than our expectations. Michael will discuss consumption trends in more detail. Finally, retention rates remained strong in Q2, demonstrating the quality of our product and the mission criticality of our platform. Our performance this quarter reinforced our confidence in our ability to execute on our long-term opportunity. As we said before, companies today rely on software to express their business strategy. This trend has driven our success for the past decade, and we anticipate it will continue to do so for the foreseeable future. Even with our success to date, we only have a low single-digit share in one of the largest and fastest-growing markets in all of software. When you combine this foundational tailwind with the opportunities for our customers to incorporate generative AI into their businesses and modernize their legacy application estate, it is clear that MongoDB has multiple long-term growth opportunities. Turning to AI, AI continues to be an additional long-term opportunity for our business. At the start of the fiscal year, we told you that we didn't expect AI to be a meaningful tailwind for our business in fiscal year 2025, which has proven accurate. Based on recent peer commentary, it seems that the industry now mostly agrees with this view. Companies are currently focusing their spending on the infrastructure layer of AI and are still largely experimenting with AI applications. Inference workloads will come and should benefit MongoDB greatly in the long run, but we are still very early. When the monetization of AI apps will take time. AI demand is a question of when, not if, and our discussions with customers and partners give us increasing conviction that we are the ideal data layer for AI apps for a number of key reasons. First, more than any other type of modern workload, AI-driven workloads require the underlying database to be capable of processing queries against rich and complex data structures quickly and efficiently. Our flexible document model is uniquely positioned to help customers build sophisticated AI applications because it is designed to handle different data types, your source data, vector data, metadata, and generated data right alongside your live operational data, obviating the need for multiple database systems and complex backend architectures. Second, MongoDB offers a high-performance and scalable architecture. As the latency of LLMs improve, the value of using real-time operational data for AI apps will become even more important. Third, we are seamlessly integrated with leading app development frameworks and AI platforms, enabling developers to incorporate MongoDB into their existing workflows while having the flexibility to choose the LLM and other specific tools that best suit their needs. Fourth, we meet or exceed the security and compliance requirements expected from an enterprise database, including enterprise-grade encryption, authorization, and auditability. Lastly, customers can run MongoDB anywhere, on-premise, or as a fully managed service in one of the 118 global cloud regions across three hyperscalers, giving them the flexibility to run workloads to best meet their application use cases and business needs. We see three main opportunities where we believe AI will accelerate our business over time. The first is that the cost of building applications in the world of AI will come down, as we've seen with every previous platform shift, creating more applications and more data, requiring more databases. The second opportunity is for us to be the database of choice for customers building greenfield AI applications. While we see that there's tremendous amount of interest in and planning for new AI-powered applications, the complexity and fast-moving nature of the AI ecosystem slows customers down. That's why we launched the MongoDB AI Applications Program, or MAAP, which became generally available to customers last month. MAAP brings together a unique ecosystem, including the three major cloud providers, AWS, Azure, and GCP, as well as Accenture and AI pioneers like Anthropic and Cohere. MAAP offers customers reference architectures, an end-to-end technology stack that includes pre-built integrations, professional services, and a unified support system to help customers quickly build and deploy AI applications. The third opportunity is to help customers modernize their legacy application estate. As you know, this segment of the market is a massive opportunity for us, as most of the existing 80 billion-plus database industry is built on dated relational architecture. Modernizing legacy applications has always been part of our business, and we have taken steps over the years to simplify and demystify this complex process through partnerships, education, and most recently, our Relational Migrator product. AI offers a potential step function improvement, lowering the cost and reducing their time and risk to modernize legacy applications. For that reason, earlier this year, we launched several pilots with our customers, where we worked with them to modernize mission-critical applications, leveraging both AI tooling and services. The early results from these pilots are very exciting, as our customers are experiencing significant reductions in time and cost of modernization. In particular, we have seen dramatic improvements in time and cost to rewrite application code and generate test suites. We see increasing interest from customers that want to modernize their legacy application state, including large enterprise customers. As a CIO of one of the world's largest insurance companies said about our pilot, "This is the first tangible return he's seen on his AI investments." While it's still early days, and generating meaningful revenue from this program will take time, we're excited about the results of our pilots and the growing pipeline of customers eager to modernize their legacy estate. Finally, I understand that there are a lot of questions about the current business conditions and the macro environment more broadly. So let me give you a sense of what we're seeing across the business. As a reminder, when thinking of the macro influence on our business, it's important to distinguish between consumption of existing workloads and new business. Starting with consumption of existing application on our platform, this is where we have historically seen a macro impact, as usage of applications impacted by the underlying business conditions of our customers. As we discussed on our last earnings call, in Q1, we did see broad-based consumption growth slow down, suggesting some macro softening. Our usage trends suggest a similar macro environment in Q2 as in Q1, even though Q2 Atlas consumption growth was modestly ahead of our expectations. Moving on to new business, we generally have not seen the macro environment impact our ability to win new business, and that was true in Q2 as well. We realize that this is different from what you hear from some other software vendors. Ultimately, software application development continues even in uncertain environments, as customers know they need to continue investing in internally developed software to run the business, as well as to drive competitive differentiation. In addition, we still have relatively low market share in a large market, which means we have an opportunity to gain share in any environment. Now, I'd like to spend a few minutes reviewing the adoption trends of MongoDB across our customer base. Customers across industries and around the world are running mission-critical projects on MongoDB Atlas, leveraging the full power of our developer data platform, including Fanatics, Occidental Petroleum, and Indeed. Fanatics Betting & Gaming, a division of the sports ecosystem company, Fanatics, leverages MongoDB to significantly enhance the user experience of their mobile app. Initially, the team launched a platform on Postgres, but faced challenges with scalability, flexibility, and excessive complexity. After migrating to MongoDB Atlas, the team also integrates Atlas Search to provide users with a better experience to find all available betting options. With Atlas handling, scaling, partitioning, and operations, developers can focus on writing code and improving the user experience. Looking ahead, Fanatics plans to continue to expand on MongoDB Atlas as they ensure they can operate at scale as they prepare for the start of the NFL season. L'Oréal, McKesson, and Nationwide Building Society are turning to MongoDB to modernize applications. L'Oréal's Tech Accelerator, a department dedicated to catalyzing digital innovation at L'Oréal, is utilizing MongoDB for an application designed to bring products and solutions to market while quickly improving employee efficiency. The team's previous database solution had limited out-of-the-box functionality and was unable to handle the complex calculations needed to retrieve and restructure large amounts of data from their data warehouse. L'Oréal migrated to MongoDB Atlas to streamline the application architecture and simplify a previously highly complex and time-consuming data access layer. With this migration, L'Oréal achieved a forty-fold performance improvement. On Atlas, the existing code is easier to maintain, more scalable, and more efficient, making life easier for developers. Mature companies and startups alike are using MongoDB to help deliver the next wave of AI-powered applications to their customers, including Delivery Hero, Generali, and Questflow. Delivery Hero, a longtime MongoDB Atlas customer, is the world's leading local delivery platform, operating in seventy-plus countries across four continents. Their quick commerce service enables customers to select fresh produce for delivery from local grocery stores. Approximately 10% of the inventory is fast-moving, perishable produce that can go quickly out of stock. The company risks losing revenue and increasing customer churn if the customer didn't have viable alternatives to their first choice. To address these risks, they are now using state-of-the-art AI models and MongoDB Atlas Vector Search to give hyper-personalized alternatives to customers in real time if items they want to order are out of stock. With the introduction of MongoDB Atlas Vector Search, the data science team recognized that they could build a highly performant, real-time solution more quickly and for less cost than alternative technologies. In summary, we had a healthy Q2 with both Atlas and EA exceeding expectations. We saw a strong new business quarter and improved sales productivity, and we're confident in our ability to keep winning new business in the second half of the year. Looking forward, we see great opportunity to help our customers modernize legacy applications and build the next generation of AI-powered applications. With that, here's Michael. Thanks, Dev. I'll begin with a detailed review of our Q2 results, and then finish with our outlook for the Q3 and full fiscal year 2025. First, I'll start with our Q2 results. Total revenue in the quarter was $478.1 million, up 13% year-over-year, and above the high end of our guidance. As a reminder, while we have difficult compares throughout fiscal 2025, we're facing a particularly difficult year-over-year comparison in Q2, given we had a number of large, multi-year partnership licensing deals in Q2 last year. Under 606 accounting rules, we recognized the license component upfront, which creates a difficult compare a year later. Shifting to our product mix, let's start with Atlas. Atlas grew 27% in the quarter compared to the previous year, and now represents 71% of the total revenue, compared to 63% in the Q2 of fiscal 2024 and 70% last quarter. We recognize Atlas revenue primarily based on customer consumption of our platform, and that consumption is closely related to end user activity of their applications. Let me provide some context on Atlas consumption in the quarter. First, as a reminder, in Q1, Atlas consumption growth was below our expectations, but we updated our growth assumptions for the remainder of the year. In Q2, Atlas consumption growth was modestly ahead of those updated expectations across the board. While this is encouraging, consumption growth is still below our original forecast from the beginning of the year. Turning to non-Atlas revenue. Non-Atlas came in modestly ahead of our expectations in the quarter, as we continue to have success selling incremental workloads into our existing customer base. On a year-over-year basis, non-Atlas revenue is down 13% due to the especially difficult compare I referenced earlier. Turning to customer growth. During the Q2, we grew our customer base by approximately 1,500 customers sequentially, bringing our total customer count to over 50,700, which is up from over 45,000 in the year-ago period. Of our total customer count, over 7,300 are direct sales customers, which compares to over 6,800 in the year-ago period. The growth in our total customer count is being driven primarily by Atlas, which had over 49,200 customers at the end of the quarter, compared to over 43,500 in the year-ago period. It is important to keep in mind the growth in our Atlas customer count reflects new customers to MongoDB, in addition to existing EA customers adding incremental Atlas workloads. Continuing on. In Q2, our net ARR expansion rate was approximately 119%. The decline versus historical periods is attributable to a smaller contribution from expanding customers. We ended the quarter with 2,189 customers, with at least $100,000 in ARR and annualized MRR, up from 1,855 in the year-ago period. Moving down the income statement, I'll be discussing our results on a non-GAAP basis, unless otherwise noted. Gross profit in the Q2 was $360.8 million, representing a gross margin of 75%, which is down from 78% in the year-ago period. Our year-over-year margin decline is primarily driven by a lower mix of high-margin upfront license revenue compared to last Q2, as well as Atlas growing as a percentage of the overall business. Our income from operations was $52.5 million, or an 11% operating margin for the Q2, compared to a 19% margin in the year-ago period. The primary reason for our more favorable operating income results versus guidance is our revenue outperformance. In addition, Q2 operating income benefited from the timing of certain marketing and other spend, which we now expect to incur in the second half of the year. Net income in the Q2 was $59 million, or $0.70 per share, based on 83.8 million diluted weighted average shares outstanding. This compares to a net income of $76.7 million, or $0.93 per share, on 82.5 million diluted weighted average shares outstanding in the year-ago period. Turning to the balance sheet and cash flow. We ended the Q2 with $2.3 billion in cash, cash equivalents, short-term investments, and restricted cash. Operating cash flow in the Q2 was negative $1.4 million. After taking into consideration approximately $2.6 million in capital expenditures and principal repayments of finance lease liabilities, free cash flow was negative $4 million in the quarter. This compares to free cash flow of negative $27.3 million in the year-ago period. In addition, this quarter, we also received $170.6 million in cash from the settlement of the capped calls associated with our 2024 convertible notes. I'd now like to turn to our outlook for the Q3 and full fiscal year 2025. For the Q3, we expect revenue to be in the range of $493 to 497 million. We expect non-GAAP income from operations to be in the range of $57 to 60 million, and non-GAAP net income per share to be in the range of $0.65 to 0.68, based on 84.6 million estimated diluted weighted average shares outstanding. For the full fiscal year 2025, we expect revenue to be in the range of $1.92 to 1.93 billion, non-GAAP income from operations to be in the range of $187 to 195 million, and non-GAAP net income per share be in the range of $2.33 to 2.47, based on $84.3 million estimated diluted weighted average shares outstanding. Note that the non-GAAP net income per share guidance for the Q3 and full fiscal year 2025 includes a non-GAAP tax provision of approximately 20%. I'll now provide some context around our updated guidance. First, because of the stronger than expected Atlas consumption in Q2, our starting Atlas ARR for the back half of the year is higher than we anticipated in May. As a result, we're raising our Atlas revenue forecast to reflect that higher starting point. We are not changing our underlying Atlas Q3 and Q4 consumption growth rate assumptions. Second, we are slightly increasing our EA assumptions for the rest of the year to reflect the strength of the second half EA pipeline. Finally, thanks to the performance in Q2 and the increased revenue outlook, we now expect a 10% operating margin at the midpoint of our fiscal 2025 guidance. We will continue investing to capture our long-term opportunity with a focus on our strategic priorities. Separately, although we don't provide guidance on cash flow, we wanted to call out two items that will impact fiscal 2025 cash flow, but benefit our long-term financial profile. In Q2, we started paying some of our cloud provider commitments upfront in exchange for better economics. We see this as a very low risk, high ROI use of our cash and one that will benefit our gross margin going forward. These prepayments will represent a negative impact to our operating cash flow in the back half of the year of roughly $20 million per quarter. In addition, in Q3, we will incur approximately $20 to 25 million of CapEx to acquire IPv4 addresses, which will allow us to further reduce our cloud infrastructure costs in the future. To summarize, we're pleased with our Q2 results and especially our ability to win new business. We have a small share of one of the largest and fastest-growing markets in all of software. The secular tailwinds at our back are getting stronger in the age of AI, and we're excited about the future. We'll continue investing judiciously and focusing on our execution to capture this long-term opportunity. With that, we'd like to open it up to questions. Operator? Thank you. As a reminder, if you would like to ask a question, please press star one one on your telephone. We also ask that you limit yourself to one question and one follow-up. As well, please wait for your name and company to be announced before you proceed with your question. One moment while we take the first question. And the first question today is gonna come from Sanjit Singh of Morgan Stanley. Your line is open. Yes, hi, thank you for taking the question, and congrats on Q2. Nice to see Mongo beating and raising again. Dev, I wanted to follow up on some of the operational changes you're making to the business that you announced last quarter. Just in terms of the update, in terms of realigning some of the sales incentives to drive higher workload quality and while maintaining some of that record workload growth that you saw last year. Could you sort of walk us through what the changes were you put in place, and how much confidence do you have that you will drive better workload growth as we get into early next year? Yeah, sure. So, first of all, thanks, Sanjit. Just a reminder for everyone, we made some slight incentive comp changes to really get our reps to focus, to have a little bit more balance on size versus volume of workloads acquired. These changes were well received by the field. We had a good workload quarter, as you just described. Workloads start small, so it's too early... While we're pleased with our results, obviously, it's too early to declare a victory, and to really see if this is gonna have a material impact and changes, but clearly, we're happy with what we've seen so far. Great. And then as a follow-up for Michael, yeah, I remember at the, you know, Q4 last year, you gave us the update on sort of the unused credit dynamics. As we start to think about the back half of this year, is there anything else that we should think about that. I mean, you just mentioned some of the cash flow impacts just now. I s there anything on sort of like the revenue side of the equation that we should keep in mind? I kind of noticed at the end of this year, there's this more holiday days in the quarter in Q4. Does that have an impact? Anything that we should be that you would like to call out in terms of our modeling when we think about expectations for Atlas more broadly going into the end of the year? Yeah, I think there are a few things to take into account that have been throughout the year, but of course, are reflected in the updated guide. Specifically on Atlas, throughout the year, we have, you know, tough compares, given the headwinds from the lack of the unused commitments. That's obviously hardest, you know, as the year goes on, that sort of number, you know, builds, so that makes for a tough year-over-year comparison. I think the other thing to think about in the context of Atlas is, you know, the ending year dynamic is really a compounding over the course of the year. As we talked about at the beginning of the year, we got off to a slower start, and some of the prior... Year workloads, those cohorts were growing at slower rates, and so that does affect and kind of compound over the course of the year. And so I think that's important to keep in mind, is factored into our guidance. And then looking at the revenue picture more broadly, you know, moving away from Atlas and thinking about, you know, EA, we've had throughout the year a headwind on EA, and we'll have that as a multi-year headwind in the back half as well. The only other things I think I would call out is, you know, we saw a slower seasonal rebound in Q1, and so we're expecting that slower seasonal rebound to, you know, occur in Q3 as well. And then, as you mentioned, Q4 is a seasonally weaker quarter. A ll those are some of the considerations to think about when you're thinking about the rest of the year. Appreciate the thoughts, Michael. Thank you. One moment for the next question. And our next question today will be coming from the line of Raimo Lenschow of Barclays. Your line is open. Hey, thank you. Two quick questions from me. Michael, on the EA, you kind of talked about, like, a slightly better pipeline in the second half. Can you talk a little about, is that kind of still the continuation of what we saw in Q2, Q3 last year, where people wanted to modernize their kind of self-service footprint ahead of the cloud to them, a move to the cloud, or what's the dynamic there? And then one for Dev, like, there's a big debate about, like, reference architecture on AI, and I think it's a little bit too early, but it comes up with investors a lot. Like, what are you seeing there? I know AI infrastructure, we're still in the early innings, but what are you seeing there in terms of people engaging with you? Thank you, and good to see you back on track. Thank you. Thanks, Raimo. On the EA question, I would say there are lots of reasons why we're seeing strength of EA. I wouldn't uniquely or exclusively tie it to, you know, AI. I think it's broadly, you know, in support and shows the strength of the Run anywhere strategy. The other thing that I'd call out is, you know, given the 606 dynamics as it relates to EA, we're always sensitive to sort of the multi-year aspect, and that's sort of what's, you know, provided, given the strength of multi-year in fiscal twenty-four, some of the tough compares here in fiscal 2025. I think what we've seen in terms of the pipeline is strength in EA broadly. So not just a multi-year phenomenon, but really sort of a volume phenomenon as well, that we're seeing when we kind of look out on the horizon, and that is reflected in the updated guide. Thanks, Raimo, on the question about AI. I think in terms of reference architectures, I think it's important to understand, and I said this in the prepared remarks, is that unlike most other workloads, AI-driven workloads really require the underlying database to be capable of processing queries against very rich and complex data structures, both quickly and efficiently. And MongoDB is well positioned to do that. You know, we can basically unify and handle source data, vector data, metadata, generated data from your LLM, right alongside your live operational data. And then as the performance of these LLMs and latency of these LLMs increase, accessing real-time data becomes really important. Like, say, you're calling and talking to a customer support chatbot, that you want that chatbot to have up-to-date information about that customer, so that they can provide the most relevant and accurate information possible. You know, there are some questions about LLMs, whether a general purpose LLM or a fine-tune LLM, what the trade-offs are. Our belief is that given the performance of LLMs, you're gonna see the general purpose LLMs probably win, and will use RAG as the predominant approach to marry you know, generally available data with proprietary data. And then you are starting to see things like advanced RAG use cases, where you get much more sophisticated ways to ask complex questions, provide more accurate and detailed answers, and better adapt to different types of information and queries. And so that's what we're seeing. I think it's a quickly evolving space, but we feel very good about our positioning for AI, even though it's still very early days. Okay, perfect. Thank you. Thank you. One moment for the next question. And our next question will be coming from Kash Rangan of Goldman Sachs. Your line is open. That's perfect. I was about to call Raimo and say: Can you please explain reference architectures? I'll buy you a nice glass of wine. So hopefully he'll take me up on that offer, 'cause that was a very technical question. Thank you. But anyway, coming back to the call here. Dev, a question for you. Why is EA doing so well? So you talked about a pipeline in the second half of the year. Last year, you had some significant wins for EA. We were supposed to be on this cloud journey, so definitely, Atlas has reached parity in many senses. It can support big scale applications, whatnot. Just curious to get your thought on why is EA still an important piece of the business? I suppose when you look at AI, could something surprise us? I know that you've had this view that we're building infrastructure first and then the platform, then applications. Could it be, by any chance, a different way to approach AI in this cycle and that we don't really need applications, but somehow these LLMs are going to be a perfect replacement for the way we think about old world applications? I'm just curious to see what the devil's advocate view might be if someone were skeptical of the whole AI applications build out on top of the infrastructure and platform. Thank you so much. Y eah, so, thanks, Kash. What I would just say is, you know, we did have a better than expected, both Atlas and EA quarter. There's no question about that. I don't wanna, you know, suddenly say there's some, you know, inflection point on EA in our business. I think, I would really, you know, attribute it to, one, better execution. And two, customers do really appreciate our Run Anywhere strategy. There's still lots of customers, either for regulatory reasons or other reasons, who want to run workloads on-premise, and, and they're not going away. I mean, we've been in this cloud journey for ten years, and some workloads are just very hard to move to the cloud, or some workloads for many customers don't make sense to work, you know, move to the cloud, at least not anytime soon. T he fact that they can, you know, build it on MongoDB and have the optionality to move it to the cloud later very easily, is something that's very compelling for customers. With regards to AI, I mean, we predominantly see most of the AI workloads in the cloud, but there are definitely lots of customers who are looking at using open source LLMs, in particular things like Llama, and running those workloads locally. Obviously, it means that they also have to have access to, you know, NVIDIA hardware like GPUs, but we do see some customers do that. Again, I wouldn't suggest that that's also an inflection point or cause for the EA outperformance. I think it's very, very early days, and most of those are experiments that customers are running. C learly, we feel really good about Run Anywhere strategy, and as we've said in the past, we are investing in our, you know, basically introducing search and vector search to our community product, and that will then show up in EA. So EA is definitely an area where we're also investing from a product point of view. Thank you. One moment for the next question. And our next question will be coming from the line of Tyler Radke of Citi. Your line is open. Hi, this is Tyler Radke. I think the question was for me. Couldn't hear the name, but thanks for taking the question. Dev, you talked about a Postgres displacement in the quarter, and I think that's the first time you've talked about that at least in recent quarters. So I was wondering if you could just sort of frame for us what use cases do you come across them? I know it is popular in terms of a SQL displacement for migrating off legacy applications. But if you could just frame for us sort of the competitive environment in Postgres both the open source stuff and some of the new you know venture-backed startups in the space. Thank you. Yeah, sure. So thanks for the question. Yeah, it's important to understand that Postgres has been around for almost forty years. I mean, it's Postgres, the name is turned from, you know, post-Ingres, so that technology has been around a long time. As you said, they're really the beneficiary of lift and shift from Oracle, SQL Server and MySQL, so they're kind of consolidating the relational market. In terms of why do we compete or why do we win, I would say it's a few things. One, our schema flexibility. You know, it's a very, you know, MongoDB has a very flexible schema, allowing you to store documents in a JSON-like format. So this is beneficial for application structures that, you know, evolve over time. We can horizontally scale, so we're make it very easy to distribute data across multiple servers or virtual servers. So it's for applications that require mass amounts of data. Performance of large data sets, you know, again, we can handle that better than Postgres. You know, the built-in sharding, so allows for automatic data distribution. You know, and then we also, I think, developer productivity, the JSON-like format and flexible schema can lead to faster development cycles, especially for customers who really work in agile environments. So we feel like we compete. Our win rates against Postgres are high. But again, there's lots of decisions being made where we're not party to, where people are just doing a lift and shift off a, you know, a legacy platform, or they're just they just wanna stay on relational because that's what they know. O bviously, it's our job to educate them on the benefits of MongoDB, but we feel good about our competitive position against Postgres. Thank you and a follow-up question for Michael: You talked about how consumption in Atlas in the quarter tracked a bit better than planned. Sounds like it was not a macro-related improvement. What do you think the driver that was, and are you seeing any improvement in some of the recently acquired workloads, those starting to ramp up better? Or maybe they have different seasonal patterns than you thought. Any color on sort of that driver of outperformance would be helpful. Thank you. Yeah, sure. I would say that yes, Q2 consumption growth was better than our expectations. That was great to see. I would describe it as within a reasonable or typical, you know, range of outcomes, and so there are no signs that we've seen that would specifically point to any material changes in the underlying macroeconomic environment, better or worse. We've certainly seen, you know, to your question on sort of the workloads and sort of some of the cohorting, we did see a little better performance there as well, and, you know, in line with what we saw, you know, elsewhere, but they're still below our original expectations. So I think that's probably the key couple things there. Thank you. Thank you. One moment for the next question. And our next question for the day will be coming from Brad Reback of Stifel. Your line is open. G reat. Thanks very much. Dev, on your commentary around the modernization pilots, how should we think about timing as that being a bit of a tailwind to the overall growth rate? Yeah. So, again, just to make sure everyone understands, you know, the legacy relational application market or database market is quite large. It's over $80 billion, and it's a massive opportunity for us. And since day one, since our IPO, we've been, you know, getting customers to migrate off relational to MongoDB. But one of the biggest friction points has been that while it's easy to move the data, it's, you know, you can map the schema from a relational schema to a document schema, and you can automate that. The biggest stumbling block is that the customer has to, or some third party, has to rewrite the application, which by definition creates more costs, more time, and in some cases, more risk, especially for older apps where the development teams who built those apps no longer exist. So what's been compelling about AI is that AI has finally created a shortcut to overcome that big hurdle. And so essentially, you can start basically diagnosing the code, understand the code, you know, recreate a modern version of that code, and generate test suites to make sure the new code performs like the old code. So that definitely gets people's interest because now all of a sudden, what may take, you know, years or multi years, you can do in a lot less time. And the pilots that we have done, the time and cost savings have been very, very compelling. That being said, we're in the very early days. There's a lot of interest. We have a growing pipeline of customers across, frankly, all parts of the world, from North America to EMEA and even the Pac Rim. And so we're quite excited about the opportunity. But again, I would say it's very early days, but there's a number of reasons why I would say that customers are very focused on this. What the cost of licensing and maintaining legacy apps is becoming too high to bear. In many cases, the regulatory and compliance requirements are forcing customers to upgrade. There's a whole end of life of critical technologies, notably Sybase, that's forcing customers to act. There's a ton of technical depth on these legacy platforms that limits the organization's flexibility to do things with AI. And candidly, customers have also soured on the traditional approach of using large, you know, systems integration projects that are very costly and take a long time. So this whole approach is definitely getting their attention. That's great. And then one fast follow-up. It feels like we've spoken about EA more than typical on this call, which is great. As we think about the back half pipeline, is the composition similar in so much as it's predominantly existing customers, or are you beginning to see an uptick in net new customers there as well? Thanks. Yeah, I would say that it's predominantly existing customers that are doing this, you know, who are maybe doubling down on EA and expanding the footprint to EA. There's and that's typically the driver for our EA business. Thanks very much. Thank you. Thank you. One moment for the next question, please. Our next question will be coming from Karl Keirstead of UBS. Your line is open. Okay, great. Hey, Dev, at the beginning of the call, you mentioned that Mongo's slow start to the year was, quote, "purely operational." But on the Q1 call, when you were describing what happened, you described it as very much a broad-based macro issue. So I'm curious, should I interpret that comment as you, Mike, and the team have done a bit of a rethink and might be changing, modestly, at least, your explanation about the Q1 results? Yeah, actually, just to be clear, I think just to make sure everyone understands, what we called out was that the consumption of existing workloads was broad-based. The slowdown was broad-based across both geos and channels. It was new business just got off to a slower start, so that was what we called out in our Q1 call. And with our Q2 call and results, as you can see, you know, new business performed better, as expected, than expected on both Atlas and EA, which is why we believe the Q1 issue was an operational issue. Q1 new business, sorry, was an operational issue, not a macro issue. The macro issue was all about the slowdown in consumption, because Q1 typically tends to be a seasonally strong quarter for us, and that didn't happen. Yeah, I think that's really important, Karl, just to keep in mind, when we talk about macro, it could have those two different effects, right? The new business piece and then the expansion of existing workloads. And so, what we were talking about, as Dev said in Q1, was the existing workload expansion. The operational piece was on the new business side. And I think the key thing that we've observed, really in a wide range of, you know, macroeconomic conditions in our almost seven years as a public company, is with the exception of that one quarter, we've been able to execute quite well in the new business opportunity, really in most environments, given that we have, you know, a huge market, you know, relatively low share, strong product, and a talented team that executes well. And so I think that's probably helpful just to understand as we're sort of using the terms, just to make sure we don't trip ourselves up. Yep. Okay, that's great. And then my follow-up for you, Mike, is: when you were pressed in prior questions about the second half, most of the variables that you brought up were frankly, you know, headwinds, things like tough compares. But- If I look objectively at your Q3 total revenue guide of $497 million, and this is my assumption, but I assume kind of a normal beat, that's going to result in sequential total revenue growth. That's actually the highest, I think, that MongoDB has ever put up. So, clearly, there's something good that you're embedding in that Q3 guide. What is that specifically? Yeah. So I'm not sure I'd follow all the math on the fly, and I'll be happy to follow up obviously, with any of that. But if I just think about the Q3 guide, I won't belabor the headwinds, but they exist, and we've sort of, you know, been through those, as you called out. But maybe to talk about the couple of positive things that we see that lead to sort of, you know, our improved outlook or increased revenue forecast for the balance of the year. I'd say it's really two things. In Atlas, it's reflecting the stronger than expected, you know, Q2, and therefore, the starting ARR at the beginning of Q3 is higher. Because we haven't seen any change in the underlying, you know, macro, the actual growth assumptions for Q3 and Q4, we have remain unchanged, and so you're supplying, you know, growth to a higher base. But that, you know, as the base keeps getting bigger and bigger, that, that does matter, and that flows through. And then secondly, was the positive impact of the increased strength in the EA pipeline for the second half of the year, and the impact on that revenue. So those would probably be the two things that I'd call out on the positive side of the revenue, in addition to, of course, having everyone keep in mind the tough compare and some of the headwinds we talked about. Okay, that's helpful, Mike. Thanks a lot. Thank you. Thank you, and one moment for the next question. Our next question will be coming from Jason Ader of William Blair. Your line is open. Yeah, thank you. I'm trying to understand the Q4 implied revenue guide, Michael. You know, just the implied sequential growth there is only 1.5% if I look at your full year relative to what you said specifically on Q3. That would be well below the historical seasonal pattern in Q4. So I just want to understand, is there something going on in Q4 that's different, just sequential? I understand the year-over-year is tough, but the sequential seem well below where you've normally been. And you know, is there something specific that we should think about there? Yeah, I think there are two things. So obviously, it sounds like you get the year-over-year, but just to make sure everyone's, you know, sort of on the same page, is making sure that people understand, you know, the tough compare, for Atlas, specifically around the unused commitments and then EA, the multi-year. And then more broadly, you know, we had one, we had less, growth in Q1, that compounds, and then also we talked about how we have, we're assuming, just in the same way that we saw in Q1, we're assuming less of a seasonal rebound in Q3, that has implications, for Q4. Gotcha. Okay. And then just, one quick follow-up on gross margins. Did you talk about Atlas gross margins in the quarter? And then, how material will the impact be from the prepayments and the IPv4, purchases on Atlas gross margins over time? Yeah, so we didn't specifically break out Atlas gross margin in the quarter, but you know, they continued to be lower. But obviously, we've pretty significantly shrunk the delta. That does explain some of the you know, comparison on the year-over-year basis. We didn't give specific guidance going forward. If you think about the two changes, you know, that we called out on the cash flow side, those will benefit us in terms of gross margin. There won't be a significant benefit in fiscal twenty-five, so we'll obviously talk about that more when we get to the fiscal twenty-six guide. But it's a very excellent use of our cash, and you know, good ROI in terms of improving those economics further. Thank you. Thank you. One moment for the next question, and our next question will be coming from Brad Sills of Bank of America. Your line is open. Oh, great. Thank you so much. Great to hear the continued strength in new workloads here. That's been very consistent theme here throughout all of this. I did wanna ask about some of the newer services like Vector and Stream Processing. You know, how are those contributing to the strength you're seeing in or sustained strength you're seeing in new workloads? Brad, thanks for the question. So, in terms of search, we're seeing solid momentum in search. We're having success with that business. It's starting to grow, and we just introduced a new capability called Search Nodes, which allows customers to optimize their search deployments by asymmetrically scaling, you know, specific nodes dedicated for search versus the rest of the nodes on their cluster. It also helps dealing with use cases that are very search-intensive. One of the largest gaming companies in the world replatformed their content moderation platform from DocDB, Elastic, and Dynamo to Atlas and Atlas Search, and using Atlas Search Nodes for workload isolation and high performance. On Vector, we're continuing to see growth and adoption, and we see Vector as effective in attracting new customers to the MongoDB platform. A world-renowned financial news organization, which was already running on Atlas, migrated from Elasticsearch to Atlas Search, using Search Nodes to take advantage of our vector search capabilities to build a site search that combines lexical search with semantic search to find the most relevant articles, you know, for user query. A European energy company built a geospatial search application using Atlas and Search and Vector Search, and the Atlas built on-prem but in two clouds to vectorize geospatial data and facilitate research and discovery. Then, we recently, you know, announced streaming or Stream Processing, I should say, you know, GA in. local, New York in May, and we've seen strong interest. It's still early days, but we're seeing interest from a variety of industries, ranging from automotive to retail to transportation, who are all who work with streaming data and wanted to be able to take actions on that data to, you know, drive their business. And so, you know, customers are very pleased with the performance of the product and how easy it is to use. But again, it's just early days since we just launched it, only in May. Wonderful. Great to hear. One more, if I may, please. On the last earnings call, you mentioned how the slowdown in consumption was broad-based across industries and workload types, which led you to believe that it was a macro-related impact. You know, with some of the improvement you've seen this quarter, I know it's early, but was that also broad-based, and could you deduce that maybe that might mean some improvement in the underlying macro, or was it more outsized to certain types of industries and services? Thank you. No, I, I would describe it as broad-based, Brad, but I would describe it within sort of a reasonable range of outcomes, and so no clear indication that macro's, you know, improving or deteriorating, and just a good quarter. Wonderful. Thank you. Thank you. One moment for the next question. Our next question will be coming from Rishi Jaluria of RBC Capital Markets. Your line is open. Wonderful. Hey, this is Rishi Jaluria from RBC. Two questions. Maybe, Dev, I wanted to first start out going back to some of what you talked about, which is the MongoDB versus Postgres debate. O ne of the kind of popular theories out there is, or debates out there, is which architecture is better suited to new generative AI applications, especially if we truly do believe AI will lead to a replatforming of software, similar to what we saw with the cloud. I know you talked a little bit about reference architecture earlier in Q&A, but maybe could you walk us through why you believe MongoDB is better suited to new generative AI-native applications versus Postgres? And then I've got a quick follow-up. Yeah, sure. So very quickly, the reason you know, we believe that we're well-positioned to win these new workloads is that AI-driven workloads require the underlying database to be capable of processing queries against rich and complex data structures. As you know, with AI, the data structures can be very, very complex. So this means that the data can be large and obviously not in any consistent size. MongoDB is designed to handle these different data structures, and I talked about, you know, we can help unify metadata, operational data, vector data, and generate data all in one platform. Relational databases, and Postgres is one of them, have limitations in terms of how they can handle different types of data. In fact, when the data gets too large, these relational databases have to do what's called off-row storage, and it becomes... It creates a performance overhead on these relational platforms. Postgres has this thing called TOAST, which stands for the Oversized-Attribute Storage Technique, and it's basically a way to handle these different data types, but it creates a massive performance overhead. So we believe that we are architecturally far better for these more complex AI workloads than relational databases, and we believe that ultimately we are the ideal data layer for AI applications. Obviously, it's early days. As I said, you know, we haven't seen a lot of inference workloads in production, but architecturally, we feel very good about our ability to compete against relational databases and Postgres in particular. That being said, Postgres is popular because they're the beneficiary of people who wanna stay on relational and who've kind of lived in relational for the last thirty, forty years. But head-to-head, we feel like we can, you know, win our share, share of business. Got it. Thank you. That's really helpful. And then maybe just sticking on the theme of AI, you know, we've talked before in the past that AI is just driving a lot of new code, making developers significantly more productive. Have you seen that behavior in any of your existing customers on Atlas, where maybe their utilization rate goes up or the number of applications built per customer goes up? Anything like that, that understanding it's super early, might at least give you some early indication that the increased developer productivity could turn into a real tailwind in terms of consumption of the underlying Atlas for you. Thank you. Yeah. So, this is a common question I ask our customers when I meet with them, in terms of what code generation tools are they using and what benefits they're gaining. The answers tend to be a little bit all over the map. Some people see 10%-15% productivity improvement, some people say 20%-25% productivity improvements. You know, some people say, "It helps my senior developers be more productive." Some people say, "It helps my junior developers become more like senior developers." So the answers tend to be all over the map. There's no question in my mind that with this platform shift, like previous platform shifts, the cost of building apps will come down. And so by definition, more apps will be produced, which will generate more data, which requires more databases. Now, obviously, we're in the early days, and much like, you know, I've lived through other platform shifts, like going to the internet. A lot of people built out these. You know, there's all this dark fiber that was built out to service all this potential demand. It didn't happen. People thought it was, maybe, you know, overinflated, and then before we knew it, the internet transformed the way we work, the way we live, the way we, you know, socialize. And so, I think that the same thing's happening here. I think, it's all on the come, but, but I think, you know, we're well-positioned for that opportunity. W onderful. Thank you. Thank you. One moment for the next question, and our next question will be coming from Brent Bracelin of Piper Sandler. Your line is open. Thank you. This is Brent Bracelin, Piper Sandler. Dev, I wanted to go back to Atlas, and the question here is, given all the moving parts here around accounting, tough compares, unused commitments, Atlas growth looked really strong. I think 30% + on a normalized basis after adjusting for unused commitments. That's before any benefit from AI. Can you just go back to the growth algorithm for Atlas here? I ask because 30% normalized growth would be 3 X faster than industry growth, implying a meaningful share capture of new software builds. So maybe it'd be worthwhile if you just go walk through what is driving the momentum on the Atlas side that is, again, two, three X faster than the industry? Well, what I would say is obviously, we're pleased with our results. What I would say is, one, Atlas is the most widely available cloud service by definition, because it runs across the largest three hyperscalers in 118 regions around the world. So no matter who you are, you know, you can run on Atlas almost anywhere in the world. Second, because MongoDB is a general purpose database, you can use us for almost any conceivable use case, so we're not limited to some narrow set of use cases or narrow set of users who have a very particular set of needs. That helps. Three, we have a large community of developers. We have millions of developers all around the world, from Asia to North America to EMEA, who are using MongoDB to address some problem. That also, obviously, because of the popularity of MongoDB, we are the world's most popular modern database. I think that also speaks to, you know, the strength of the product. Then I would say, you know, we try and execute well. Obviously, you know, we got off to a slower start than we liked in Q1, but we are very, very focused on execution. We have a really good team, both in terms of our go-to-market team, as well as our product and the supporting ecosystem teams, our partner team, engineering team. So we all, you know, try and put our heads down, and we were obviously disappointed by Q1, and we're really focused on growing the business as fast as we can. Perfect. And then, Mike, just a quick follow-up on op margins. Guidance implies 10% plus op margins in the second half, particularly as the revenue run rate here gets to $2 billion exiting the year. Can you continue to invest in sales capacity while balancing double-digit op margins at this scale? Yeah, so specifically around the second half, we've obviously increased the full year guide, and that flows through. We did talk about some of the timing issues between halves. We are incrementally on a marginal basis, investing in the back half of the year in our AI initiatives. But I think if you look at the two-year view, we're still making five hundred basis points, you know, of margin progress over the last two years. So yeah, I think it's a balancing act, Brent. I think the key thing is we have such a large, you know, opportunity and such attractive investment areas that we'll try and continue to do both. Helpful. Thank you. Thank you. One moment for the next question, and our next question will be coming from Eric Heath of KeyBanc Capital Markets. Your line is open. Hey. Hey, good afternoon. Thanks for taking the question. Just a couple of quick ones for me. Mike, was curious to get a better understanding on just maybe some of your assumptions on why you're expecting a slower than typical rebound, coming out of Q3. And then, Dev, thinking about the Q3 here and the Fed fiscal year-end, just what are some of your expectations for that vertical, which I assume is usually a big EA opportunity? And thanks. Yeah, so quickly, just on Q3, I think we're informed by our recent experience, including the fact that the seasonal rebound in Q1 of this year was slower than what we've typically seen, and so that's what we're taking into account when we think about Q3, and that's really what's driving it. Yeah, and on the... I think you said, if I heard you correctly, you talked about the FedRAMP. Public sector, yeah. The public sector and the FedRAMP. Right. In particular. Yes. I mean, obviously, their fiscal year ends in September. We have a good team there. We have FedRAMP Moderate, so we are well suited for workloads that have that requirement. We are not yet FedRAMP High certified, so that is something that we're working on as well, to try and expand the envelope of opportunities we can pursue. And as you implied, there's also an opportunity to sell EA to these customers, and we're doing that as well. Obviously, all that is baked into our guide for how we think about Q3 and the second half of the year, but we feel good about you know, about the opportunities in that segment. Thank you. This does conclude today's Q&A session. I would now like to turn the call back to Dev Ittycheria for closing remarks. Please go ahead. Thank you. And again, I wanna thank everyone for joining us today. We are pleased with our Q2 results and our continued execution against our large market opportunity. While the macro environment remains mixed, our ability to win new business remains strong across both Atlas and EA. And as we look ahead, we believe we are the ideal data layer for AI applications, and we continue to see increased demand from customers to modernize their legacy applications. And last but not least, we will continue investing judiciously and focusing on our execution to capture this long-term opportunity. Thank you for joining us today, and we'll talk to you soon. Take care. This does conclude today's conference call. You may all disconnect.