MongoDB, Inc. (MDB) Q2 2022 Earnings Report, Transcript and Summary

Good day, and welcome to the MongoDB Second Quarter Fiscal Year 2022 Earnings Conference Call. All participants will be in a listen-only mode. [Operator Instructions] After today’s presentation, there will be an opportunity to ask questions. [Operator Instructions] Please note this event is being recorded. I would now like to turn the conference over to Brian Denyeau from ICR. Please go ahead, sir.

Great. Thank you, Chuck. Good afternoon, and thank you for joining us today to review MongoDB’s second quarter fiscal 2022 financial results, which we announced in our press release issued after the close of the market today. Joining me on the call today are Dev Ittycheria, President and CEO of MongoDB; and Michael Gordon, MongoDB’s COO and CFO. During this call, we will make forward-looking statements including statements related to our market and future growth opportunities, 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 COIVD-19 pandemic and its impact on our business, results of operations, clients and the macroeconomic environment, could cause actual results to differ materially from our expectations. For discussion of 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 on this call reflect our views only as of today and we undertake no obligation 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 our -- 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, and thank you to everyone for joining us today. I will start by reviewing our second quarter results before giving you a company update. Before diving in, I want to share that today marks my seventh anniversary at MongoDB. I’m incredibly proud of how much progress we’ve made over the past seven years. We went from being a small private company with an interesting technology to disrupting one of the largest markets in all of software. Along the way, we changed how open source software is licensed, we introduced a new cloud service that required us to both partner and compete with the largest cloud providers, and we grew revenues 20-fold with a compound annual growth rate of over 50%. I’m incredibly grateful to all the amazing people in MongoDB and to our customers and partners around the world who made this happen. As proud as I am of the amazing journey we’ve had, I’m even more optimistic today about our opportunities ahead. Looking quickly at our second quarter financial results, we generated revenue of $199 million, a 44% year-over-year increase and above the high end of our guidance. We grew subscription revenue 44% year-over-year. Atlas revenue grew 83% year-over-year and now represents 56% of our revenue. And we had another strong quarter of customer growth ending the quarter with over 29,000 customers. Businesses across nearly every industry have realized that in today’s highly dynamic global markets, speed of development is a meaningful competitive advantage. Businesses that can develop software faster are able to improve their products faster, and ultimately, grow more quickly than their competition. We believe our strong second quarter results are a clear indication that customers view MongoDB as a critical platform to accelerate their digital innovation agenda. Customers of all types are using MongoDB because they can develop so much faster using our platform to build new applications and re-platform legacy applications across a broad range of use cases to drive their business forward. Fundamentally MongoDB’s application data platform offers three intrinsic advantages. First, MongoDB’s document model is designed around how developers think and code, unlike legacy data technologies. This enables developers to be far more productive and build applications faster, as compared to any other technology. Second, MongoDB’s document model is a superset of other data models, tabular, key value, time series, graph and other kinds of data relationships can be easily created using documents. The document model enables MongoDB to address a wide range of use cases and reduces the need for customers to use niche technologies that only serve a single purpose. Third, MongoDB is designed for performance and scale. With MongoDB sophisticated capabilities to replicate, manage and distribute data at massive scale, organizations increasingly choose MongoDB to address the most demanding requirements. Legacy technologies are fundamentally not designed for today’s scale and performance expectations, requiring developers to spend an enormous amount of time working around their architectural limitations. The continued success of Atlas shows that speed is of paramount importance to our customers. Atlas is the best way for customers to enjoy the benefits of our platform, as the time to value can literally be only a matter of minutes. Atlas had another excellent quarter, accelerating to 83% year-over-year growth, while approaching a $0.5 billion run rate. We also had another strong quarter of Atlas customer additions from self-serve to enterprise customers. Our second quarter results give us even more conviction to continue investing in both our product portfolio and our go-to-market initiatives. Starting with go-to-market, our field sales team is increasingly being pulled into higher level strategic conversations at the C-suite of the largest companies in the world and we are adjusting our approach to more effectively serve that audience. Last year we expanded with increasing our focus on our most promising customers. Our hypothesis was that by going deep into an account with more resources, it will position us more strategically and allow us to penetrate the account more quickly. Those investments produce excellent returns and most accounts that ran this experiment grew faster than we expected. This is giving us confidence to expand this deeper coverage model to more accounts this year, while also focusing on expanding our field sales capacity in all regions. Our inside sales team is firing on all cylinders and had another great quarter. The strong product market fit of Atlas for this channel, along with the changes we introduced last year to make it easier for customers to start using Atlas, have had a positive impact. Given the results, we are focused on expanding our inside sales capacity in our regional hubs around the world to capture more of the large opportunity we see in this channel. Finally, turning to self-serve, this channel is a cost effective way to acquire large numbers of customers and is a critical lead generation vehicle for our sales organization. We are focused on increasing our sophistication on digital acquisition and product-led growth techniques to increase the top of funnel and optimize mid-funnel conversion rates. This is an iterative process with a lot of experimentation that is yielding promising results. Turning to our product roadmap, we continue to invest both to extend our lead and the core database space, as well as to mature and grow our merchant products. At MongoDB.live, our User Conference held in July, we made significant -- several significant product announcements that further advance our vision. We focused on two themes ease-of-use and expanding the capabilities of our platform to make it more compelling for customers to standardize on MongoDB. First, on ease-of-use, making it easy for developers to use and get value out of MongoDB has been the core of our DNA since the founding of the company. Our announcement of Atlas Serverless takes ease-of-use and developer productivity to the next level. With Serverless, customers can get started with MongoDB without having to pick a specific machine type or size. The application connects to Atlas and we handle the elastic scaling of compute and storage seamlessly, whether an application scales quickly or as spiky traffic patterns. This dramatically simplifies life for our customers, because they no longer have to do capacity planning or manually intervene to adjust the size of the deployment. We expect Serverless to drive more customer demand, because getting started on and using Atlas just became even easier. Next, for customers who want to benefit from our sharding features to manage a massive amount of data, we introduced Live Resharding. As a reminder, sharding is a method for horizontally distributing data across multiple machines. MongoDB uses sharding to support deployments with very large amounts of data and high throughput operations to prevent any single machine from becoming a bottleneck. Previously, when a customer wanted to shard data, the customer had to pick a shard key, essentially the parameter that would be used to partition the data. However, we know an application’s requirements can change quickly, make it more beneficial to partition data using a different shard key. Live Resharding allows users to easily change the shard key when this happens. This feature, which is not available in any other platform, will make it far easier for customers to start using our sharding capabilities and seamlessly redistribute data when the requirements of their application or their business change. Finally, our announcement in Versioned API addresses a structural issue with all databases. Historically, when a new database version is introduced, there are feature changes that can break existing application functionality and create significant rework for development teams. Invariably, some organizations prefer to stay on an older version of a database to avoid this risk. But the downside is that they then cannot take advantage of new features available in the latest version. Our introduction of Versioned API solves this problem. The Versioned API feature lets you upgrade your MongoDB server at will. This groundbreaking capability allows customers to decouple the application development lifecycle from the database lifecycle, so they only need to update their application when they want to introduce new functionality, not when they upgrade the database. Of all the features we announced in MongoDB.Live, Versioned API got perhaps the most enthusiastic customer reception. Regarding the second theme, we remain focused on expanding the capabilities of our platform. Because customers consistently tell us that they want a modern general purpose platform that precludes the need for single purpose technologies in order to reduce back end infrastructure complexity and increase the speed of innovation. We introduce native time series support across our entire platform. Time series collections, clustered indexing and windows functions make it easier, faster and lower cost to build and run application like IoT. While we were able to address this fast growing use case in the past, with these new features, we can compete for even the most demanding time series workloads. We also add a depth of functionality across our merchant products, perhaps most notably an Atlas Search. We’re enhancing search with custom synonyms and function scoring, which allow e-commerce customers to provide more relevant and geographically targeted results. We believe these features will make Atlas Search an excellent solution for even more use cases. Finally, we also recently announced that we achieve FedRAMP Ready status. This designation allows to capture the substantial demand for MongoDB Atlas across federal and state government agencies and ISVs that serve that market. Our recently announced product enhancements enable customers to use MongoDB for an even broader set of use cases and represent a meaningful step forward on our journey to deliver the preeminent modern application data platform. Now I’d like to spend a few minutes reviewing some customer wins and interesting use cases from the second quarter. JetBlue is New York’s hometown airline with 1 -- with over 100 destinations across the U.S., Caribbean, Latin America and between New York and London. To overhaul their core e-commerce app, JetBlue chose the MongoDB application data platform. MongoDB flexible data model allows JetBlue to build dynamic customer experiences when their ticketing application, as well as predictive analytics in real time. DataRobot is a leader in augmented intelligence, delivering a trusted AI platform that empowers organizations to make better data driven business decisions faster and at scale. MongoDB has powered the company’s SaaS platform from its inception and this quarter DataRobot migrate from MongoDB Community Edition to Enterprise Advanced for compliance encryption features and support. Our enhanced relationship will help DataRobot continue to innovate and support its global customer base, as users who are using AI to transform their businesses. Roma Capitale is the governing body for the City of Rome and manages services across transport, welfare and education for over 4 million citizens. In a bid to drive a new smart city approach, Roma chose MongoDB as part of the underlying data platform to modernize its entire content management system and drive a new comprehensive single-view environment for development. As a result, Roma jumped from 15th place to fourth in the latest Italian Smart City ranking and was able to bring new online digital opportunities to its citizens. PT Visionet Internasional or OVO, a leading Indonesian payments, rewards and financial services platform relies on MongoDB to power its core digital payments platform that serves over 115 million devices. As part of a strategic initiative to market all of its database workloads spread across multiple databases and hosting platforms, OVO chose MongoDB Atlas enterprise to consolidate its tech stack and move to Google Cloud. OVO expect the modernization will increase developer productivity, accelerate new feature release cycles and consolidate workloads making the over infrastructure feature ready. In summary, we had another excellent quarter. Our customers want to innovate faster and are looking for a scalable general purpose application data platform that will give their developers the freedom to move quickly. MongoDB is increasingly seen as uniquely positioned to fulfill this need. With that, I’ll now turn it over to Michael.

