Thank you for standing by, and Welcome to MongoDB's Q3 FY 2024 Conference Call. At this time, all participants are in listen-only mode. After the speaker's presentations, there'll be a Q&A session. To ask a question at that time, please press star one one on your telephone. As a reminder, today's call is being recorded. I would now like to turn the call over to your host, Mr. Brian Denyeau from ICR. Please go ahead. Great. Thank you, Valerie. Good afternoon, and thank you for joining us today to review MongoDB's Q3 FY 2024 Financial Results, which we announced in our press release issued at the close of the market today. Joining me on the call today are Dev Ittycheria, President and CEO of MongoDB, and Michael Gordon, COO and CFO of MongoDB. During this call, we will make forward-looking statements, including statements related to our market and future growth opportunities, the benefits of our product platform, our competitive landscape, customer behaviors, our financial guidance, and our planned investments. 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 July 31st 2023, that was filed with the SEC on September 1st 2023. Any forward-looking statements made on 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 the most directly comparable GAAP financial measure. With that, I'd like to turn the call over to Dev. Thank you, Brian, and thank you to everyone for joining us today. I'm pleased to report that we had another strong quarter as we continue to execute well despite challenging market conditions. I will start by reviewing our Q3 results before giving you a broader company update. We generated revenue of $433 million, a 30% year-over-year increase and above the high end of our guidance. Atlas revenue grew 36% year- over- year, representing 66% of total revenue. We generated non-GAAP operating income of $79 million for an 18% non-GAAP operating margin, and we had another solid quarter of customer growth, ending the quarter with over 46,400 customers. Overall, we delivered a strong Q3. We had a healthy quarter of new business acquisition, led by continued strength and new workload acquisition within our existing customers. In addition, our Enterprise Advanced business again exceeded our expectations, demonstrating strong demand for our platform and the appeal of our Run Anywhere strategy. Moving on to Atlas consumption trends, the quarter played out in line with our expectations. Michael will discuss consumption trends in more detail later. Finally, retention rates remained strong in Q3, reinforcing the mission criticality of our platform, even in a difficult spending environment. This quarter, we held our most recent Global Customer Advisory Board meeting, where customers across various geographies and industries came together to share feedback and insight about their experience using MongoDB. From these discussions, as well as our ongoing C-suite dialogue with our customers, a few themes emerged. First, AI is in nearly every conversation with customers of all sizes. We're seeing great early feedback from our partners' partnership with AWS's CodeWhisperer, the AI-powered coding companion that is now trained on MongoDB data to generate code suggestions based on MongoDB's best practices from over 15 years of history. Microsoft's GitHub Copilot is also proficient at generating code suggestions that reflect best practices, enabling developers to build highly performing applications even faster on MongoDB. With the recent advances in GenAI, building AI applications is no longer the sole domain of AI or ML experts. Increasingly, it's software developers who are being asked to build powerful AI functionality directly into their applications. We are well positioned to help them do just that. We saw exceptional interest in our vector search public preview, and we announced general availability yesterday. Customers are building a range of AI use cases, from semantic search to Retrieval-A ugmented Generation, or RAG, where organizations can leverage the use of their private data to increase the accuracy of LLMs. For example, UKG, a human capital and workflows management technology, serves over 80,000+ customers around the globe, chose to use MongoDB Atlas Vector Search for an AI-powered assistant that helps guide their customers, employees, people, managers, and HR leaders. They chose Atlas Vector Search because of its minimal added architectural complexity, flexibility to handle rapidly changing data as applications evolve, and the scale to handle large workloads. UKG is not alone. In a recent State of AI survey report by Retool, Atlas Vector Search received by far the highest Net Promoter Score from developers compared to all other vector databases available in the market. Moreover, developers can combine vector search with any other query capabilities available in MongoDB, namely analytics, text search, geospatial, and time series. This provides powerful ways of defining additional filters on vector-based queries that other solutions just cannot provide. For example, you can run complex AI-enriched queries, such as, "Find pants, a shirt, shoes in my size that look like the outfit in this image within a particular price range and have free shipping," or, "Find real estate listings with houses that look like this image that were built in the last five years and are in an area within seven miles west of downtown Chicago with top-rated schools." Second, customers feel more pressure than ever to modernize their data infrastructure.... They are aware that their legacy platforms are holding them back from building modern applications designed for an AI future. However, customers also tell us that they lack the skills and the capacity to modernize. They all want to become modern, but are daunted by the challenges as they're aware it's complex, it's a complex endeavor that involves technology, process, and people. Consequently, customers are increasingly looking to MongoDB to help them modernize successfully. We launched Relational Migrator early this year to help customers successfully migrate data from their legacy relational databases to MongoDB. Now we're looking beyond data migration to the full lifecycle of application modernization. At our.local London event, we unveiled the Query Converter, which uses generative AI to analyze existing SQL queries and stored procedures and convert them to work with MongoDB's Query API. Customers already use the tool successfully to convert decades-old procedures to modernize their back-end with minimal need for manual changes. While it's still early days, we're continuing to invest in the Query Converter and other AI features with the goal of significantly reducing the effort involved in monetizing legacy applications to run on MongoDB. To be clear, application modernization will take time to ramp, but is one of the largest long-term growth opportunities for our business. Third, our Run Anywhere strategy continues to be a real differentiator, as customers greatly appreciate the optionality that our platform provides as they manage often conflicting priorities on the way to the cloud. On one hand, the movement to the cloud continues unabated. Customers in industries and geographies who are at first hesitant to move to cloud, such as financial services in Southern Europe, are now moving to the cloud with urgency to become more nimble and to reduce costs. Many of our customers find that the all-in cost of maintaining legacy workloads on-prem is higher than the cost of migrating them to the cloud. On the other hand, our largest enterprise customers tell us they are planning to maintain a meaningful on-prem footprint for the foreseeable future. The reasons for keeping workloads on-prem include regulatory requirements, the desire to keep using their existing on-prem infrastructure, or the enormity of the task of migrating all their apps to the cloud. In the meantime, they still want a modern data platform to deploy new and existing applications. The continued outperformance of our EA business demonstrates that our customers value our ability to run anywhere and to future-proof their eventual move to the cloud by building on EA. Finally, our customers remain focused on cost management. They are looking to do more with less by consolidating vendors and reducing the complexity of their data architecture. MongoDB dramatically increases developer productivity and supports a wide variety of use cases, eliminating the need for many point solutions. This combination resonates with customers in this macro environment. For example, Atlas Search now powers the homepage of one of the most recognizable sports media brands in the world. The customer replaced an incumbent search technology with Atlas Search because they were drawn to the operational ease of running search queries alongside other queries on Atlas, as well as the overall cost savings from consolidating functionality onto a single platform. In short, customers view MongoDB as a true partner, a partner that not only accelerates the pace of innovation, but also drives them to become more efficient. We are deepening investments in our product, partnerships, and customer-facing teams to continue to enable customers to do both. Now, I'd like to spend a few minutes reviewing the adoption trends of MongoDB across our customer base. Customers across industries around the world are running mission-critical applications on Atlas, leveraging the full power of our developer data platform. These customers include AT&T, Fishbowl by Glassdoor, and Trend Micro. AT&T selected Atlas as a key element of their modernization journey. The location management application validates 380 million unique customer addresses and handles about 14 million transactions per day, but their various disparate data management solutions led to technical debt, and there were duplicative sources of information. The company turned to Atlas as a developer data platform to simplify their data infrastructure, merge their data into a single view, and free their teams from managing database operations. Now they rely on Atlas Change Streams to easily track changes with data, as well as Atlas's native search capabilities and built-in Geospatial functions to quickly identify location information and accelerate time to market for mission-critical products and services. EY, Delivery Hero, and Asap Log are examples of customers turning to MongoDB to free up their developers' time for innovation while achieving significant cost savings. One of the 2023 MongoDB Innovation Award winners is EY. Ernst & Young LLP manages high volumes of transactional data, and its clients and internal teams work under strict timelines to file taxes and meet regulatory deadlines. The cloud-based Global VAT Reporting Tool, or GVRT, automates and digitizes the preparation of 242 different types of returns across 79 countries. EY migrated from their previous non-relational database solution to Atlas and experienced a significant performance boost, reduced costs by as much as 50%, and are able to scale without limitations to handle increased data volumes, transaction loads, and concurrent user requests during peak periods. Evernorth Health Services, a division of the Cigna Group, Manulife, and Playvox, are turning to MongoDB to modernize applications. Manulife, one of the largest life insurance companies in the world, migrated to Atlas when it became clear that their relational database caused a drag on innovation and increased the time to bring new digital products to market. Manulife selected Atlas because the flexible document model speeds up development, scales easily, supports asset transactions, and offers seamless data migration. Using Atlas Device Sync, they successfully launched one critical app's offline mode to ensure uninterrupted app usage when offline or in low connectivity areas to improve mobile data synchronization. Using Atlas allows Manulife to broaden its digital capabilities and enhance the personalization of customers' interactions cost-effectively. In summary, I'm pleased with our Q3 results. Our Run Anywhere strategy allows customers flexibility over where they deploy, and MongoDB is emerging as a platform of choice for their AI-powered applications, and customers are using MongoDB to modernize and become more efficient. Before I turn it over to Michael, I'm excited to share that Ann Lewnes, the former Chief Marketing Officer and Executive Vice President of Corporate Strategy and Development at Adobe, just joined MongoDB's Board of Directors. Ann held leadership roles at Adobe from 2006 to 2023. She was instrumental in driving Adobe's transition from a perpetual to a subscription-based business model, and has experienced marketing to creative professionals, whether they are in a small agency, a medium-sized business, or a very large enterprise. If you replace creative professionals with developers, this strategy is very similar to what MongoDB is doing, and Ann did it at the next level of scale. Prior to Adobe, Ann held a variety of leadership positions at Intel during her 20-year tenure at the company, including Vice President of Sales and Marketing. We are thrilled for the exceptional perspective Ann will bring to the board. With that, here's Michael. Thanks, Dev. As mentioned, we delivered a strong performance in the Q3, both financially and operationally. I'll begin with a detailed review of our Q3 results, and then finish with our outlook for the Q4 and full FY 2024. First, I'll start with our Q3 results. Total revenue in the quarter was $433 million, up 30% year-over-year, and above the high end of our guidance. As Dev mentioned, we continue to see a healthy new business environment, demonstrating our product market fit and the mission criticality of our platform. Shifting to our product mix, let's start with Atlas. Atlas grew 36% in the quarter compared to the previous year and represents 66% of total revenue, compared to 63% in the Q3 of FY 2023 and 63% last quarter. As a reminder, we recognize Atlas revenue primarily based on customer consumption of our platform, and that consumption is closely related to end-user activity of the application, which can be impacted by macroeconomic factors. Let me provide some context on Atlas consumption in the quarter. Week-over-week consumption growth in Q3 was in line with our expectations and stronger than Q2. As a reminder, we were expecting a seasonal uptick in consumption in Q3 compared to Q2, based on what we had experienced and shared with you last year. We had forecast that seasonal improvement to be less pronounced this year compared to last year, given that overall, we've seen less consumption variability this year, and that is exactly how the quarter played out. Turning to non-Atlas revenues, EA exceeded our expectations in the quarter as we continue to have success selling incremental workloads into our existing EA customer base. Ongoing EA strength speaks to the appeal and the success of our Run Anywhere strategy. The EA revenue outperformance was, in part, a result of more multi-year deals than we had expected. As a reminder, the term license component for multi-year deals is recognized as upfront revenue at the start of the contract, and therefore includes term license revenues from future years. Turning to customer growth. During the Q3, we grew our customer base by approximately 1,400 customers sequentially, bringing our total customer count to over 46,400, which is up from over 39,100 in the year ago period. Of our total customer count, over 6,900 are direct sales customers, which compares to over 5,900 in the year ago period. The growth in our total customer count is being driven primarily by Atlas, which had over 44,900 customers at the end of the quarter, compared to over 37,600 customers in the year-ago period. It is important to keep in mind that the growth in our Atlas customer count reflects new customers to MongoDB, in addition to existing EA customers adding incremental Atlas workloads. During the quarter, we moved approximately 350 accounts, representing negligible ARR, out of our self-serve customer account because they're better classified as subsidiaries of other customers, or they are now users of our free tier. Taking that into account, our self-serve net additions and overall net additions remain consistent with our historic healthy trends. In terms of our direct sales net additions, new sales activity remains healthy. Our reported direct sales net adds continue to reflect the dynamics we discussed last quarter, related to leveraging cloud provider marketplaces to fulfill new direct sales customer additions and the movement of some small mid-market direct sales accounts to self-serve. Moving on to ARR. We had another quarter with our net ARR expansion rate above 120%. We ended the quarter with 1,972 customers, with at least $100,000 in ARR and annualized MRR, which is up from 1,545 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 Q3 was $335.3 million, representing a gross margin of 77%, which is up from 74% in the year ago period. Our year-over-year margin improvement is primarily driven by improved efficiencies that we are realizing in Atlas. Our income from operations was $78.5 million or an 18% operating margin for the Q3, compared to a 6% margin in the year ago period. Our strong bottom line results demonstrate the significant operating leverage in our model and are a clear indication of the strength in our underlying unit economics. The primary reason for our operating income results versus guidance is our revenue outperformance. In addition, our operating income benefited from the timing of new hires. Finally, Q3 benefited from the timing of marketing programs, internal events, and other expenses, which we now expect to incur in Q4. Net income in the Q3 was $79.1 million or $0.96 per share, based on 82.7 million diluted weighted average shares outstanding. This compares to a net income of $18.7 million, or $0.23 per share, on 80.4 million diluted weighted average shares outstanding in the year ago period. Turning to the balance sheet and cash flow. We ended the Q3 with $1.9 billion in cash, cash equivalents, short-term investments, and restricted cash. Operating cash flow in the Q3 was $38.4 million. After taking into consideration approximately $3.5 million in capital expenditures and principal repayments of finance lease liabilities, free cash flow was $35 million in the quarter. This compares to negative free cash flows of $8.4 million in the Q3 of FY 2023. I'd now like to turn to our outlook for the Q4 and full year FY 2024. For the Q4, we expect revenue to be in the range of $429 million-$433 million. We expect non-GAAP income from operations to be in the range of $35 million-$38 million, and non-GAAP net income per share to be in the range of $0.44-$0.46, based on 83.2 million estimated diluted weighted average shares outstanding. For the full year FY 2024, we are increasing our outlook across the board. We now expect revenue to be in the range of $1.654 billion-$1.658 billion, non-GAAP income from operations to be in the range of $236.3 million-$239.3 million, and non-GAAP net income per share to be in the range of $2.89-$2.91, based on 82.5 million estimated diluted weighted average shares outstanding. Note that the non-GAAP net income per share guidance for the Q4 and full FY 2024 includes a non-GAAP tax provision of approximately 20%. I'll now provide some context on our guidance. First, we expect Q4 Atlas consumption growth to be impacted by the seasonal slowdown around the holidays. Second, as you think about both sequential and year-over-year revenue growth of Atlas in Q4, keep in mind that in Q4 last year, we had $several million more of revenue coming from unused commitments, which we do not expect to occur this quarter. Third, as a result of our strong execution so far this year, we are again raising our non-Atlas revenue expectations for Q4. However, we expect that our non-Atlas revenues will decline sequentially, Q4 versus Q3. This is different from our normal pattern, as we usually see a seasonal uptick in Q4 due to greater renewal activity. The reason for the sequential decline this year is because of the strength we've seen in Q3, including the benefit of multi-year EA deals. Finally, thanks to the strong performance in Q3 and the increased revenue outlook, again, we are again increasing our assumption for operating margins in FY 2024 to 14% at the midpoint of our guidance, an improvement of more than 900 basis points compared to FY 2023. Our significant margin improvement this year is primarily driven by our revenue outperformance and the fact that we didn't increase our pace of investment as the revenue outlook improved until relatively late in the year. As a result, we achieved greater margin expansion this year than we think is desirable in the short term, given the long-term market opportunity ahead of us. To summarize, MongoDB delivered excellent Q3 results in a difficult environment. We're pleased with our ability to win new business and are demonstrating the operating leverage inherent in our model. While we'll continue to monitor the macro environment, we remain incredibly excited about the opportunity ahead, and we'll continue to invest responsibly to maximize our long-term value. With that, we'd like to open up to questions. Operator? Thank you. Again, ladies and gentlemen, if you'd like to ask a question, please press star one one on your telephone. Again, to ask a question, please press star one one. We do ask that you please limit yourself to one question and a follow-up. One moment for our first question. Thank you. Our first question comes from Sanjit Singh of Morgan Stanley. Your line is open. Thank you for taking the questions, and congrats, congrats on the results in Q3. When we look at the Atlas growth this quarter, Michael, I know you mentioned that the consumption trends were, you know, better than expectations. In terms of the seasonality that you were anticipating and that what has shown up in the business in the past two years, was that more pronounced than you expected, or did that come in below in terms of the seasonal uplift that you've seen in Q3? Yeah, so just to clarify, Q3 for Atlas came in line with our expectations. We had seen and called out last year, seasonality for Q3. We had expected that, and incorporated that into our forecast. What we have seen is less variability over the course of the year, and so we assumed that that Q3 seasonality would be more muted this year, and that's exactly what happened and how the quarter played out. Oh, understood. Thank you, Michael, for the clarification. And the Dev, I guess a much bigger picture question. You know, it's. I think the company was founded in 2007, so it's about 17 years into the journey. And if you compare that to some of the, you know, large incumbents of the players in the space, like an Oracle, around this time, you know, 17 to kind of 20 years in, they started to move away from, like, the data management, database space and into, like, the application software market. Is that a vision, particularly as we're in the dawn of this sort of new compute cycle with AI, is that an analogy that applies to Mongo in terms of its long-term roadmap in, in your view? Yeah, thanks for your question, Sanjit. What I would say is, you know, we've been very clear that we're really pushing our developer data platform strategy, and we think the market is way larger today than it was for Oracle when they were essentially 17 years old. And our developer data platform strategy is really very simply enabling the developers to use MongoDB for a wide variety of use cases across a wide variety of deployment models, whether it's on-prem, on the cloud, multi-cloud, or even at the edge. And so that's really our strategy. We don't see any need to get into, quote, unquote, "the application space itself," and we think that we have a lot of runway ahead of us. I appreciate it thoughts, Dev. Thank you. Thanks, Sanjit. Thank you. Thank you. One moment, please. Our next question comes from the line of Raimo Lenschow of Barclays. Your line is open. Thank you. Congrats for me as well. I wanted to ask on EA first. Another very strong quarter there. Can you talk a little bit more on the drivers there? Because I do seem to remember you kind of doubled down on sales capacity. I think it was junior sales guys that you wanted to put on existing accounts. Is that kind of a main driver, or is it more like modernizations are kind of picking up a lot more than what we thought would be possible? Can you speak to that, because it's like the Q2 in a row where we kind of have better numbers there. And I have one follow-up for Michael. Yeah, so Raimo, with regards to our EA outperformance, I think it really speaks to a Run Anywhere strategy, where customers really value the ability to build on MongoDB and for essentially future-proof their deployment model, whether to stay on-prem, also move to the cloud, or move from one cloud to another cloud. And the fact that they can do that without having to rewrite the application is very compelling for customers. As you also said, a lot of customers still, especially the largest customers, still have a lot of sunk costs, and they wanna leverage that—their existing data infrastructure. So a lot of customers have told us that they will still deploy infrastructure on-prem for the foreseeable future. but by building on MongoDB, they get the benefits of a modern platform and the optionality to also move to the cloud when they're ready to do so. Yeah, the other thing, which I know you know, Raimo, but just for the broader audience, you know, we run the business on a channel basis. Sales isn't oriented around, you know, products. And then also, as we've said before, EA tends to be the additional sales of EA tend to be to existing customers. We don't tend to land a ton of new, brand new customers on EA. Okay, perfect. And then the follow-up is more, it's around AI. So, if I look at the demos that you guys have around vector search and how search is getting a lot better, that seems very compelling, and it seems like really straightforward for a client to improve the customer experience, if they use it for a customer-facing app, for example. What are the implications for growth margins for you, Michael? Like, you know, do you have to do a lot more compute there to be able to handle it? How should we think about that in terms of extra revenue, but then also extra cost coming through? Thank you. Yeah. So I, I think it's a little too early to tell. There's obviously plenty of variability, you know, in the workloads, depending on the nature, you know, of what the underlying, you know, application is. So I think it's a little early to give a strong, you know, direction to that. I think more broadly on margins, we've, we've certainly been very happy with the margin progress that we've made. I referenced the, you know, continued efficiencies that we're driving in Atlas. You know, Atlas is roughly two-thirds of the business, so as that continues to increase, you know, Atlas still is lower margin, you know, overall. And so that will have some impact, you know, over the next several years, but we're really pleased on the margin front. I think too early to make a specific call or quantification on the gross margins impact of AI. Yeah, and Raimo, just to add to that, one of the announcements we also made was that you can now do Workload Isolation. So for search or Vector Search functionality, you can scale those nodes independently of your overall cluster. So what that really does is allow customers to really configure their clusters to have the right level of performance at the most efficient cost. So we've been very sensitive about making sure that based on the different use cases, you can scale up and down different nodes based on your application needs. So by definition, that would be a very compelling value proposition for customers. Okay, perfect. Thank you. Thank you. One moment, please. Our next question comes from the line of Karl Keirstead of UBS. Your line is open. Great, thanks. Maybe I'll direct this question to Dev. Dev, I think a lot of people on the line are hearing this refrain about customers, enterprises wanting to, quote, "get their data estates in order" in advance of moving forward on AI initiatives. And you even spoke about customers feeling pressured to modernize their data infrastructure. I'd just like to ask where we are in that journey. Is this a conversation that your sales teams are having, or do you feel like this is actually beginning to result in deals and revenue pull-through? And if it isn't yet, roughly when do you think that might start to translate to an actual revenue lift? Yeah, so I'll make a couple points. Karl, you're absolutely right. There is a lot of focus on data, because with AI, data, in some ways, becomes the new code. You can train your models with your proprietary data that allows you to really drive much more value and build smarter applications. Now, the key thing is that it's operational data, because with applications, this data is always constantly being updated, and for many customers, most of those applications are right now running on legacy platforms, so that operational data is trapped in those legacy platforms. And you can't really do a batch process of ETLing all that data into some sort of warehouse and then still be able to leverage the real-time use of that data. That's why customers are now much more interested in potentially modernizing these legacy platforms than they ever have before. I would say, Karl, to your second part of your question, I would say it's still very, very early days. We definitely believe that this will be one of the largest long-term opportunities for our business, but you know, we're in the very early days, and as I've said in the past, there's a risk of overestimating the impact in the short term, but underestimating the impact in the long term. We definitely think this is a long-term impact. Okay, great. And if I could ask a follow-up to Mike on a different subject. Mike, you had talked on the last call a little bit more about this mix shift away from multi-year Atlas commits, and you were pointing to that as a reason for some of your metrics, like DR, and I think even cash flow, to come under a little pressure. This quarter, I see, DR is still under pressure. Cash flow was a little bit better. Can you maybe revisit that phenomenon and describe how it's impacting some of these metrics? Yeah, a couple of things. As we've said from the beginning, some of those, like, calculated billings or Deferred Revenue metrics, you know, aren't super helpful or don't provide a ton of insight in terms of how we run the business. We've also talked about how, you know, over the last couple of years, one of the things we've been trying to do is reduce friction for the sales force. Some of that includes reducing the emphasis around upfront commitments. And so that helps accelerate, you know, landing new workloads and things like that, and that will flow through or does flow through the financial statements, you know, as less upfront, Deferred, and things like that. And so, but allows us to sort of, you know, synthetically, you know, cover more ground from a sales force perspective. And so you do see that, you know, continuing to go through. We shared the statistic last quarter that, you know, the Atlas revenue growth last quarter was 38%, but dollars of committed Atlas declined 15% year- over- year, just as one way to try and help dimensionalize it. We also talked, I think earlier in the year, about how roughly 80% of Atlas doesn't flow through deferreds. And so I think all of those data points help kind of line up to explain the rest of what you're seeing and why that's not sort of a helpful forward-looking metric like it might be in other companies. It doesn't kind of give you the insight that maybe people are used to or hope that that will provide. Yep, that's clear. Thanks a lot. Thanks, Karl. Thank you. One moment, please. Our next question comes from the line of Brad Reback of Stifel. Your line is open. Great. Thanks very much. Michael, maybe following up on that last question and your commentary. At what point should DR stop being a headwind from, you know, a financial perspective? When should it stabilize or is this a multi-year trend as you kind of bleed it down? Yeah. So I'd say there are a couple things. Obviously, it's not something we guide to. It's not a key thing that we focus on, but I think the trends will be, you've got sort of two factors. One is overall Atlas mix, right? And so to the extent that Atlas continues to grow, that will provide a headwind, you know, on this dynamic. And then similarly, even within the current Atlas footprint, there's this historic commitments that we need to run through renewal cycles and everything else, and so I think this will take a little while still to play out. Great. And then switching gears, Dev, as customers begin to trial, excuse me, some of these Copilot AI code tools, we'll say, what type of feedback have you gotten from them as it relates to the pace at which they've been able to reduce net new workload time to market? How much faster or efficient are customers getting using these tools? Yeah, you know, we get different answers from a lot of different customers. It really depends on which tool they're using. Without commenting on who's better, who's worse, we definitely see a difference in the quality of the output between the different tools. I think it's gonna take some time for these tools to mature. So I think you're seeing a lot of customers do a lot of testing and prototyping. I would also tell you that they're doing a lot of this on internal-facing applications because there's still lots of questions about IP rights and what is potentially copyrightable, then ultimately licensable if they offer this as a, you know, shrink wrap software or service to their end customers. So we're seeing more of this work on internally facing applications. But the productivity gains really do vary by tool and also by the sophistication of the app being built. So it's hard for me to give you a real number. I know there's people out there quoting 30 or 40% improvements, but it really depends on the customer and the use case and the tool that they're trying to use. So it'd be hard for me to give you a specific number. Okay, thanks very much. Thank you. Thanks, Brad. Thank you. One moment, please. Our next question comes from the line of Tyler Radke, Citi. Your line is open. Yeah, thanks for taking the question. So earlier this quarter, you hired Mark Porter's replacement, Jim Scharf, from AWS, who, you know, has a lot of experience in the database industry. Can you just talk about some of his priorities, what you're kind of accelerating in terms of the product roadmap, to sell to larger enterprises? Yeah. So, for those people who don't know Jim's background, he spent about 17 years at AWS. He had a variety of roles. The last two, you know, meaningful roles was he ran the DynamoDB business at AWS, which is AWS's fastest growing and largest non-relational database business. And then he ultimately took over their identity access management business, which, if you think about it, every AWS customer has to use. So it's a service that has to not only perform, but perform at massive scale. The fact that he's dealt and built two mission-critical services for AWS was very appealing to us, given our ambitions to kind of... and the level of scale that we expect our business to ultimately get to at some point in time.... He obviously, you know, brings us very strong technical DNA. He obviously has a lot, lot of network of relationships in the industry, so we expect him to help us grow the team around the world, leveraging his relationships. And in terms of priorities, I mean, right now, he's still kind of really assessing the current state of the business. He's been quite impressed with the quality of talent that we have, but he's really kind of what I, you know, what I'd encouraged him to do was, you know, we need to go slow to go fast. So take his time in terms of really understanding the business, understanding the team, understanding the code base before he starts really prioritizing what to do. And it's not like there's some things massively broken. It's really helping us set up to scale to the next level. Great. And a follow-up for Michael. I know you talked about how Atlas consumption during Q3 was in line with your expectations. I'm just curious, given there were a lot of volatility in at least the equity markets and the economy, was there any more variability within the quarter? You know, in other words, did it start weaker and stronger? And then, I'm just curious, throughout the month of November, you know, have things kind of further improved ahead of the holiday seasonality? Just any additional color would be helpful. Thank you. Yeah. So as Dev said, Q3 Atlas results were in line with our expectations. There was, you know, a seasonal benefit to Q3 relative to Q2. But given the fact that we've seen less variability in consumption in FY 2024, we had expected that to be smaller than it was in FY 2023, and that's exactly how it played out. The seasonal improvement as it relates to Q3 is a little bit more in the back half of the quarter. As it relates to Q4, typically the back half is weaker given the holiday slowdown. And so hopefully, that helps people understand a little bit. Thank you. One moment, please. Our next question comes from the line of Kash Rangan of Goldman Sachs. Your line is open. Hey, yeah, thank you very much, Dev and Michael. Happy holidays. Congrats on the results. So going into calendar 2024, how does the management team feel relative to going into calendar 2023 with respect to how macro conditions are no longer impacting, or maybe they are impacting, some aspects of the business? Any verticals that stand out that you feel particularly excited about? So just wanted to understand the, how MongoDB is therefore fitting into customer priorities as you get into 2024. Thank you so much. Hey, Kash. Thanks for the question. I think compared from last year, this year, we don't see things getting worse, but we don't see things getting better. Where I said last year, with the Fed raising rates, you could really sense that people were getting much more cautious, and, and it was, there was probably more negativity in terms of the outlook coming into calendar 2023. So that being said, you know, we definitely see innovation being a priority for our customers. We clearly are—I would say the distinction between must-have and nice-to-have are clearly in the first category, but customers are also, as I mentioned in the prepared remarks, you know, remain focused on, on being sensitive to costs and ensuring that any investments they make have a high ROI. So we feel that we're well positioned. In terms of use cases or segments, I would say in general, you know, there's no real kind of material change in any across any vertical industry or geography. We do see. I mean, we were at re:Invent last week, and, you know, we had an amazing set of conversations with lots of senior-level customers. I think we're really viewed as a mission-critical platform by all our customers, and I think people view us as a platform that they can bet on long term. And so we see less, I would say, focus on, like, point solutions and more about, like, trying to leverage MongoDB for more and more use cases. And I would say that that's pretty consistent across, you know, industries and geographies. Yeah, the only other thing I'd add, Kash, is, you know, clearly things have stabilized. We, you know, are not guiding FY 2025, but just, you know, looking out, there's clearly a difficult EA and non-EA compare that, you know, people should sort of keep in mind. And I think the big assumption or the big, you know, determiner will be people's macro outlook in terms of how that affects, you know, the FY 2025 numbers. But those are probably the key things to keep in mind. Thank you. One moment, please. Our next question comes from the line of Ittai Kidron of Oppenheimer. Your line is open. Thanks. Hey, guys, nice numbers. Michael, I want to go back to one of the comments in your prepared remarks. I think you talked about how you expect non-Atlas business to be down quarter over quarter in the Q4, because I think the Q3 had multiple multi-year deals. Correct me if, if I've got this wrong. I, I guess my question is: Why would that affect 4Q unless there was a pull forward also, and not just multi-years? Is there a pull forward element from 4Q into 3Q in your non-Atlas business? No, it's not about a pull forward. It's just when you take into account the 606 impact of a multi-year deal, you wind up recognizing a lot of upfront license revenue. And so when you think about what that means on a sequential basis, you see the difference of the delta there. ... Got it, helpful. And then Dev, for you on the- I think the only other thing, Ittai, just for people is, given the strength that we've seen of EA throughout the year, but including Q3, we effectively, you know, raised our outlook, if you will, in Q4, in part given the strength of EA. Even though we don't guide, you know, to product, you can, you know, Atlas was in line with our expectations. EA outperformed in Q3, and our full year, you know, raise was more than the beat in Q3, and I think that shows the kinda continued strength of EA. Got it. Helpful. And then, Dev, on vector search, I know this is kind of fresh out of the oven here, but maybe you can talk about the opportunity here on a per customer basis. How do I think about the dollar potential here? And is there one common vendor out there that you expect to see more in competition for those types of use cases? Yeah. So let me start with the second question first. I would say that, I think, you know, 6-9 months ago, there was a lot of interest in vector databases, and there were some point solutions that got a lot of name recognition, and a lot of people were wondering, is there a risk, you know, that we could be disrupted by them? And at that point in time, we made it clear that we believe vectors were really another form of an index, and that every database platform would ultimately incorporate vectors into their architecture. And the winner really would be the technology that made the vector functionality very integrated and cohesive as part of the developer workflow. I would argue that that's really played out. As I said in the prepared remarks, there was a recent analysis done by a consultancy firm called Retool that really spoke to lots of customers, and we came out on top in terms of NPS. And by the way, our product was a preview product. It wasn't even the GA product. We've seen a lot of demand from customers, and we feel like this is a big, big opportunity. Again, it's early days. You know, it's gonna take time to materialize, but this is, again, one of the other big growth opportunities for our business. That being said, in terms of the revenue opportunity, it's really hard to quantify now because the use cases that customers are starting with are still kind of, I would say, early and developmental, we, you know, because people are still playing around with the technology. But we are seeing, you know, as I mentioned, you know, UKG is using it to essentially provide a AI-powered assistant for its people. You know, one European energy company is using has terabytes of geospatial data and is using, you know, vectors to basically get better insights in terms of the images that they're getting from the, you know, the work they're doing in terms of drilling for oil. So it's still very, very early days, so hard to give you, like, exact numbers. Even today, even in our general, you know, non-AI workloads, the workload variety can vary a lot depending on the customer, the number of users, the amount of data. So I think it's gonna be similar to, you know, our core business, which is that it just really depends on the use case. Very good. Appreciate it. Thank you. Thank you. One moment, please. Our next question comes from the line of Brad Sills of Bank of America. Your line is open. Oh, great. Thanks so much. Wanted to ask a question around the, the customer count greater than 100K. It looks like a real nice result this quarter. Is there any change going on there in terms of the trajectory or the path for customers to get to that level? In other words, are they starting bigger? Are they landing bigger, or are they just getting to that point faster? And, and what would be driving those two things? Yes, I'm glad you called that out, Brad. Yeah, we're, I think we added 117 100K customers this quarter, which is the largest add, I think, in the company's history. What I think it really speaks to is that customers are increasingly viewing MongoDB as a mission-critical platform. They're gonna run more and more workloads on MongoDB. So by definition, it's rare that one workload on its own will drive that kind of revenue. So the multiple workloads, you know, and really viewing us as a standard part of their infrastructure stack is what's really driving that number, and we're obviously happy to see the results of that. And we think that that's just indication, as I said earlier, where people are consolidating onto a few vendors. They recognize that we offer broad support for a broad set of use cases. We are truly a general-purpose, mission-critical platform, and that their developers really love using MongoDB. Wonderful to hear. And then one more, one more, if I may, please. On the commentary around, you know, customers viewing Mongo as that platform. With some of these newer workloads besides search, like Relational Migrator, you know, Atlas Streaming, do you-- are you finding that that receptivity for customers who want to run, you know, search within, you know, one single solution, is that also the case for streaming and relational? Just trying to get a sense for, you know, those cycles and how those might ramp on that platform capability. Thank you. Yes. So, actually, yeah, one of the reasons we actually built Search is because we got feedback from our customers. In many instances, a lot of our customers were dual-homing data to MongoDB and to some sort of search database. So consequently, not only had to manage two databases, keep that data in sync, but also manage the plumbing that connected those two database platforms. And customers told us they said, like: We don't understand why you're not offering a solution, because we'd much rather, you know, have it all on one platform with one API. And that ultimately drove our desire to build out our search functionality, which is, you know, really becoming more and more popular. The point for customers is that if you can remove friction in terms of how they can use the platform, leverage the platform, have one set of kind of semantics in terms of to address a broad set of use cases, it really simplifies the data architecture, and the more you simplify data architecture, the more nimble you can be and the more cost-effective you can be. I think that's what's really resonating with customers. Thanks so much, Dev. Thank you. One moment, please. Our next question comes from the line of Rishi Jaluria of RBC. Your line is open. Oh, wonderful. Thanks so much for, for taking my question. Maybe I want to start by diving a little bit into Relational Migrator. Dev, I know you said it's definitely early days, but where you are seeing usage of it, maybe can you give us a little bit of color? What sort of workloads are these that customers are, are utilizing the tool for? What does kind of that timeline look like? Any color you can give there in terms of early adoption would be really helpful, then I've got a quick follow-up. Yeah. So, again, as you can imagine, given the, you know, lot of these legacy platforms have been around for between 30-40 years, a lot of people have a large repository of legacy apps. And, you know, migrating off a legacy platform to another platform does require some work. It requires, you know, essentially three things: One, you have to map the schema of the old platform onto the new platform, you then have to map, move the data, and then you have to rewrite the application code. And, those three things took some time. So we heard feedback. When we took the company public, you might remember that 30% of our net new business at the time went public, was actually Relational Migrator. So customers were undertaking that heavy lifting because they were in such pain and wanted to move to a more modern platform. But clearly, you know, that pain can basically be a bitch, a bit of a tax on switching costs. And so essentially, we built tooling based on feedback from customers to start automating the schema mapping and the data movement. Now, with the availability of Gen AI, you can also now start automating the code generation associated with rebuilding or rebuilding an application. Essentially, rather than think about just, you know, moving the app, you know, you know, in one lock step, we can actually break down a monolithic relational app into microservices and start cleaving off different parts of the services first, so it can be a much more efficient and also more ROI, a quicker ROI on some of the investments we're making. So there's a big, big opportunity here for us to do that. But again, I want to be very clear, you know, we view this as a, a long-term growth opportunity. We're still in the very early days. We've got some really interested customers who are doing some interesting things in working with us on pilots. Our engineering and product and field teams are really focused on this, but we're in the very, very early days of really automating, you know, Relational Migrator to the next level, leveraging GenAI. All right. Wonderful. That's, that's really helpful. Then I wanted to ask about MongoDB Serverless. I know this is something you've, you've kind of had, at least been talking about for, for a while. Given a lot of the, the concerns around cloud optimization and rationalization and, you know, customers overpaying and having to figure out how to optimize their footprint, it feels like that could be a natural tailwind for, for MongoDB Serverless, especially because you were early to embrace it. Can you talk a little bit about, what you're, what you're seeing in terms of adoption there, how we should be thinking about that opportunity, and, and, and maybe just kind of what, what this could look like over the next several years in terms of serverless adoption versus traditional consumption adoption in, in Atlas? Thanks. Yeah. So just to be clear, when we talk about serverless, basically what we're, what customers think about is that they don't have to start thinking about capacity planning, that the workload can scale up and scale down based on the needs of whatever the use case is and what the compute and other resource needs are. So there's been a lot of interest from customers. You know, at first stage, it was a lot of ephemeral workloads where they didn't want to go provision a dedicated cluster. They wanted to be able to leverage our serverless functionality. We think long term, that almost every workload will become serverless, because over time, that'll be the way most applications are provisioned. But we're in the early days, and the receptivity and use of our serverless serverless functionality has been very high. And you're right, it's for those legacy platforms that they can't offer similar solutions, MongoDB becomes that much more attractive because a development team and architecture team doesn't have to worry about capacity planning. They can just build the app, and they know in the background, our infrastructure can scale up and down as their usage, you know, as their usage goes up and down. Well, wonderful. Really helpful. Thank you. Thank you. One moment, please. Our next question comes from the line of Brent Bracelin of Piper Sandler. Your line is open. Brent Bracelin, your line is open. Oh, hi, guys. This is Hannah on for Brent. Thanks for taking my question. Just one from me. Subscription gross margins remained above 80% for the second straight quarter, even with that continued mix shift to Atlas. I know you mentioned efficiency improvements to Atlas, but are we at a structural point, Michael, where the scale of gross margins can remain at that 80%+ range into the next year? Yeah. So, what I would say is I do not think. I think if you think about it, Atlas gross margins continue to be lower than Enterprise Advanced gross margins. And while we're very pleased with the 80% margin performance, you know, on a subscription margin basis in Q3, Atlas is quote, unquote, "only" two-thirds. And so, you know, there is still a delta between the two, and so, you know, I think that, that will have a slightly dilutive effect, on margins as Atlas increases as a percent of overall revenue. ... Okay, makes sense. Thank you. Thank you. One moment, please. Our next question comes from the line of Patrick Colville of Scotiabank. Your line is open. Hi, this is Joe Vandrick on for Patrick Colville. As of 3Q, it looks like about 29% of direct sales customers are spending over $100K on the platform. Just curious where you think that percentage can trend over the longer term and kind of how big the opportunity is within these existing direct sales customer accounts. Thanks. Yeah, Joe, I would say that, you know, we still believe that we have a very small percentage of wallet share in most accounts, and so obviously, the smaller the customer, the bigger the wallet share. But in most direct sales customers, our percent of wallet share is still quite small, so we see a big opportunity there. And as we talked about in terms of our new business, a big part of our new business came from acquiring new workloads with existing customers, and that is a big focus for our go-to-market teams. And the runway is, you know, quite long for that trend to continue. Great. And just one more for me. I mean, you kind of touched on this, but what's the feedback been from those customers who've used vector search, you know, in preview? And then obviously with vector search comes quite a bit more data. So, how are you making sure that the customers don't receive, you know, a surprise bill and end up unhappy? Yeah. So, as we mentioned earlier, the feedback on our vector search has been very high. Even when it was in public preview, we were getting a lot of feedback. And then we saw this report that came out. Obviously, we don't talk to, you know, customers who are using alternatives. We just talk, focus on our own customers. But, it was, you know, we're pleased to see that out of all the products available in the marketplace, our own preview product had the highest NPS score. So then if you unpack that, why do customers like using MongoDB? Because it's one tightly integrated solution. You can tightly integrate capturing vector data, metadata, and then data regarding, you know, the particular use case, and that becomes very, very attractive. It just becomes much more seamless and easier to use versus either using point solutions or some kludgy, you know, solution that's been put together. So I think that's a big reason about how we remove friction from a developer's workflow and why, you know, the MongoDB approach makes it so much better to you know, to use than say any other alternative approach. In terms of your question around, you know, the amount of data and the data bills, obviously, vectors can be memory intensive, and, the amount of vectors you generate will obviously drive the amount of usage, on those nodes. That's one of the reasons we also introduce dedicated search nodes, so you can asymmetrically scale particular nodes of your application, especially your search nodes, without having to increase the overall size of your cluster. So you're not, you know, to your point, socked with a big bill for underlying usage, for non-usage, right? So you only scale the nodes that are really need that incremental compute and memory versus nodes that don't, and that becomes a much more cost-effective way for people to do this. And obviously, that's another differentiator from MongoDB. Got it. Thank you. Thank you. Okay, so that is all the time that we have today for today's conference. I'll just turn the call back over to Dev Ittycheria, CEO, for any closing remarks. Thank you. I appreciate everyone joining the call today. Again, I just want to reiterate that we had another strong quarter new business performance, validating the value proposition of our developer data platform and our Run Anywhere strategy. We are seeing strong momentum on our AI strategy, especially Atlas Vector Search, which is emerging as a best-in-class solution for building powerful AI applications. And we continue to help customers drive greater efficiency while also accelerating their pace of innovation. So with that, I, I appreciate your time, and we'll talk to you soon. Take care. Thank you. Ladies and gentlemen, this does conclude today's conference. Thank you all participating. You may now disconnect.