Good evening. Thank you for attending today's MongoDB fourth quarter FY 2022 earnings call. My name is Selena, and I will be your moderator. All lines will be muted during the presentation portion of the call, with an opportunity for questions and answers at the end. If you would like to ask a question, please press star one on your telephone keypad. I would now like to pass the conference over to our host, Brian Denyeau with ICR. Please go ahead. Thank you, Selena. Good afternoon, and thank you for joining us today to review MongoDB's fourth quarter fiscal 2022 financial results, which we announced in our press release issued after the close of the market today. Joining 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, 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 those related to the ongoing COVID-19 pandemic and its impacts on our business, results of operations, clients, and the macroeconomic environment. They cause actual results to differ materially from our expectations. For a discussion of these, the material risks and uncertainties that could affect our actual results, please refer to the risks described in our SEC filings, including our most recent quarterly report on Form 10-Q. Any forward-looking statements made in this call reflect our views only as of today, and we undertake no obligations to update them. 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. Thanks, Brian. Thank you to everyone for joining us today. I will start by reviewing our fourth quarter results before giving you a broader company update. Looking quickly at our fourth quarter financial results, we generated revenue of $266 million, a 56% year-over-year increase and above the high end of our guidance. Atlas revenue grew 85% year-over-year, representing 58% of revenue. We had another strong quarter of customer growth, ending the quarter with over 33,000 customers. The fourth quarter marked another major milestone as we crossed 1 billion in annualized revenue run rate. Crossing over the 1 billion mark five years after reaching the annualized 100 million mark is clear evidence of the value MongoDB's application data platform offers customers large and small all over the world. Our excellent fourth quarter performance was broad-based. We saw success in nearly every industry, geography, and customer type. It was powered once again by the ongoing strength of Atlas. We also saw an uptick in sales for Enterprise Advanced, which speaks to the popularity of MongoDB regardless of where our technology is deployed. Customer net additions remained robust, especially in our direct channel, where Q4 marked a new record. It is expected that hundreds of millions of new applications will be developed over the next few years as most organizations now recognize that a competitive advantage has to be built rather than being bought with off-the-shelf software. The core reason for our success is that in an era where there's an urgency to build compelling modern applications, MongoDB reduces the friction and cost of working with data, which is the biggest challenge developers face. However, the developer experience of working with data has become increasingly complex. The technologies and mechanisms of working with data have continued to get more fragmented as there has been a proliferation of specialized and niche data technologies, each designed to solve a slice of a growing set of necessary data use cases. The hyperscale cloud providers are reinforcing this by taking a bag-of-tools approach by introducing many proprietary point solutions. This approach pushes complexity onto developers to wrangle these data technologies in their applications and develop workarounds to address scalability and performance. The complexity created by this data sprawl impedes the speed of innovation, adds cost, and effectively becomes a direct business risk. MongoDB's application data platform takes a radically different approach to liberate the developer from the unnecessary data complexity to accelerate innovation. First, our platform removes enormous friction in how a developer works with data. Instead of requiring developers to work with inflexible data models, MongoDB is built on the document model, which is aligned to the way how developers think and code. The document model not only allows developers to build applications faster, but to also easily make changes in response to business conditions or customer feedback. Second, our application data platform enables developers to focus on the needs of the business as opposed to working around the constraints of their data infrastructure. MongoDB abstracts away all that complexity through an architecture that is designed to address the vast majority of use cases. Instead of having to deal with numerous point solutions, customers can use our tightly integrated platform that offers a unified and seamless developer experience. Third, our platform is designed to meet the most demanding requirements for performance and scale. Unlike other solutions that struggle scaling beyond a few nodes in a few regions, MongoDB's application data platform can enable anyone to provision a globally distributed and persistent data platform anywhere in a matter of minutes with just a few clicks of a button by virtue of being available on 80+ regions across AWS, Azure, and GCP. Perhaps the best evidence that our platform is resonating in the marketplace is in the growth of our customer base. We ended the year with over 33,000 customers, of which over 1,300 are six-figure customers and 164 are million-dollar-plus customers, the latter number growing nearly 70% year-over-year. This level of customer adoption is reflective of our popularity around the world as well as our value as a general purpose rather than a niche technology. To provide a small sampling of how MongoDB is used across different industries, in financial services, MongoDB is used for a trading platform, global payment data store, a digital end-to-end loan origination and servicing solution, general ledger system of record, regulatory risk, treasury, and for many other back-office processes. In the retail sector, MongoDB is used for single view, real-time product catalogs, hyper-personalization, recommendation engines, AI-driven customer engagement, inventory and supply chain management, including sensor tracking and omni-channel user experiences. In the telecom industry, MongoDB is used to enable smart home services, Internet of Things, media streaming, call routing, endpoint management, real-time fulfillment, AI-based fraud detection, and advanced billing and payment services. These are a few examples of how MongoDB is being used. We also do extensive work in the healthcare, manufacturing, gaming, oil and gas, and many other industries. We continue to be excited about the future and the massive opportunities in front of us. Businesses across all industries will continue to invest heavily in software as a means to differentiate themselves, to seize new opportunities, and to respond to new threats. While this has been happening aggressively over the past decade, we are still only in the early stage of this movement. As infrastructure becomes more advanced, with chips getting more powerful, algorithms getting smarter, and networks getting faster, the capability for innovation only increases. Powerful software powered by real-time data will empower experiences and business models we cannot even conceive of today. Future applications will need to be incredibly responsive, increasingly global, and require strong distribution data to the edge or across the world. However, there is still a dearth of development talent to meet this demand. Consequently, organizations will invest in technologies that allow developers to go faster by offering an integrated suite of data capabilities to build smarter applications. In fiscal 2023, we'll continue to build on our momentum and advantages in the marketplace. In product, we'll continue innovating to enhance the value of our platform. Our high win rates and strong broad-based performance gives us confidence to continue to rapidly scale our sales organization as we remain fractionally penetrated in the $70 billion+ market. In marketing, we see a great opportunity to elevate our brand and our value proposition to the voice of our customers who are doing remarkable things with our platform across different industries and geographies. Finally, we'll continue investing in our people, processes, and systems to support rapidly scaling our company. Now I'd like to spend a few minutes reviewing some customer wins and interesting use cases from the fourth quarter. Ultrafast grocery delivery pioneer, Getir, has revolutionized last-mile grocery delivery with its 10-minute grocery delivery proposition, making thousands of everyday items available within minutes. The company has built its core grocery delivery platform on MongoDB community and migrated to Atlas. Getir achieved superior performance and reliability and also relied on Atlas' always-on multi-region clusters for a 99.995% uptime during its critical U.S. launch. One of the largest North American banks chose MongoDB as its modern database standard to fuel monetization, improve uptime, and power a highly available, always-on, secure customer experience for the bank's 10 million retail customers. The bank runs over 200 applications on MongoDB across digital, capital markets, consumer lending, risk, and payment divisions. Use cases span mainframe offload, operational data store, single view of the customer, time series, caching, real-time analytics, mobile, and content management. Società Generale d'Informatica, or SOGEI, is an information technology company operated by the Italian Ministry of Economy and Finance. It recently chose MongoDB as the application data platform for a government initiative that mandates citizens to present a digital or paper certificate to show whether they have been vaccinated, tested negative, or recovered from COVID-19. Called the Green Pass project, the program grants access to activities like restaurant dining, museums, cinemas, amusement parks, and more. SOGEI was able to generate 150 million certificates in less than 45 days with MongoDB. Content cloud company, Box, empowers more than 100,000 businesses globally to revolutionize how they work by securely connecting their people, information, and applications. Box's content ingestion solution, Box Shuttle, leverages MongoDB Atlas to accelerate a customer's migration to the cloud. Box wanted a FedRAMP-ready, multi-cloud managed cloud database to support high throughput and horizontal scale by sharding large datasets. One of the largest supermarket chains in the United States selected Atlas and Atlas Search to power its enterprise promotions engine. The engine gives customers immediate access to promotions and coupons while shopping at any one of its thousands of stores across the U.S. With Atlas Search, the company was able to modernize its data structure so that developers can make more updates more quickly and use multi-dimensional array lookups to run 5 million queries per day faster. Insulet Corporation is an innovative medical device company dedicated to simplifying life for people with diabetes. Insulet's flagship product, Omnipod, is the first tubeless automated insulin delivery system that is helping people with diabetes lead better lives. Insulet migrated to MongoDB Atlas to reduce costs while simplifying the complexity of mission-critical database management, configuration, upgrades, and scale without business interruption while having HIPAA, PII, and PCI compliance protection. In summary, we had another excellent quarter. We are seeing continued strong momentum because we're solving one of the most important problems impeding innovation, namely the challenges of working with data. We are more optimistic than ever about our prospects, and we'll continue investing and executing to capture the large market opportunity ahead of us. With that, here's Michael. Thanks, Dev. As mentioned, we delivered another strong performance in the fourth quarter, both financially and operationally. I'll begin with a detailed review of our fourth quarter results and then finish with our outlook for the first quarter and full fiscal year 2023. First, I'll start with our fourth quarter results. Total revenue in the quarter was $266.5 million, up 56% year-over-year. Subscription revenue was $258.2 million, up 58% year-over-year, and professional services revenue was $8.3 million, up 17% year-over-year. It was a very strong quarter across the board, and we exceeded our expectations for both Atlas and Enterprise Advanced. Overall, Atlas's strong performance continues to be the largest contributor to our growth. Atlas grew 85% in the quarter compared to the previous year and represents 58% of total revenue, compared to 49% in the fourth quarter of fiscal 2021 and 58% last quarter. On a sequential basis, this quarter's strong Atlas revenue performance was driven in part by the exceptionally high in-quarter expansion of existing customers that we experienced and previously called out in Q3. Simply put, strong in-quarter expansion benefits not just the revenue in the completed quarter, but also the revenue in the following quarter because the new quarter starts with a higher beginning run rate. In Q4, we experienced strong in-quarter expansion of existing customers that was in line with historical trends versus the exceptionally high growth rates we experienced in Q3. Enterprise Advanced had a particularly strong quarter. An important driver of the strength of EA is the success we are seeing in our large, high-potential accounts. As a reminder, we provide incremental resources to some of our most promising customers in order to accelerate the adoption of MongoDB. A number of these high-potential accounts are primarily using EA, and we had a strong new business quarter with them in Q4. During the fourth quarter, we again grew our customer base by over 2,000 customers sequentially, bringing our total customer count to over 33,000, which is up from over 24,800 in the year ago period. Of our total customer count, over 4,400 are direct sales customers, which compares to over 3,000 in the year ago period. As a reminder, our direct customer count growth is driven by customers who are net new to our platform, as well as self-serve customers with whom we've now established a direct sales relationship. The growth in our total customer count is being driven in large part by Atlas, which had over 31,500 customers at the end of the quarter, compared to over 23,300 in the year ago period. It's 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. We had another quarter with our net ARR expansion rate above 120%. We ended the quarter with 1,307 customers with at least $100,000 in ARR and annualized MRR, which is up from 975 in the year ago period. As Dev mentioned, we ended the year with 164 customers with at least $1 million in ARR and annualized MRR, which is up from 98 in the year ago period. The continued strong growth in our $100,000 and $1 million-plus annualized spend is an indication of the success of our land and expand strategy and the fact that we're increasingly becoming a strategic platform for our customers. Moving down the income statement, I'll be discussing our results on a non-GAAP basis unless otherwise noted. Gross profit in the fourth quarter was $196.6 million, representing a gross margin of 74%, which is up from last quarter and up from 72% in the year-ago period. Our loss from operations was $1.3 million or a negative 1% operating margin for the fourth quarter compared to a negative 9% margin in the year-ago period. Our outperformance versus our operating loss guidance was primarily driven by our revenue outperformance. Net loss in the fourth quarter was $6.3 million or $0.09 per share based on 67 million weighted average shares outstanding. This compares to a loss of $19.9 million or $0.33 per share on 60.5 million weighted average shares outstanding in the year-ago period. Turning to the balance sheet and cash flow. We ended the fourth quarter with $1.8 billion in cash equivalents, short-term investments and restricted cash. This quarter, we saw strong sequential growth in deferred revenue driven by the strength of Enterprise Advanced, given EA contracts are predominantly billed annually in advance. As we've discussed in the past, Q4 is the seasonally strongest quarter for our EA installed base. As a reminder, in Q3, we noted that our deferred revenue benefited from several very large Atlas early renewals. We did not see a similar impact in Q4, but would like to reiterate that some of those large deals that renewed early in Q3 were originally scheduled to renew in Q1. Operating cash flow in the quarter was positive $22.3 million. After taking into consideration approximately $5.5 million in capital expenditures and principal repayments of finance lease liabilities, free cash flow was positive $16.8 million in the quarter. This compares to negative free cash flow of $20.7 million in the fourth quarter of fiscal 2021. For the full fiscal year 2022, we had positive operating cash flow of $7 million and negative free cash flow of $6.7 million. While we have had positive operating cash flow quarters before, this is the first full year in our company's history that we generated cash from operations. I'd now like to turn to our outlook for the first quarter and full fiscal year 2023. Please note that the guidance provided for fiscal year 2023 includes certain refinements to our non-GAAP financial measures for expenses related to stock-based compensation to more accurately depict the underlying business results each quarter. For comparative purposes, we've provided a historical reconciliation of these updated measures in our earnings release. For the first quarter, we expect revenue to be in the range of $263 million-$267 million. We expect non-GAAP loss from operations to be $5 million - $2 million, and non-GAAP net loss per share to be in the range of $0.12 -$0.08 based on 67.7 million weighted average shares outstanding. For the full fiscal year 2023, we expect revenue to be in a range of $1.151 billion-$1.181 billion. For the full fiscal year 2023, we expect non-GAAP loss from operations to be $22 million-$7 million, and non-GAAP net loss per share to be in the range of $0.51-$0.29 based on 68.7 million weighted average shares outstanding. Our strong guidance for fiscal 2023 reflects our underlying confidence in our market opportunity and our ability to deliver strong growth at significant scale. Let me provide some incremental context around our guidance. In Q1, at the midpoint of our guidance, we expect to see a slight sequential revenue decline as Q1 is typically a lower new business quarter for Enterprise Advanced than Q4. As a reminder, EA revenue recognition under ASC 606 is disproportionately affected by the upfront term license component. In addition, as we've discussed in the past, Atlas sequential growth in Q1 is lower compared to other quarters, driven by seasonal factors impacting consumption, most notably the fact that there's simply fewer calendar days in Q1 than in other quarters. Let me also discuss how we are factoring the impacts of the COVID-19 pandemic into our fiscal year 2023 guidance. First, unlike in fiscal 2021 and fiscal 2022, we do not assume any impact of the pandemic on our revenue performance in fiscal 2023. Despite the ongoing uncertainty related to the pandemic, our performance over the last two years gives us confidence in our ability to execute in this environment. In other words, our guidance reflects that we have more confidence operating in the current environment than in either of the last two years. Second, on the expense side, our guidance anticipates the normalization of travel, event, and office expenses as COVID-19 restrictions continue to relax. We had previously expected a normalization in the second half of fiscal 2022, but the spread of the Delta and Omicron variants delayed our return to office plans and reduced employee travel. As a result, our travel, event, and office expenses in fiscal 2022 were only modestly higher than in fiscal 2021 and well below our initial expectation. However, we now expect normalization starting in Q2, and we anticipate an incremental $45 million-$55 million in travel, event, and office expenses in fiscal 2023. To summarize, MongoDB delivered excellent fourth quarter results. We continue acquiring new customers at a strong pace, and our revenue growth is a testament to the breadth of platform adoption and our increasing strategic importance to our customers. We remain convinced that we're in the early innings of pursuing our large market opportunity. With that, we'd like to open up to questions. Operator? Thank you. If you'd like to ask a question, please press star followed by one on your telephone keypad. If for any reason you'd like to remove that question, please press star followed by two. Again, to ask a question, press star one. As a reminder, if you are using a speakerphone, please remember to pick up your handset before asking your question. We will pause here briefly as questions are registered. The first question comes from Kash Rangan with Goldman Sachs. Please go ahead. Much congratulations on the quarter. I just want to clarify the seasonality comment, Michael, that you made with respect to Atlas. We're merely talking about it sequentially only because Atlas is a much larger business today than it was exactly a year ago going into a Q1. Or are we actually calling out any structural changes in consumption that underlie that forecast? I also have a follow-up question. Thank you so much. Yeah. What we're talking about, and we called this out last year, is that Q1 for Atlas is seasonally lower because of the fewer calendar days in the quarter. It's a consumption-based model, and just obviously you need days in order to consume, and Q1 has fewer of those days. The overall cohort behaviors, as evidenced by the Q4 numbers, are very strong, and we feel good about the underlying patterns. Got it. Consumption as a structural change driver of your Atlas business is still less positive as you felt before. Yeah. No change. No change. Got it. Yeah. One for Dev. When you look at the cohort of Atlas customers, initial deployments generally small. But then, what are some of the bigger deployments on Atlas looking like that rival the more traditional on-prem deployments that give you the conviction that some of the biggest database deployments on the planet could end up being completely cloud native and might surprise us two to three years from now? Thank you so much. Yeah. Thanks, Kash. I would say just I'd point to the seven-figure customers. The majority of those customers are on Atlas today. We have, you know, large customers and actually even cutting-edge startups who are, you know, running mission-critical workloads. For startups, it's probably their entire business on Atlas. For large customers, they're running mission-critical workloads. Atlas is not just for small workloads. This has happened now for a number of years. We're seeing enterprises increasingly get comfortable with moving mission-critical workloads to the cloud. One of the benefits of moving to MongoDB is that you get real optionality of not just starting on-prem and moving to the cloud, but going from one cloud provider to another. We're seeing strong interest, and I think we have the customer proof points to give people confidence to really move mission-critical workloads to Atlas. Tremendous. Thank you so much. Thank you. Thank you, Kash. The next question comes from Sanjit Singh with Morgan Stanley. Please proceed. Oh, thank you for taking the question. My congrats to the team on another exceptional year. Dev, you mentioned that you went from $100 million to $1 billion in five years, which is really incredible. I've been thinking about how you [audio distortion] Hey, Sanjit? -to $2 billion. Hey, Sanjit, we're having trouble hearing your question. It's coming across very muffled. Can you Apologies. I apologize, Dev. That was my headset. So the question is essentially like, as you scale beyond $1 billion, going from $1 billion-$2 billion, does anything in the sort of how you go to market, how you organize the business change versus how you got to $1 billion? You know, typically in prior sort of ramps of software companies, there's been a bit of a hiccup scaling past $1 billion. As this business crosses $1 billion, how do you feel about your ability to scale to, you know, $2 billion and beyond over time? Sure. You know, we've constantly always tried to stay ahead of where the business is in terms of anticipating changes to our go-to-market model. I mean, as you can imagine, in the early days, we had one model, which is a direct sales force, really trying to sell to everyone. Then we introduced an inside sales team, then we introduced self-serve, then we introduced the notion of having focus teams on high-end accounts. We introduced the notion of removing friction from the initial selling process to get customers on our platform more quickly. We're always refining our go-to-market motion and in anticipation of one, how big this market is, and we try to meet customers where they are versus trying to force them to engage with us in one way. You'll see us continue to do that. We're gonna be focused on increasing verticalizations. As I mentioned in the prepared remarks, we're seeing a lot of traction in key vertical industries. We're developing a deep degree of competence around those industries. We've been having a team focused on solutions marketing for a number of years to particular industries, and you're gonna see us organize our sales teams more over time with a vertical orientation. You'll also see us going after what we call digital natives, which are kind of fast-growing mid-market customers who are building software, not just buying software. They will obviously see a lot of value from MongoDB. You can see us continue to push the envelope in terms of innovation, and I would argue that we have the best sales organization in enterprise software. Well, plenty of opportunity ahead. It sounds like a lot to look forward to. Michael, on the guidance, you did a really great job of sort of contextualizing how you're approaching guidance this year versus last year, particularly on the element of COVID. I guess I sort of just have to ask, you know, just given the geopolitical environment that we're in, particularly with exposure, potential exposure to Russia and Eastern Europe, and then we also have this element of, you know, higher oil prices and what that can do for the macro environment more broadly. To what extent did you sort of incorporate those factors into this year's guidance, understanding that, you know, COVID looks hopefully, knock on wood, largely behind us? Yeah. Thank you. Obviously, we try and be thoughtful and transparent in the guidance. That said, we don't have a crystal ball for what's gonna happen geopolitically or macroeconomically. I think we feel confident in our ability to execute, you know, sort of despite the uncertainty. Specifically on your point about Russia, I would just call out, we have very limited revenue, you know, in Russia, you know, for fiscal 2022, it was roughly a low single-digit millions revenue contributor. We're obviously, you know, complying with all of the relevant laws and regulations, you know, as they emerge. Obviously, if there are future things on the horizon that we can't contemplate, we'll certainly update you, but we feel good about the outlook. Super helpful context. Thank you, Michael, and congrats. Thank you. Thank you, Sanjit. The next question comes from Raimo Lenschow with Barclays. Please proceed. Thank you. Dev, could you speak a little bit to the relationship with the big hyperscalers? It looked like the deals influenced by them kind of shot up quite a bit, like, you know, and obviously it's this funny relationship of cooperation. Like, what did you see there in terms of, like, how they are interacting with you and how that relationship is changing over time? Then I had one follow on. Sure. The basis of our relationship with the cloud providers is really first and foremost based on the strong product markets that of MongoDB. MongoDB is incredibly popular and the popularity spans all major cloud providers. I think what we have shown first with Google, as we started working with them very closely, given their ambitions to grow their business quickly, is that we could partner effectively and help them acquire a lot of new customers, a lot of new workloads onto their platform. This did not go unnoticed by some of the other cloud providers, and we started going deeper with AWS. As people may remember, in early 2018, AWS introduced a competitor clone of MongoDB, and there was some worries about how that relationship would evolve. I'm pleased to say that I feel like the relationship has never been stronger. We have deep relationships in the field. We partner more on deals, and AWS has recognized that MongoDB drives a lot of demand to their platform. The relationship there is very healthy and we're also doing a lot of business with Azure. I would say our win rates are still very high against them when we go head-to-head against them. Clearly, they're good partners and we're investing a lot in those relationships. Yeah. Okay. Michael, on the guidance, like it's really impressive to see the margin guidance, if I consider the $45 million-$55 million extra spending that we see this year. Can you just talk a little bit about the other drivers that help you achieve that? The what, sorry, that helped us? It's also just like it does look like the internal efficiencies or the scale of the businesses are allowing you to do that- Yeah. -because the, you know, that looks, you know, despite the spending, the outlook is actually better than what I modeled. Yeah, no. We've been continuing to show, you know, meaningful operating leverage. We feel good about that. We're seeing scaling, you know, throughout the business. That said, we certainly are, you know, investing to pursue the market opportunity. That means both investments in sales and marketing, and in R&D, and obviously sort of everything else to scale the business. No, we've been really pleased, both, you know, at the gross margin line, you know, with the success given where, you know, Atlas is as a percentage of the business and executing against the plan there, as well as, you know, on the bottom line. And I think that, you know, we'll continue to execute on that, but we feel really good about where we are. Perfect. Congrats. Well done. Thank you. Thank you. Thank you, Raimo. The next question comes from Phil Winslow with Credit Suisse. Please proceed. Hey, guys. Thanks for taking my question. If we look at just the analysis of just sales efficiency, it seems that the productivity continues to, you know, to rise, but you also continue to add capacity. What if you have a sense of just what you're seeing from the inside in terms of productivity and how you're thinking about this coming year in terms of just, you know, capacity adds but also productivity? Thanks. Thanks, Phil. We feel really good about the performance and the productivity of the sales organization. The performance was broad-based. You know, one of the traps in software sales is that you can get some big deals can mask weak performance in the rest of the sales cohort. We're not seeing that. We're seeing broad-based performance across our entire sales teams, you know, across all the different theaters. That's giving us a lot of confidence. We're adding a lot of people quickly. MongoDB is viewed as a very attractive place to come to. We believe that we really help people understand and master the art of sales. We put a lot of time and effort into developing our people. Because we're growing so fast, we give people tremendous opportunities for growth. People can really grow their careers here at MongoDB. We push the envelope on innovation. We're doing things that not many other companies are doing. All things put together, we feel really good about the sales organization. As a result, the reason why we're investing aggressively to expand the capacity of that organization. Great. Thanks, guys. Keep up the great work. Thanks, Phil. Thank you, Phil. The next question comes from DJ Hynes with Canaccord. Please proceed. Hey, guys. Nice set of numbers here. Dev, we've seen a bit of an inflection in revenue per customer over the last couple of quarters. I'm wondering if that's more a function of your big customers getting bigger, right? I mean, we saw a record 100k+ adds. Or is it all the smaller starting Atlas customers that you've added over the last couple of years now kind of ramping to more material spend levels? I'm sure it's a bit of both. I'd love to get some qualitative color. Yeah. In general, you know, the expansion rates of the cohorts are very strong, but I think a lot of it is also due to the mix. When we changed the way we want to engage with customers, we saw a big influx of self-serve customers moving to a direct relationship. Obviously, that change in mix affected the revenue per customer number. As things have kind of, you know, as I said, gone to more of a steady state function, you're seeing those numbers stabilize. We feel like we have a really huge embedded growth opportunity in our customer base, and that's where we're spending a lot of time with, as well as acquiring new customers. Yeah. Okay. Michael, my follow-up for you. I mean, obviously the EA strength in the quarter drove the strong cash flow that we saw. As you look out to fiscal 2023, do you think Mongo can be free cash flow profitable? Yeah. Thanks for that, DJ. A couple of things. I would say in general, it's a very strong quarter, Q4 from a cash flow perspective. I would say that's less as a result of the EA sales in Q4 and more a result of the strong Q3, inclusive of some of the pull forwards that we called out previously. Typically, you know, there is a little less intra-quarter collection from when you book business. Obviously, it depends a little bit on the linearity. We haven't given specific, you know, guidance around operating cash flow positive, but I certainly do think it's noteworthy, not just the strong, you know, and significant magnitude, you know, the more than $20 million in Q4, but the fact that we had $7 million in positive operating cash flow for the full year. I do think it is noteworthy. It's not a specific milestone that we've focused on or set out, but I do think it's, you know, a positive reflection on the underlying trends of the business. Yep. Yep. I agree. Okay. Thank you. Thank you, DJ. The next question comes from Karl Keirstead with UBS. Please proceed. Thanks a lot. Maybe two for Mike. Mike, back to the Atlas strong sequential usage growth. I'm sure you're well aware that some of your peers, Snowflake, Confluent, Datadog, that also have AWS-centric usage models, called out a bit of a usage lull or unusual consumption seasonality in December, January. Did you see that? Perhaps it was offset by other drivers, or did you not? If you didn't, what makes your model different from those peers? Thank you. Yeah. Thanks, Karl. No, we saw a very strong behavior in Q4. The cohort expansion was in line with historical trends. Nothing sort of abnormal or atypical there. It was a strong quarter in Q4, as we mentioned, in part because the beginning run rate was higher given the exceptionally high, you know, expansion in Q3. Q4 itself behaved pretty normally. You know, I think it doesn't quite fit the patterns that you're describing. Hard for me to speculate exactly on all the reasons why as it relates to those other businesses, other than the fact that, you know, from the database standpoint, you know, that it sort of has an always-on component to it, for lack of a better phrase, as opposed to something that is a specific- Episodic. Yeah, episodic or, you know, analytics query or batch query-driven basis. Yeah. Okay. That's perfectly clear. Thanks for that, Mike. My follow-up, I just wanna be crystal clear on what you're conveying when you say that you're not assuming a pandemic impact in your fiscal 2023 guidance, Mike. Are you really saying that you're guiding less conservatively going forward and therefore implying that perhaps we should, you know, not be thinking that the beat cadence will maintain at the level you've put up in the last two to three quarters? Yeah. The way I would think about it, Karl, is that our guidance philosophy hasn't changed, but I think our perception of the uncertainty or risk of the environment has changed. Given how well we've operated over the course of the last two years of the pandemic, it would be hard for us. Despite the uncertainty that still exists, I think we just have a lot of confidence that we can execute in that environment, and that hasn't been the case the last two Marches when we've, you know, provided that guidance. I wouldn't describe it as a change in philosophy or a change in conservatism, but I think it's just sort of reacting to the facts as we have them, and less risk and less uncertainty than we've had previously. Got it. Okay. That's very clear. Congrats to the whole team on the great results. Thanks, Karl. Thank you, Karl. The next question comes from Brent Bracelin with Piper Sandler. Please proceed. Thanks for taking the question here, Michael. It certainly is impressive to hear all this talk about positive free cash flow and positive cash from operations. I guess, as you think about the guide for next year, clearly much better than what we had modeled from an operating perspective. Where do you expect to see the most operating efficiencies coming from in the coming year? Then Dev, if you could talk a little bit about Atlas, the usage trends per customer are showing the highest growth rate that we've seen in three years. Just wondering here if that's seasonally strong or do you think this is just tied to a broader adoption, broader number of customers standardizing the platform? Thanks. Yeah. Thanks, Brent. On the first part of the question, I don't think that there's any material skew, you know, sort of one way or other. If you look across the board, I think we'll, you know, continue to show, you know, progress, you know, overall, and that will come from sales and marketing, you know, R&D, and then, you know, overall, you know, the rest of the organization in G&A. We're not intentionally trying to skew that, you know, in any particular way. As Dev mentioned, we feel like we are still quite thin on the footprint coverage, and so we're trying to expand sales and marketing, you know, as rapidly as we responsibly can just to make sure that we're, you know, in as many conversations and customer dialogues as possible. Given the breadth of the product roadmap and the returns that we've been getting on those investments, we think that it's prudent to invest in those as well. There's not one particular lever that we're looking to sort of disproportionately or incrementally scale. You'll see, you know, scaling in aggregate, as you can see in the results and in the guide. Dev, do you wanna cover the Atlas piece? Yeah. Brent, on your question on usage trends, whether it's seasonal or there's some other things going on, I would say it's definitely the latter. We are definitely seeing broader adoption of Atlas by customers. We're definitely adding more customers and more workloads to Atlas. I'd also say the mission criticality of those workloads is increasing from, say, four or five years ago to today, where people are now running, you know, major elements of their infrastructure and major elements of their business on our platform, and these are not applications that you turn off or slow down. I think that's why you're seeing the usage trends as we've observed. Yeah. I would just add, Brent, I'm not exactly sure which math you're doing, but if you're looking at sort of Atlas revenue per average Atlas customer, part of that, to Dev's point, will very specifically come from the fact that we're seeing increased adoption of Atlas among direct sales customers, right? Which will be at a higher spending level than self-serve customers. That's really more of an output rather than an input. Again, we run the business on a channel basis, and that's a little bit of what's happening kinda below the surface of the math that you might be doing. Helpful color. Great to see the momentum. Thanks. Thank you, Brent. The next question comes from Ittai Kidron with Oppenheimer. Please proceed. Thanks. Hey, guys. Great quarter. Dev, I wanna go to the macro environment. I know the events in Russia and Ukraine are not more than two weeks old, but I'm just kinda wondering if your discussions, I'm sure you had a few of them. With customers in Europe, we're just really concerned that the continent will go into recession or several continents will go into recession over there. Is there any change in the tone and the discussion and the investment planning? Are things getting elongated as far as deal closings? Any color that will help us understand what the state of mind is over there right now, of course, outside of Ukraine and Russia. Yeah, outside of Ukraine and Russia, we see no change. We feel really good about Q1 as per the guidance, and we look at this on a daily and weekly basis, and we're seeing no change. Very good. Thanks. Thank you, Ittai. The next question comes from Rishi Jaluria with RBC. Please proceed. Wonderful. Hi. Hey, Dev. Hey, Michael. Thanks so much for taking my question. Just two on my end. First, I wanted to start with the serverless offering, which is in preview mode. Can you talk a little bit about, you know, how customer feedback and early adopter feedback has been? How to think about the long-term impact if this starts to see real adoption, and maybe help us understand, you know, some use cases that you've seen for serverless versus the core Atlas, and then I've got a follow-up. Sure. So, the whole notion of serverless is to essentially abstract away the need to do capacity planning, that people can basically connect to our database, start using it, and not have to worry about it anymore. The database will just scale up and down, based on the needs of the application. The early feedback has been incredibly positive. We're seeing a lot of interest. We have a lot of people using it today. We're getting great customer feedback, and you'll see us continue to invest aggressively on serverless. We obviously will have, you know, our own dedicated offerings as well as serverless, but over time, we think serverless will become, you know, a more meaningful part of the business. We're super excited by the feedback so far. All right, great. I wanted to go into the NRR. You know, showing 120%+ NRR at a billion in ARR is really impressive. Can you talk a little bit about what are kind of some of the drivers of being able to maintain this level of NRR at this scale? You know, is it a function of you know, expanding workloads, new use cases, upmarket momentum, lower churn? Maybe walk us through a few of the drivers for keeping it up and how to think of that metric going forward. Thanks. Yeah. You know, we believe that we have built a very durable business, and a big reason for that is we've really focused on acquiring workloads, acquiring customers, then acquiring workloads in those customer accounts. Unlike other businesses where you can grow very, very quickly because you just basically manage a lot of data, our unit of measure in terms of account penetration is the number of apps or number of workloads. They do take time. No one's gonna move 100 workloads overnight, but you have a great opportunity because we're so fractionally penetrated in even our existing accounts, even though they may be large customers and they're spending a lot of money with us, there's still thousands of apps that we can win, whether they're new apps they're building or existing apps that they want to modernize. We also put a lot of focus on making sure our customers are successful, really ensuring that the customers get value very, very quickly from our platform, which obviously affects retention rates and churn. The degree to which we do that well, that also affects our net expansion rates. I think those two factors, along with adding new customers in general to our platform, really help keep that high net retention rate. All right, great. Thank you. Thank you, Rishi. The next question comes from Tyler Radke with Citi. Please proceed. Hey, thanks for taking the question. Obviously, the Atlas revenue was really impressive this quarter, but I think the Enterprise Advanced revenue really, really stood out to me this quarter. It, you know, grew seven points faster than you saw last quarter where there was kind of a pull-forward dynamic. I was wondering if you could just kinda unpack the drivers of the EA performance this quarter. Was it primarily driven by an uptick in new customers? And given that EA customers tend to be, you know, larger companies, are you seeing any change in terms of, you know, the mix of legacy or, you know, traditional database migrations? Thanks. Sure, yeah. As we mentioned, and as I, you know, commented on in the prepared remarks, it was obviously a very strong Enterprise Advanced quarter. Q4 historically has been the strongest EA renewal base. We clearly demonstrated, you know, and observed very strong demand for more EA workloads. Just if you step back more generically, most sales of EA are to existing EA customers, right, who are expanding incremental workloads. In addition, as we called out these sort of focus accounts that we're putting more resources around, a number of them are primarily EA accounts. We, you know, had a lot of success deepening our penetration with those customers. Given that Q4 is a large renewal base, that's often a good time, you know, when that takes place. Certainly, EA will be volatile quarter- to- quarter, given, you know, 6 0 6, but it continues to be very strong. Again, our goal is really just to give the customers choice and meet them wherever they are in their cloud journey. Great. Maybe a question for Dev. So you've released a lot of kind of interesting new capabilities around support for time series and streaming. I'm just curious how you're seeing kind of the uptick in, you know, operational intelligence or real-time analytics within your customer base, and, you know, how impactful is that gonna be, you know, in terms of growing existing accounts going forward? Thanks. We believe that the trend of applications getting smarter, and they get smarter by embedding more data and more real-time data and more analytics into the application is a trend that's going to increase dramatically, which is why we believe we're well set up to take advantage of that trend. One, by definition, we're an operational data platform, but that's where you get the live data. Two, we have a distributed platform, so you can segregate nodes, one for essentially, you know, writing the transaction and the other nodes for reading data. So this enables you to do that without impacting user performance. Three, we came out with capabilities where if you wanna do a sophisticated query, obviously, operational data is constantly changing. You can take a snapshot of the data at some point in time and run a query and get that result and embed that result back into the application. We're embedding more and more capabilities into our platform to enable developers to build smarter applications. As I mentioned, you know, with the advent of faster networks, faster chips, better algorithms, the sophistication of use cases are only gonna increase, and we feel like we're really well positioned to take advantage of that, and you'll see a lot of our investments go in that direction. Thank you. Thank you, Tyler. The next question comes from Fred Havemeyer with Macquarie. Please proceed. Hey, thank you. You know, in your prepared remarks, Dev, you were mentioning how Getir was scaling from just MongoDB Community Edition onto MongoDB Atlas. It got me thinking, you know, Dev, would either you or Michael be able to provide any context on some of the larger Atlas customers or generally MongoDB customers and, you know, how many of them began as just kind of like Community Edition startups and scaled into some of your larger and more material accounts? Well, in the early days, all of them came from community. What they were attracted by was the notion of really outsourcing all the undifferentiated work of provisioning, configuring, and managing a distributed database, and essentially focusing on, you know, building great apps that, you know, transform their business. What we've done over the last few years is really enabled a free tier of users on Atlas. They essentially can try and test and play with Atlas. Then we get those customers to migrate into our paid offerings, and we're starting to see increased success with that motion, where people start on our free tier because they don't even wanna, you know, they just wanna work on the cloud, and then very quickly they start using their level of usage and interest ends up getting them to a paid offering. That's another trend that we're seeing that's emerged. Obviously it all starts with a product market fit of MongoDB, the document model, the way we just make it so easy to build applications quickly, the way we enable developers to innovate fast. Atlas just allows them to essentially focus on what's important and leave all the plumbing to us. Yeah. I would just add that Atlas self-serve, whether it's free tiered or paid, is sort of the modern, more, you know, contemporary version of downloading community server and managing it yourself. And as we pointed out before, more than 50% of Atlas ARR was self-serve sourced, right? It's just sort of reinforcing that same, you know, motion that Dev is describing. Okay. Thank you for the context there, and I think I'm one of those free tier users. Eventually, I'll scale up. The second question I wanted to ask you, Dev, is- Let us know if you need anything. Oh, thank you. I'll head over to your office and knock on the door and ask for some help, just like back in the old days. I'd also like to ask, you know, about cash in the balance sheet and, you know, with, you know, generating some free cash flow this year, material free cash flow this year. I wanted to ask, you know, how, you know, Michael, are you thinking about cash deployment within MongoDB? Generally, you know, are you thinking about just really how are you thinking about cash in your balance sheet, and how do you characterize MongoDB's M&A appetite, if you have one? Yeah. In general, I would say that we've got an appropriate and very healthy cash balance with, you know, $1.8 billion. It gives us the confidence to think long term. Obviously we're continuing to make operating leverage progress, but as we see, you know, needs or opportunities or, you know, or higher return investments, we're able to make those. I think specifically from an M&A perspective, we'll be opportunistic. We feel like we've got a lot of organic running room to go, but, you know, we'll certainly, you know, be opportunistic as needed. Dev, I don't know if there's anything you want to add to that. Yeah. I would say that we obviously stay very close to the ground in terms of what's happening in the data infrastructure space. There's a lot of activity in the startup ecosystem. But as Michael mentioned, we feel like we have a lot of opportunity with our core offerings. We have done some acquisitions in the past. They tend to be smaller, more surgical acquisitions. If we do end up doing anything, it's probably more in that category than anything meaningful. Thank you for the context, and congratulations on a strong quarter. Thanks, Fred. Thank you, Fred. The next question comes from Steve Koenig with SMBC. Please proceed. Hi, gentlemen. Just one question today from me. You know, last week it was pretty surprising to see from Snowflake how performance improvements in their platform negatively impacted effective pricing and the revenue outlook. I don't think I've ever seen that, you know, either working in or covering database companies. I'm wondering, you know, without commenting on them, like, tell me about maybe your model. Why won't performance improvements negatively impact you guys, and is there, you know, a difference between operational and analytic data stores that's relevant here? Thank you very much. Yes. Thanks, Steve, for your question. I would say the big difference is our unit of work is the application or the workload. I would say other companies' unit of work is the amount of data they have to ingest. I think, when people think about building a new application, there's obviously some sort of business case, essentially some funding to solve some important business problem or seek some new business opportunity. They think about that investment very differently than the amount of data that they're constantly collecting. As you can imagine, it's not surprising to me that some customers, when they see their bills escalate, probably get frustrated at the rate and pace of how their bills are escalating. Whereas as customers are building new applications on our platform, for them, that's a new decision on a new use case, and for them it makes sense to obviously invest the appropriate resources and technologies to deliver on that use case. I think that's the big difference that you're seeing. We have made performance improvements in our platform, but it doesn't show up, you know, in the way I think it does for other companies. I think we feel very, very comfortable about the value proposition that we're offering to our customers. Awesome. Great. Thanks, Dev. Thanks, Steve. Thank you, Steve. The next question comes from Mike Cikos with Needham & Co. Please proceed. Hey, guys. Thanks for getting me on for a couple of questions here. I did just wanna walk through the guidance real quick for Michael. If I'm thinking about that revenue guidance that you guys provided for the full year of fiscal 2023 and parse out Q1, but is that implied deceleration? Should we be thinking about that as just more difficult year-on-year comps? Or are there any other puts or takes to that? The second point, gross margins has really just held up phenomenally given the amount of exposure coming in from Atlas as it becomes a more meaningful driver to total revenue. Should we still expect some gross margin erosion going forward as that Atlas becomes a larger piece because of the associated infrastructure component? Sure. You're thinking about your gross margin. The first question was? Guidance. Oh, guidance. Yes. Yeah. Thank you. No, I think overall on the guide, we feel like it's a very strong, you know, outlook and we're guiding to, you know, significant durable growth at scale. I would say two key factors to point out. One is we continue to expect more Atlas over time, and so less 606 impact of EA. Obviously, over a 12-month period, you know, that all sort of comes out in the wash. But given that upfront term license component piece, as more of the business shifts from EA to Atlas over time, we expect to have less of that. Yes, the second point would be what you called out, which is the strong Atlas performance, particularly in the back half of the year, sets up, you know, a very significant compare. On the gross margins, yes, we've been super pleased with how we've done on our gross margin game plan. We've executed, you know, better than we had thought we could. If we'd, you know, thought that Atlas was gonna be this size and scale and at 58% of revenue, and you'd say we'd have 74% non-GAAP gross margins or 77% non-GAAP subscription margins, I would have doubted that we'd be able to execute that. I don't think we're prepared to call a bottom, but I do think that we are closing in on one, given the strong performance of our, you know, optimization program. Thank you very much for that. I hope I didn't mean that to sound like the revenue guide is not strong here. I just wanted to make sure I understood the puts and takes to the full year. Just one more- Totally understand. One more if I could. I think the last time we received an update as far as incremental OpEx, and I'm thinking about that $45 million-$55 million that we're talking to as commercial activity normalizes, right? I guess backward looking here, but for fiscal 2022, I think we might have been expecting, call it $9 million-$12 million based on the most recent data point we had, and just wanted to see how the year ended up finishing up versus that $9 million-$12 million, I guess guideposts that we had previously had when thinking through the Q4 upside. Yeah. I think when we've talked about it, we said in the end, fiscal 2022 came out broadly in line with our fiscal 2021 spending, and we had expected to spend much more in fiscal 2022, on the sort of, you know, I'll call them COVID-related expenses for lack of a better phrase. Just given the, you know, environment and backdrop, we did not see as much activity there. Makes a ton of sense. Thank you very much for getting me on, guys. I really do appreciate it. Thanks, Mike. No problem. Thank you, Mike. That concludes the Q&A session. I'll pass the conference back to MongoDB CEO, Dev Ittycheria, for additional remarks. Thanks, Selena. I think it's fair to say that we had an excellent quarter. We're continuing to see strong momentum. We believe that we're solving and addressing fundamental problems that developers have, and the value of our platform offering one unified and integrated way to solve and address many use cases is really resonating in the marketplace. That's evident in our continued strong customer growth. With that, I wanna thank everyone for joining us today, and we'll talk to you soon. Take care. Bye-bye. That concludes the MongoDB fourth quarter FY 2022 earnings call. Thank you for your participation. You may now disconnect your line.