Thanks, Dev. As mentioned, we delivered another strong performance in the second quarter, both financially and operationally. I’ll begin with a detailed review of our second quarter results and then finish with our outlook for the third quarter and full fiscal year 2022. First, I’ll start with our second quarter results. Total revenue in the quarter was $198.7 million, up 44% year-over-year, subscription revenue was $191.4 million, up 44% year-over-year, and professional services revenue was $7.4 million, up 27% year-over-year. We exceeded our expectations in both Atlas and Enterprise Advanced but our outperformance was particularly notable in Enterprise Advanced. As you know, EA has a more immediate impact on revenue due to the fact that under ASC 606 we’re required to recognize the term license component of revenue upfront. Overall, Atlas’ strong performance continues to be the largest contributor to our growth. Atlas grew 83% in the quarter compared to the previous year and now represents 56% of total revenue, compared to 44% in the second quarter of fiscal year 2021 and 51% last quarter. During the second quarter, we grew our customer base by over 2,200 customers sequentially, bringing our total customer count to over 29,000, which is up from over 20,200 in the year ago period. Of our total customer count over 3,600 are direct sales customers, which compares to over 2,500 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-service customers with whom we now have a direct sales relationship The growth in our total customer count is being driven in large part by Atlas, which had over 27,500 customers at the end of the quarter, compared to over 18,800 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. We had another quarter with our net ARR expansion rate above 120%. We ended the quarter with 1,126 customers with at least $100,000 in ARR and annualized MRR, which is up from 819 in the year ago period. The continued strong growth in customers, with $100,000 or more in ARR is an indication of the success of our land and expand go-to-market strategy and the fact that we’re increasingly becoming a strategic partner and a database standard 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 second quarter was $142.9 million, representing a gross margin of 72%, which is consistent with last quarter and consistent with 72% in the year ago period. Overall, we are pleased with our gross margin performance, which is only seeing a modest impact from Atlas as it becomes a bigger portion of our revenue despite its infrastructure component. We continue to expect that we’ll see a modest reduction in overall company gross margin as Atlas continues to grow as a percentage of our revenues. Our operating loss was $11.5 million or a negative 6% operating margin for the second quarter compared to a negative 7% margin in a year ago period. Our outperformance versus our operating loss guidance was driven primarily by revenue outperformance. Net loss in the second quarter was $15.2 million or $0.24 per share based on 63.4 million weighted average shares outstanding. This compares to a loss of $12.7 million or $0.22 per share on 58.4 million weighted average shares outstanding in the year ago period. Turning to the balance sheet and cash flow, after raising almost $900 million and a follow on equity offerings during the quarter, we ended the quarter with $1.8 billion in cash, cash equivalents, short-term investments and restricted cash. Operating cash flow in the second quarter was negative $19.8 million. After taking into consideration approximately $2.9 million in capital expenditures and principal repayments of finance lease liabilities, free cash flow was negative $22.7 million in the quarter. This comparison negative free cash flow $15 million in the second quarter of fiscal 2021. I’d now like to turn to our outlook for the third quarter and full fiscal year 2022. For the third quarter, we expect revenue to be in the range of $202 million to $204 million. We expect non-GAAP loss from operations to be $25 million to $23 million and non-GAAP net loss per share to be in the range of $0.42 cents to $0.39 based on 66.4 million weighted average shares outstanding. For the full fiscal year 2022, we now expect revenue to be in the range of $805 million to $811 million. For the full fiscal year 2022, we now expect non-GAAP loss from operations to be $67 million to $62 million and non-gap net loss per share to be in the range of $1.20 to $1.13 based on 64.6 million weighted average shares outstanding. To summarize, MongoDB delivered excellent second quarter results. We’re driving high levels of growth at scale, driven by our large market opportunity and strong execution. We continue investing to capture the large opportunity ahead of us. We’re seeing attractive returns on those investments and we’re excited about our positioning for the future. With that, we’d like to open up to questions. Operator?

Thank you. We will now begin the question-and-answer session. [Operator Instructions] And the first question will come from Sanjit Singh with Morgan Stanley. Please go ahead.

Thank you for taking the question and congrats on another really impressive quarter. Dev, maybe I wanted to understand the Atlas growth, I think on a sequential dollar basis, you almost doubled the amount of revenue that you added in Q1. If we could sort of unpack that along with a couple of different buckets, sort of existing customers, sort of expanding with Atlas versus migrating either Enterprise Advanced or another database versus contribution from net new, particularly, customers, you may have thought of the quarter, but also maybe the customers that you have added last year, was that you saw a big uptick, we could sort of unpack the sources of growth of that was and that would be helpful?

Sure. So, first of all, what I’d say is that, customer additions remain robust across all three channels. So we’re seeing strengthen in all geographies, including places like India and Latin America. And we frankly also see strong Enterprise adoption of Atlas. Atlas is increasingly seen as a destination for mission-critical applications. And as we said last quarter, over 600 customers spend north of $100,000 on Atlas alone. And self-serve remains a critical channel and a customer acquisition vehicle. So, over 50% of our Atlas ARR was from customers originally sourced in the self-serve channel. I’d also say that multi-cloud is a huge selling point for Atlas, multi-cloud improves resilience. And as you know, cloud providers do have outages and they can leverage the best features of each cloud provider and avoid lock-in. In terms of like breakdown of where these customers are coming from, I think, I would just say, we’re seeing healthy growth of both new customers, as well as expansion of existing customers. And yes, the customers we’ve acquired over the last few quarters are growing, expansion rates for Atlas are very strong and so all of them are essentially contributing to the growth of Atlas.

I would just add maybe, Sanjit, from perspective, the two thoughts. One, on the year-over-year piece, obviously, Q2 was an easier Atlas compare, given the COVID impact that we experienced last year that was that sort of broad based, but modest impact that we saw, resulting in slower expansion from accounts. And then sequentially to your point, there is some seasonality and Q2 tends to be meaningfully stronger than Q1 and so you sort of -- you see that showing up in the numbers as well.

That’s good context, Michael. And then as my follow-up, Dev, MongoDB 5.0 versus 4.0. Anyway sort of you could sort of frame out how significant this release? I mean, 4.0 was a major release, right? There was a lot of key enterprise features, multi-document ACID support, sort of a game-changing at least in my view. How should we think about 5.0 versus the 4.0 cycle?

Well, it’s a question I actually haven’t thought of. But as you said, 4.0 was assembled at least for us because it’s introduced a big feature with multi-document ACID transactions, which at the time was the biggest objection for enterprises or anyone using, wanting to use MongoDB for mission-critical use case. That objection was obviously taken off the table. What I would say with 5.0 is we’re just continue to double down on it, one, expanding our platform, obviously, with all the additions that we’re making, especially with native time series support and we’re also making it far easier for customers to use MongoDB. As you can imagine, with over 29,000 customers, we have customers of all shapes and sizes, of all levels of sophistication. And we really want, frankly, and that -- this is in our DNA, we really want the database to get other way of people getting their work done. And so we just want to make it really easy for people to use MongoDB and obviously Atlas is the best way to expose a lot of the features. And so I would just contrast, I would say, 4.0 is all about convincing people that we truly could be a general purpose, mission-critical platform. And 5.0 is all about expanding our platform and making MongoDB even more easy to use, so that people can get started on MongoDB more quickly.

Makes total sense, Dev. Congrats on the stellar results. Thank you.

Thanks, Sanjit.

The next question will come from Raimo Lenschow with Barclays. Please go ahead.

Hey, thanks and congrats from me as well. Can you talk a little bit about, Dev, what you see out in the field in terms of customer interest to do more stuff again. So I’m looking at your self-service Atlas started to kind of reaccelerate on growth. But we’re coming also out of the pandemic. What do you see in terms of pipeline build and appetite for bigger projects coming through again? And I had one follow up for Mike.

We’re clearly seeing more and more demand. So one of the things that we talked about in the prepared remarks is that, we had identified a set of promising accounts and said, what can we do to grow these accounts even more quickly, because we knew that they like MongoDB, but our percent of the total database spend was still quite small. And so when we deployed more resources and really had one rep focus on that account only, we suddenly saw the level of focus and the incremental resources really drive great results. We started -- those accounts started growing more quickly and so we’re starting to do that even more with some of our other more promising counts again. It’s a small percentage of a total customer base. But these are probably some of the most sophisticated and demanding customers and we are obviously careful about who we choose. We -- these people are predisposed to use Atlas. So we kind of negotiated some sort of agreement with them to use our cloud services, they already have some existing Atlas spend. So we know we have a - some strong champions in account. But we also know that there’s a massive upside in that account. So for the most demanding customers, we’re seeing really, really strong signals and this is giving us confidence to expand this program even further this year, as well as into next year. So that’s kind of the top of the food chain. And I would say that, we’re even seeing digital-native companies, ISVs, who have very, very demanding requirements that can continue to use -- either choose MongoDB or double down on MongoDB for their platforms and we’re really excited about what that means for us long-term.

Okay. Perfect. And then the follow-up for Michael, just, if I look at your cash position now, it’s obviously kind of after the action last quarter kind of a bit bigger. Can you just talk a little bit about your philosophy around cash, how much you want to carry to run the company, et cetera? Thank you.

Sure. Yeah. Thanks. Obviously, the cash was bolstered in part by the equity offering we did during the quarter. We talked about that as an opportunistic financing. I think we just want to make sure that we have the full degrees of freedom that we think makes sense in terms of maximizing the long-term opportunity and to sort of invest in a business as long as we continue to see good returns from that. So I think that’s probably the key points there.

Okay. Perfect. Thank you. Congrats.

The next question will come from Kash Rangan with Goldman Sachs. Please go ahead.

I’m sure you will get very good returns on cash. Thank you so much, Raimo. My question was on Atlas. It looks like the adoption curve for Atlas is turning out to be even more aggressively positive than one would have expected given that its cloud deployment? If you can just compare and contrast the kind of workloads that Atlas is able to take on relative to its life history versus the core MongoDB platform and what are things that have surprised you with the adoption curve? And what does this mean for where this business could look like in the next three years to four years in terms of the scale and scope of customers you could take on, had versus the standalone MongoDB on-prem database server? Thank you so much.

Yeah. So one of the key differences with Atlas and say deploying on-prem is that developers can move very, very quickly, without needing their operations team to set up the infra -- underlying compute and storage infrastructure to get going. So, and by definition, the cloud has elastic scalability and so people can increase their instance sizes or their capacity very, very quickly, without having to go back and ask the ops teams to build out more infrastructure. So the ability for development teams to move very, very fast is even more pronounced on a cloud service like Atlas than it is on prem. The second thing I would say is that, Atlas has clearly become a mission critical platform. In the early days, there were probably people were, obviously, being a new service and people didn’t know what to expect. You saw more dev and test workloads, perhaps, peripheral or Tier 3 workloads moving on to Atlas. But as people got more and more experience with Atlas, as we added more enterprise features to Atlas, people became increasingly more comfortable and now we’re seeing, very, very large and demanding applications move to Atlas, even from some of the more conservative mainstream organizations out there. So what we’re really seeing now is enterprise adoption of Atlas at scale.

Got it. So it’s not a limiting factor itself as it relates to Atlas as a platform, right? We have everything that you get with MongoDB plus more the deployment flexibility, the ability to scale, so on. Is there a point where Atlas becomes even more scalable, even more functionally complete than the core MongoDB platform.

Well, I think, we said this and this happened a couple years back. I mean, we got to feature parity on Atlas far faster than we expected and now we actually release new feature development Atlas First and then we catch up on Enterprise Advanced. And so I would say that, in terms of feature completeness and scalability, Atlas is the best solution in the marketplace today. And I think you’ll see us continue to invest aggressively in Atlas, because every customer that we know, even the customers who are predominantly on-premise, they know that the benefit of using MongoDB is that they can start on-prem, but they have a very seamless path to the cloud. There’s no forklift upgrade. There’s no rewrite of the application code. It’s just a very seamless migration path. And so there’s different customers based on the regulatory environment they’re in, compliance reasons, sometimes even cultural reasons. They may be moving more slowly. But every customer has a very clear migration path to the cloud and we believe the ultimate destination will be Atlas.

Congrats, Dev. Thank you so much.

Thanks, Kash.

The next question will come from Brad Reback with Stifel. Please go ahead.

Great. Thanks very much. Gentlemen, as you think about the last couple of years, you’ve obviously introduced a bunch of new products. So, as we think of where we are today, are those products a meaningful amount or a meaningful contributor to new consumption that we’ve seen quarter-over-quarter, year-over-year or is that really yet to come?

Yeah. So, Brad, I think, that’s good question. Again, I just want to remind you and everyone else that, the new product usage, the revenue shows up as Atlas revenue. But let me just give you a little bit of color on each of the products and what we’re seeing. On Search, what’s becoming very, very clear, is that customers are really, really attracted to being able to combine a database with a Search engine as one endpoint and as a managed service that becomes very, very attractive. They don’t want a disparate MongoDB deployment and then some sort of elastic or solar deployment. To do that on one platform becomes really attractive and we’re seeing really interesting uptick there. On Realm Sync, which, by the way, Sync was just G8 in February. We’re seeing some really interesting customer use cases in particular in retail and logistics, where people want to do inventory management and logistics and we’re seeing some really interesting customer traction there. On the Data Lake product, we’re seeing a lot of interest, especially from some of our larger customers to basically improve the economics of keeping large volumes of data accessible. There’s a challenge of that either they have to migrate the data completely, but then you can’t really access it or you have to delete the data. And with online archive, you can actually get the benefits of having all the data but in a very cost effective way. We also see that people are building more and more interesting smarter applications, where they’re leveraging analytics to build better customer experiences. And so as that becomes more pervasive, you’ll see use cases like real-time analytics and so on, so forth, becoming more and more prevalent. And then, what I would say is that, even though time series is new, we’ve had some interesting traction on time series. Again, customers attracted to rather than buying some sort of bespoke solution, being a part of a single platform and we can leverage the existing MongoDB installed base to go after more business. And so, I would say, that’s the color I provide in terms of new customer traction and we’re quite pleased with how things are progressing.

That’s great. Thanks very much.

The next question will come from Brent Bracelin with Piper Sandler. Please go ahead.

Thank you. Good afternoon. Sticking with Atlas thread here, obviously, third quarter of accelerating growth, if I look at kind of customer add metrics versus usage metrics, this quarter it looks like a more material uptick in usage. So I guess first question, what drove the step up in Atlas usage this quarter? I think you talked about 600 -- 100,000 plus kind of enterprise type customers spending on the platform. Is it mostly enterprise? Are there other factors here at play? And then one quick follow up?

Yeah. What I would say is that, the performance of Atlas is strong across all the three channels. But I think, I would add that, the enterprise adoption of Atlas is really, in particular, something that should be called out. Because we’re seeing customers now becoming very comfortable in deploying mission critical applications on Atlas with very demanding requirements and I think that’s a big part of what’s driving our growth. And I would also say that, multi-cloud is becoming increasingly important. Customers really like the fact that they can protect and preserve their investments in the application, even though they may end up moving cloud providers or may be running an app across different cloud providers. And I would say that, we’re seeing some really interesting demand and some regions like India and Latin America, especially in a mid-market channel. So that gives us -- just gives us more conviction about how big an opportunity we’re going after.

Great. And then Michael for you…

Yeah. Brent, just…

I know…

Okay.

Yeah.

Okay. Let me just add on one thing and then happy to cover your question. I just -- I think people get the year-over-year piece given the easier compare, but I think, I just want to underscore the sort of sequential piece, which I think is really important in the seasonality of Q2 being stronger than Q2 -- than Q1. And when we look out to the second half of the year, we see a tougher compare for Atlas in the second half. Sorry, go ahead.

Got it. So seasonal factor help there. Now my question is still on Atlas. It’s just on the gross margin side. I know overall gross margins downtick slightly. But if I look at kind of gross versus subscription gross margins, you’re well north of 75% for the last three quarters, even with a pretty material mix shift to Atlas. So do you think that with Atlas over half of the revenue mix that sits 75% subscription gross margin is sustainable?

Yeah. So I don’t think we’re prepared to call the bottom yet, but we’ve been exceptionally pleased with how we’ve executed against the strategy. They’re still sort of additional opportunities and while we’re very pleased that Atlas has 56% of revenue, there’s still a lot -- there still is a margin delta between the two and a healthy chunk of the revenue. And so we’ve got more that we need to do and want to do on Atlas gross margin, but we’ve -- so we’re certainly not at the bottom, but we’ve been really pleased with the progress to-date.

Sounds good. Thank you.

The next question will come from Jason Adder with William Blair. Please go ahead.

Yeah. Thank you. Dev, do you have a sense of how you’re doing versus the cloud players? I mean, obviously, your results speak for themselves. But do you track win rates there and any just color or commentary on your competitive position versus some of the house databases from the cloud providers?

Well, if you know anything about the MongoDB culture, we’re very focused on serving our customers, but also being quite aware of what a competition is doing and I’m pleased to report that our win rates against the competition are very, very high, against both the standalone companies, as well as the clones being offered by the cloud providers, our win rates are really, really high. As I’ve said in the past, our biggest issue is deals that are going down that we’re just not aware of and that’s -- those are deals that keep us up at night, because when you go head-to-head, our win rates are extremely high.

All right. And then just a quick follow up on the multi-model capabilities of the platform. I know you have native time series now. I know you have graph and some other data models. Do you have a sense of how much of your customer base actually uses some of those capabilities? Can you track that?

In general, we can, and obviously, with these new capabilities, we can track usage. One of the benefits of a cloud service is you get much better fidelity in terms of what customers are doing on your platform. Yeah, and to underscore, the point you just made is that, the point that we make to our customers is that, rather than having a bunch of bespoke solutions and some of our competition has like 13 or 15 different database options. What people realize after the fact is that the challenge of managing, learning, managing supporting all the different technologies, let alone dealing with how to query all that data, synthesize all that data, backup all that data, becomes onerous management task. And so being able to consolidate it on a single platform becomes very, very attractive, which is why we’re seeing so much interest in Search, which is why we’re seeing so much interest in time series, even though it’s very early and why we think that our platform strategy is really working.

Thanks. Good luck.

Thank you.

The next question will come from Tyler Radke with Citi. Please go ahead.

Thank you. Good evening. I wanted to start, Dev, you made an interesting comment in your prepared remarks, just around higher C level engagement and I guess a couple questions there. What specifically are you doing to support that? Is it hiring more experienced traditional enterprise sellers? And then, secondly, like, what do you think is driving that? Is it Atlas? Is it just overall standardization as they look at legacy migrations? Just to expand on that that comment would be helpful? Thank you.

Yeah. Sure. So, one of the things that we learned about the buying behavior in the space is that people make decisions workload-by workload. So every time you build an application, every time you want to re-platform application, you have to make a decision about what database you want to use. So it tends to be, when you’re in an account, you tend to have a bunch of micro decisions about all these workloads and you have to almost win them workload-by-workload. The benefit of going high is that, ultimately, your goal is to become declarative standard, where people don’t need permission to use MongoDB to build an app. They can pretty much choose MongoDB, quote-unquote, that’s a product off the shelf that is choose and it’s part of the standard architecture that’s been blessed and approved by that organization. So part of the value is going high, is accelerating the path being declared standard and going high also allows you to be positioned very differently than just being yet another database that a company uses. So understanding, helping them understand how we can really help them accelerate the business, how we can help them seize new opportunities, respond to new threats and that -- it’s a real competitive advantage to build applications MongoDB versus any other alternative. So in terms of the people we have, we have -- we hired some outstanding salespeople and sales leaders. And so, obviously, we leverage the whole organization up into including the C level executives. For example, Sahir Azam, our Chief Product officer; Mike -- Mark Porter, our Chief Technology Officer; and myself and others get involved in strategic conversations. Cedric Pech our CRO is outstanding at knowing how to kind of build and scale these types of organizations. And we have very strong leaders in different theaters of the world who know how to do this really, really well. And I would say, in terms of why are we being invited to these conversations. One, I would say, people are starting to get more and more familiar with MongoDB. There’s more and more evidence of the value we can provide. So one is time, they get more experience in MongoDB and they get more confident. Second, I would say, our feature -- our product portfolio is expanded quite significantly, so that we can address more and more use cases. And third, obviously, Atlas has really changed the game where people can just deploy MongoDB far more quickly than doing it’s really on-premise. And so all those things have kind of been accomplished events for us to see the acceleration in these accounts.

Thanks. And Michael, I had follow up for you, I think, in an earlier question, you reference some more challenging comparison in the second half on a sequential basis on Atlas. I’m just curious if you could expand on that. I think if we look back at least on a $1 basis added. The last few years, you’ve seen similar, if not even a little bit more kind of net new Atlas revenue added in Q3 than Q2. So just curious if you could expand on that and how we should kind of think about the shape of the Atlas trajectory for this year?

Yeah. So it’s less about sequential and it’s more commenting that the first half of the year in the base period of the compare was an easier compare given the COVID impacts that we saw at the end of Q1 and then in Q2. So it’s really more of a year-over-year compare question than a sequential comment.

The next question will come from Karl Keirstead with UBS. Please go ahead.

Thank you. I’ve got to two Atlas related questions. Dev, a lot of developers are building apps for Azure and GCP. I think we all understand that the vast majority of Atlas revenues are on AWS. Could you give us a bit of a progress report maybe on the mix from Atlas on GCP and Atlas on Azure? Thank you.

Yeah. I don’t believe we break out the exact detail. But our business tends to mirror the market share of all three cloud providers. I would say, GCP probably is further ahead in terms of our list -- we’re further ahead with GCP relative to their market share. But in general, our business tracks on the market share the cloud providers. I would say GCP -- and I think what really differentiates one cloud provider versus another is that people are recognizing that moving an Atlas workload to their cloud actually has ancillary benefits for that cloud provider, that customer ends up consuming other services and the dollars that they spend with us, they spend multiples of that with the end cloud provider. So in particular, Amazon and Google have been more aggressive in partnering the field at the sales level, there’s more partnering going on and I think that’s yielding more deals. And I think Microsoft is starting to see the -- potentially the benefits of doing that as well, but they are little bit further behind.

Got it. That’s helpful. And then maybe a second Atlas question, the Azure Cosmos DB vulnerability got a decent amount of attention over the last couple of weeks? I’m just curious whether you sense any change and focus on cloud database security exposures? And how and if that’s a differentiator for Atlas?

Yeah. So that’s a good question. Obviously, that news was quite recent in terms of what happened with the Cosmos breach and just a level set, a security company discovered that was possible to gain completely -- a complete unrestricted access to accounts and databases of all the Azure customers, including their flagship product, Cosmos DB and this vulnerability was introduced through -- integration through its Jupyter Notebook service. I would say that, we have a very robust focus on security. Our products are - have a bunch of security certifications, including SOC 2, ISO 27001, HIPAA, PSI, et cetera, and we have layers of defensive controls and triggers alarms in the event of suspicious activity. We spend a lot of time on product innovation and the other security including using features like client side field level encryption, which allows customers to store data in Atlas without there being anyone outside of their organization can even see the data. We utilize external security firms to perform regular penetration tests, same way an attacker would. And we have had a coordinated disclosure program where we encourage independent security researchers to contact us if they find a security issue in our products and we reward them accordingly. So we found tremendous value and output from our engagement with the external security consultants researchers, as well as our internal team and controls around vulnerability and discovery management. And thankfully, we’ve not had a breach of MongoDB Atlas. But we’re very, very focused on security. So it’s a core tenant of our offering.

Okay. Dev, thank you for that.

The next question will come from Pat Walravens with JMP Securities. Please go ahead.

Oh! Great. Thank you and congratulations on the quarter. Hey, Dev, if you look at like the five major use cases for databases, transaction processing, data warehousing, data science, stream processing, operational intelligence, where do you see the most opportunity for MongoDB?

Well, clearly, our roots start off in transaction processing. But we definitely, we definitely see a lot of opportunity in, what you call operational intelligence or what we say is analytics -- real time analytics for the application, we’re not trying to be a data warehouse and you’ll see us continue to invest more in that area. And what we see is that, it’s a massive market and we’re well positioned and as you can do to expand our platform, we address a wider variety of use cases. And what I would say is that, what customers are clearly telling us that, that they just don’t want to use a net new technology for net new use case, that they want to be able to run more things on platforms and they want to get the benefits of all the best of breed solutions out there. But they want to be able to do that on a fewer set of platforms and that’s where I think we’re really differentiating ourselves, because we truly are a general purpose mission critical platform. When you look at the size of our customer base, the variety of use cases that customers run a MongoDB, the types of customers that use MongoDB, it becomes very, very clear that people can use us for a lot of different things.

Great. Thank you.

The next question will come from Jack Andrews with Needham. Please go ahead.

Good afternoon. Thanks for taking my question. I would ask a bit more on the 5.0 release. It seems to be one of the important features is, you’ve talked about the ability to have a faster cadence of releases between major releases? So could you just flesh out for us, what should we be expecting in terms of, how do you anticipate priorities and focus on when -- what to release when?

Well, I -- we have a pretty rigorous approach, starting our product manager organization leads that process, but we take input from obviously our sales team, our customer support team, our technical sales organization, as well as I know kind of we do some top down analysis in terms of what are the areas that we want to get into. Obviously, we also look at what the competition is doing to understand, whether they’re getting traction and whether or not and that informs our view in terms of how we want to decide, what products to build and what cadence. And obviously, in our space is not like you just build a product and move on, you come out with a MVP release and then you introduce new features or basically mature that product over time. If you look at even Atlas, Atlas only came out five years ago and the level of feature development Atlas, even though it was one product has been enormous. And so these products just tend to mature over time and so there’s a -- there is always some debate about new features and capabilities versus maturing and strengthening the existing set of products. And there’s -- it’s obviously a judgment call and some art, as well as science in terms of how we handle that. And I would say to your point, with a cloud service, we can introduce new capabilities far more quickly than, say, an on-prem version. So we have gone to a quarterly release cycle, which allows us to introduce new features, fix bugs is that much faster, while folding in all the new changes and so forth into our on-prem product once a year. So -- and so that really allows us to continue to innovate fast, but still be able to address the needs of the organization and make sure customers can consume MongoDB’s capabilities at the rate and pace that they want to.

Thanks for the color. Just as a follow up question, could you update us, perhaps, on progress with the systems integrators? Is there a way to frame the proportion of your deals that are maybe SI driven or SI influenced these days?

Yeah. We don’t break out that’s in particular, but I would say, a meaningful percentage of our business is done through some sort of partner. Those partners can come in a variety of flavors. We already talked about the cloud providers. To your point, the systems integrators are another key cohort of partners that we work with. We also work with a bunch of ISVs and they could be either sell-to or sell-through kind of relations with the ISVs. And so our partnerships play a big role. We have a dedicated partner organization focused on our partners. And they play a critical role in kind of helping us expand our reach and accelerate deals, as well as shorten the cycle time to close deals. And with regards to the SIs, historically, we’ve done business with every major SI in the industry and so I can’t think of one larger SI where we haven’t done some business with. We’re obviously picking and choosing the partners we work with where we think we can have the biggest impact. But we’re also working with some boutique partners who have real MongoDB expertise who bring some expertise, especially since many customers may not necessarily have all the MongoDB skills that they want in their own organization and they also provide a valuable role in helping us grow our business.

Thanks and congratulations on the results.

Thank you.

The next question will come from Ittai Kidron with Oppenheimer. Please go ahead.

Thanks. Nice numbers, guys. Just one from me, Dev, maybe you could talk about international, you haven’t talked about your international mix and that performed in the quarter. Maybe you can kind of recap for us how patterns internationally similar or different than they are here in the U.S.? And also is your strategic discussions that you’re having with customers now here in the U.S., is that also something that applies internationally or that’s more of later cycles, say, relative to where you are here in the U.S.

So, I would say, our business is frankly strong across the globe. Obviously, different theaters are -- the size of businesses is different, but we’re seeing significant demand across the globe. I’ll start with Europe. Historically, we’ve been very strong in Northern Europe, and particularly, U.K., but we’ve really expanded very aggressively to Southern Europe, France, Italy, Spain, have become really, really strong markets for us. We’ve also expanded quite aggressively as you imagined to Germany and in Northern Europe, and we’re feeling really good about the opportunity there. In fact, we’re trying to hire as fast as we can. In terms of Asia, we’ve seen a burgeoning demand coming out of India and Southeast Asia. It was funny, our sales leadership, when we first launched Atlas, argue that Atlas, the value proposition would make a lot of sense as the cost of labor was a lot lower in India. Atlas, the value proposition wouldn’t even make as much sense because people just hire their own op -- database administrators will turns out, people value speed, people value being able to innovate and people value being able to offload undifferentiated work. So Atlas is going on like gangbusters. Our India team has been crushing their numbers. So we’re trying to expand that team as fast as possible, same in other parts of Southeast Asia. In China, obviously, we can’t offer Atlas due to regulatory constraints. So we decided, as -- I think you may be aware that we have relationship with both Alibaba and Tencent. And Alibaba we are about in year two of that relationship and that relationship is going really, really well. And Tencent is just starting to heat up. As you know that there’s some, the government there is taking -- there’s a little bit more scrutiny about what the tech companies can do. But we’re not seeing that in our business with those partners. And then, in terms of Latin America, while we don’t have a huge present in Latin America, we’re seeing a lot of demand. So we’re trying to service that through our inside sales team and our self-serve channel and we’re starting to deploy more resources in Latin America. So I would tell you that this market is very large and it’s truly a global phenomenon.

Very good. Good luck. Thanks.

Thanks, Ittai.

The next question will come from Matthew Broome with Mizuho Securities. Please go ahead.

Thanks very much and definitely appreciate the geographic color there on. I guess, sort of a similar question in terms of, sort of, customer that goes, if there are any specific industries that sort of particularly outperformed your expectations or conversely where you’d like to see a bit stronger momentum?

Well, I would say, obviously, it’s a big market. So as you can imagine, our sales teams tend to go where the business is. We tend to not organize by verticals. But that’s something that may change over time, as we see getting going deeper and accounts going deeper in financial services, going deeper into understanding their particular use cases can have disproportionate impact on our business. So that’s something that we’re contemplating. But I would say, in general, we’re seeing strong across the Board performance. MongoDB is truly a horizontal solution and it’s really a function of our coverage model and how many people we have in the region. And because they’re organized geographically, they’ll go after the opposite way, they think that they can have the quickest impact on. So, as you can imagine, companies that are more technology sophisticated tend to be really good customers of ours, because of companies who want to build their own custom applications tend to be really the customers ours. And obviously, every new SaaS company who’s coming out, as we think about the tech stack, we want to be part of that tech stack. So we’re spending a lot more focus on those companies, because as they grow, we’re the beneficiaries of that growth.

Yeah. I would just add if you…

Okay.

I would just add if you think about the Q2 outperformance. We talked about sort of strength across the Board. We also talked about how Enterprise Advanced was particularly strong. And while sometimes you might map that to certain industries, I think, even in the vignettes and customer examples, Dev pointed out, really, it depends on how someone’s, what their architecture looks like and how they’re going to consume software. So it doesn’t perfectly map to the industries. But we had, like I said, very strong performance in Q2 really across the product wise, but particularly in EA. And then when we look out for the second half of the year, we don’t see that -- we’re not counting on that EA performance, when you look at the back half, which obviously, impacts numbers.

Excellent. Thanks again.

The next question will come from Steve Koenig with SMBC Nikko. Please go ahead.

Okay, Hey. Thanks for squeezing me in guys. I’ll just ask one question. So I remember back in the day, at Oracle, when interoperability and portability were big marketing points for them. Now their applications have all been built and the marketing message isn’t so important for them. But new applications are being developed in the cloud, with new databases like Mongo, yet database interoperability is great, multi-cloud is great, but there’s a lot of other past services that apps need to hook into besides database. So can you give us more color on how real multi-cloud is today and the customer challenges associated with implementing it? And I think the broader question is, long-term how do you stay ahead of the major cloud vendors who expand a very good chance of being major forces in this market? Thank you very much and I appreciate the squeezing me in.

Yeah. So when -- if you talk to any developer, they will tell you that the most amount of time and effort that they spend on is working with data. So the database tends to be a place where they spend a particular amount of time and that’s where they have the biggest challenges and that’s where we see the biggest opportunity. So while they have to integrate with other solutions and they may have to build a range of microservices, every microservices, for example, will need a database. And so while applications are getting decomposed into smaller, smaller piece parts, like microservices, the database still plays a very, very important role. And so, yes, when a customer builds an application, they may tie into other services that the cloud provider may offer, but a big factor in terms of what application to build, how quickly they can innovate, how fast they can add features is directly correlated to what database they are using, which is why we win. And I would say that, to your second question, compared to the cloud providers, we have been competing with the largest companies in the world, obviously, Oracle and others in the early days and then the cloud providers, including Amazon and Azure, with their own competitive offerings for the longest time and we’ve held our own. And the reason we’ve held our own is that, we have built a very, very strong set of IP with the document model, it’s proven to be the best way to work with data. Even though it’s an open source product, we have a strong IP moat around it. So the cloud providers cannot just take our free version and compete with us, unlike a lot of other open source technologies. And with the success of Atlas, when we went public, there was some degree of skepticism by some investors about could we really compete by building our own cloud service going head-to-head with the cloud vendors. Well, I think the results speak for themselves. There aren’t many businesses that are growing at over 80% that are at a $0.5 billion run rate and I think that speaks to the IP that we have, it speaks to the value that customers are getting and it speaks to our ability to execute.

Great. Thanks very much again. Thank you.

This concludes our question-and-answer session. I would like to turn the conference back over to Dev Ittycheria for any closing remarks. Please go ahead, sir.

Thank you. I just want to leave you with a few comments. First, I think, what we really want to reinforce is that we believe customers realize that if they want to move fast MongoDB is the best way to do so. Second, Atlas’ growth of 83% reinforced the point that customers want a multi-cloud platform that enables them to innovate quickly and outsource the undifferentiated heavy lifting of managing their data infrastructure. Third, we continued investing and evolving a go-to-market strategy across field sales, inside sales and sell the self-serve channels to capture this large market opportunity. And last but not least, we continue to rollout significant innovation to improve our platform through both ease-of-use and expansion of capabilities to encourage more and more customers to use MongoDB. So thank you for your time and we’ll talk to you next quarter. Take care.

The conference has now concluded. Thank you for attending today’s presentation. You may now disconnect.