Good day, everyone. Welcome to MongoDB's second quarter 2019 earnings call. Today's conference is being recorded. At this time, for opening remarks, I'd like to turn things over to Mr. Brian Deneu. Please go ahead, sir.
Thank you, Kellyanne. Good afternoon, and thank you for joining us today to review MongoDB's second quarter fiscal 2019 financial results, which we announced in our press release issued after the close of market today. Joining me on the call today are Dev Ittycheria, President and CEO of MongoDB, and Michael Gordon, MongoDB's CFO. During this call, we may make statements related to our business that are forward-looking under federal securities laws.
These statements are made pursuant to the safe harbor provisions of the Private Securities Litigation Reform Act of 1995, including statements related to our financial guidance for the third quarter and full year fiscal 2019, our market opportunity, our go-to-market and growth strategies, our introduction of future product enhancements, the potential advantages of those enhancements, and the impact of these product enhancements on our gross margin and sales opportunity, our ability to expand our leadership position and drive best-in-class revenue growth, and the anticipated benefits of our platform for our customers and partners. The words anticipate, continue, estimate, expect, intend, will, and similar expressions are intended to identify forward-looking statements or similar indications of future expectations. These statements reflect our views only as of today and should not be reflected upon as representing our views as of any subsequent date.
We do not have plans to update these statements except as required by law. These statements are subject to a variety of risks and uncertainties that cause actual results to differ materially from expectations. For discussion of the material risks and other important factors that could affect our actual results, please refer to those contained in our annual report on Form 10-K filed with the SEC on March 30th, 2018, and our other periodic filings with the SEC. These documents are available in the investor relations section of our website at www.mongodb.com. A replay of this call will also be available there for a limited time. Additionally, non-GAAP financial measures will be discussed 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. Thanks to all of you for joining us today to review our second quarter results. We are incredibly pleased with our second quarter performance, which reflects the positive impact the investments in our product and go-to-market efforts are having on the business. To quickly summarize our second quarter results, we generated revenue of $57.5 million, a 61% year-over-year increase, which was above the high end of our guidance. We grew subscription revenue 63% year-over-year. We ended the quarter with over 7,400 customers, up 72% compared to a year ago. We saw strong growth across all major regions, including North America, EMEA, and Asia. Atlas revenue grew more than 400% year-over-year and now represents 18% of revenue. We raised $254 million in net proceeds from our successful convertible notes offering. Our second quarter results further demonstrate MongoDB's clear leadership as the modern database platform of the future.
Customers recognize that MongoDB offers the best way to work with data, to put data intelligently where it's needed, and to allow customers to run applications anywhere. The MongoDB platform offers sophisticated ways to manage data, and we are extending that further with the introduction of global clusters in MongoDB Atlas. This groundbreaking technology allows customers to easily create policies to strategically distribute data closer to their users for low-latency read and write operations. In addition, with this feature, customers can easily comply with the ever-changing and increasingly demanding regulatory environment for managing data, like Europe's new GDPR rules. This is a big competitive differentiator for us, as it is incredibly challenging, if not impossible, for companies to orchestrate these types of sophisticated data policies with legacy databases.
Our ability to address these types of complex data problems is a significant driver in the increasingly strategic nature of our conversations with customers. Turning to second quarter results in more detail, we again saw a healthy mix of new logo wins and strong upsell activity, both of which included customers migrating existing workloads from legacy databases to MongoDB. Our performance in the second quarter exemplified the power of our land, expand, and expand model and our multiple vectors of growth. During the second quarter, we added a number of new enterprise customers, including Canon U.S.A., Coinbase, Monitran, IPC Systems, Royal Caribbean Cruises, and Service NSW. We also expanded our relationship with customers such as Apervita, Cisco, Fresenius Medical Care North America, HSBC, Maple Leaf Sports & Entertainment Partnership, Squarespace, the Bank of Nova Scotia, and ClickTech.
As we expand the functionality of the MongoDB platform and build deeper relationships with our customers, we are seeing those customers turn to MongoDB to support an ever-increasing variety of use cases. Coinbase, a leading global digital currency wallet and platform, made a strategic decision to build its business on MongoDB in order to rapidly develop its capabilities and fuel the growth and scale necessary to be the market share leader in the hyper-competitive cryptocurrency exchange industry. The company continues to invest in MongoDB to extend its platform, better handle traffic spikes of peak trading hours, and to serve a growing global customer base. Squarespace, one of the largest SaaS-based website building and hosting platforms, chose MongoDB as the standard for its core website platform. This is a great example of an innovative company building an integral part of its business on top of MongoDB.
Medable, a platform enabling users to build HIPAA-compliant applications and services, was recently approved by the FDA to collect and analyze data from clinical trials, has built their system on MongoDB. Due to the nature of the data managed, Medable relies heavily on MongoDB's robust security features and flexible data model to rapidly add features and make schema changes to serve the needs of their business. Maple Leaf Sports & Entertainment, the largest sports and entertainment company in Canada and owners of the Toronto Maple Leafs, Raptors, Argonauts, and Toronto FC, needed to consolidate customer information that was spread across more than five different sources into one holistic view. The lack of a unified customer repository was leading to inefficiencies, lost revenue, and the potential for missed customer service opportunities for MLSE.
They chose MongoDB due to our proven track record with other large entertainment companies and our ability to support their cloud-first mandate. HSBC, a longtime MongoDB customer, once again expanded its relationship with us as it continues on the path of its digital revolution. Embracing a board-level directive to use technology that makes its operations simpler, better and faster, HSBC is migrating several trading app platforms from relational databases to MongoDB in order to simplify, migrate, and manage complex financial data transactions. Hancom, a Korean provider of office productivity tools, is using MongoDB as a core component of its ThinkFree Office online suite. The company needed the scalability and flexibility of MongoDB to support its microservices architecture with a low total cost of ownership to address their key strategic priority of offering a cloud-native version of ThinkFree.
Turning to Atlas, we saw a large number of new customer wins during the quarter, as well as better-than-expected usage from a number of existing customers. Atlas now represents 18% of revenue versus 5% a year ago and 14% last quarter. In two years, Atlas has scaled from zero to $40 million revenue run rate and generated more than 400% growth over the past year. In addition to offering lower operating costs and improved development velocity, a key attribute of Atlas is that it provides elastic capacity for customers when they experience spikes in usage for their applications. There's a particularly strong product market fit for Atlas with customers who have a cloud-first strategy, which enables our sales reps to sign more deals, bigger deals, and quicker up-sells within this market segment, which all contribute to meaningful productivity increases.
FTD Companies, a premier floral and gifting company, is leveraging MongoDB Atlas as part of its digital transformation initiatives. Specifically, FTD is utilizing Atlas to deliver new experiences for its customers and network of member florists, provide true omni-channel customer service, while also beginning the process of moving to a cloud infrastructure. During the quarter, we introduced many of the premium features of MongoDB Enterprise Advanced into Atlas, including sophisticated new security features like encryption key management, LDAP integration, and database auditing. We also introduced a secure Atlas environment for healthcare customers that is fully HIPAA compliant. Apervita, a leading healthcare cloud analytics platform serving over 1,200 hospitals, expanded its use of MongoDB after Atlas became HIPAA compliant. By leveraging the complex data to create predictive models, the company helps healthcare professionals deliver more effective care.
MongoDB powers the Apervita platform, massively simplifying the process of connecting health data to analytics. By providing the scale and robustness required for a real-time big data environment, clinicians have the ability to run analytics and algorithms against patient data and deliver improved clinical outcomes. We expect the introduction of Enterprise features in Atlas to be a catalyst for our sales organization. With Enterprise features, Atlas can now serve the needs of the most demanding and sophisticated customers who want to consume MongoDB as a service. Royal Caribbean, one of the world's largest cruise lines, chose MongoDB Atlas to optimize the cruise search application on its e-commerce platform to increase revenue and reduce churn.
One of the exciting aspects of this win is that it was driven by the e-commerce team inside Royal Caribbean's marketing organization, who within three months went from having zero MongoDB experience to launching a mission-critical application on Atlas. While our second quarter results were impressive, we are not standing still. We continue to invest in our platform to push the pace of innovation and deliver even greater value for our customers. During the quarter, we hosted our annual user conference, MongoDB World, in New York. More than 2,000 developers, customers, partners, and investors experienced a day of product introductions, training, customer testimonials, and most importantly, shared ideas and best practices among the MongoDB community. The highlight of the event was the formal introduction of MongoDB 4.0.
As we have discussed in the past, 4.0 includes multi-document ACID transactions, which combines the speed, flexibility, and power of the document model with ACID guarantees. ACID is having a positive impact in our conversations with prospective and existing customers by enabling a greater number of discussions about the strategic role that MongoDB can play in their digital transformation initiatives. MongoDB 4.0 included far more than ACID transactions. I would like to call out a few of the highlights. Stitch, our new serverless platform, is now generally available. Stitch makes it easy to build modern cross-platform applications on MongoDB without developers having to do the tedious work of managing the back end of an application. With Stitch, the app server is no longer required, and developers can use the MongoDB query language directly from front-end code, as well as to connect to third-party services.
Stitch will dramatically increase the velocity of development while allowing teams to focus on only value-added code. We announced the beta of MongoDB Mobile, which will extend the power of MongoDB all the way to the network edge on IoT assets, as well as iOS and Android devices. MongoDB Mobile enables real-time automatic syncing of data between the device and the back-end database, which will significantly enhance development velocity and application performance. To support our mission of giving customers the freedom to take advantage of an on-premise, hybrid, and public cloud infrastructure, we have also introduced a new MongoDB Kubernetes operator in beta. This solution will support the provisioning and orchestration of MongoDB within a Kubernetes environment. We are incredibly proud of the innovations introduced in MongoDB 4.0, and we believe it will significantly raise the bar for the value we deliver to customers.
With 4.0 successfully launched and generating significant customer interest, our engineering team is already hard at work executing on the robust product roadmap we have laid out for the coming years. To summarize, we delivered terrific results in the second quarter. We are executing well across all aspects of the business, and we're seeing strong returns on the product and go-to-market investments we are making. We are in the early stages of disrupting one of the largest markets in technology, and our position continues to strengthen with each passing quarter. With that, let me now turn the call over to Michael to review the financial results.
Thanks, Dev. As mentioned, we're very pleased with our second quarter performance, and it was our fourth strong quarter as a public company. 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 2019. Total revenue in the quarter was $57.5 million, up 61% year-over-year. Subscription revenue was $52.9 million, up 63% year-over-year. Professional services revenue was $4.6 million, up 48% year-over-year. In addition to our strong net customer acquisitions and expansion activity, we also recognized approximately $1.5 million of revenue that we had not anticipated during the second quarter. This was primarily due to a greater contribution to revenue from new contracts signed in the quarter, as well as the favorable impact related to bundled services subscriptions.
Recall, when we sell software and services on a bundled basis, we do not begin recognizing subscription revenue from customers until the delivery of services has commenced. In Q2, this led us to start recognizing revenue from these customers in the second quarter versus our expectation that they would begin in the third quarter. The second quarter was also another strong quarter for MongoDB Atlas. Atlas represented 18% of revenue during the quarter, up from 5% in the year ago period and 14% last quarter. During the quarter, we experienced some large Atlas wins, a few of which generated additional revenue as a result of testing, launching, or migrating their applications. This reflects the elastic nature of cloud-related workloads and serves as a reminder that customers can have periods of elevated or reduced usage based on customer-specific factors, including the application's life cycle.
We continue to see strong global demand for our offerings. During the second quarter, we grew our customer base by approximately 800 customers, bringing our total customer count to over 7,400 customers, which is up from over 4,300 customers in the year ago period and over 6,600 customers at the end of last quarter. Of our total customer count, over 1,600 are direct sales customers, which compares to over 1,550 at the end of the prior quarter and over 1,350 in the year ago period. The growth in our total customer count is driven largely in part by Atlas, which had over 5,300 customers at the end of the quarter, compared to over 4,400 customers at the end of the first quarter.
The growth in total customers includes growth in our Enterprise Advanced customers, as well as new Atlas customers. It's important to keep in mind that the growth in our Atlas customer count reflects both new customers to MongoDB as well as existing EA customers adding incremental Atlas workloads. We also continue to see healthy expansion from our existing customers. Our net ARR expansion rate in the second quarter remained above 120% for the 14th consecutive quarter. We ended the quarter with 438 customers with at least $100,000 in annual recurring revenue and annualized MRR, which is up from 394 in the first quarter and 296 in the year ago period. Driving expanded adoption and spend among existing customers is a key component of our growth strategy and has been a consistent area of success.
Even among our largest customers today, we believe MongoDB comprises a small fraction of their total database spend, which represents a large and attractive growth opportunity for us over time. Moving down the P&L, I'll be discussing our results on a non-GAAP basis unless otherwise noted. Gross profit in the second quarter was $41.8 million, representing a gross margin of 73%, which was slightly better than the year ago period. We are pleased with the gross margin performance in the quarter, particularly in light of Atlas's growth. Atlas includes the underlying infrastructure and our success in reducing the infrastructure costs related to Atlas have resulted in improved Atlas gross margins. We have now begun to introduce the premium Enterprise Advanced features into Atlas, starting with advanced security. We expect this will be an incremental benefit to revenue and gross margins going forward.
We still anticipate Atlas will be a modest headwind to gross margins overall. We are tracking well relative to our original expectations. Our operating loss was $21.6 million or negative 38% operating margin for the second quarter, compared to a negative 60% margin in the year ago period. The more than 2,000 basis point improvement in operating margin reflects the benefits of our increased scale while we invest in the continued growth of the business. Net loss in the second quarter was $21.1 million, or $0.41 a share, based on 51.2 million average weighted shares outstanding. Turning to the balance sheet and cash flow, we ended the quarter with $523.2 million in cash equivalents, short-term investments, and restricted cash. The increase in our cash balance reflects the $254 million of net proceeds from our successful convertible notes offering in June.
These notes are due in 2024 and have a coupon of 75 basis points. We entered into capped call transactions that raised the effective conversion price of the notes to $106.90, a 100% premium to our share price at the time of the transaction. This was an opportunistic financing to raise additional capital at advantageous terms. Operating cash flow in the second quarter was -$16.9 million, after taking into consideration approximately $1.2 million in capital expenditures. Free cash flow is -$18 million in the quarter. As a reminder, the second quarter is typically the low point in the year for operating cash flow due to seasonally low collections, and the second quarter is usually our heaviest investment in marketing events like MongoDB World.
In the second quarter, we began to incur capital expenditures associated with our New York City office move, and we expect to see capital expenditures at an elevated level in the third quarter as a result. Short-term deferred revenue was $125.5 million, up 44% year-over-year, while total deferred revenue of $145.8 million was up 38% year-over-year. We believe longer-term trends in deferred revenue are directionally correlated to the underlying momentum of our business. That said, as Atlas continues to become a larger portion of our business, it is important to appreciate that it is a usage-based model and does not generate meaningful deferred revenue. As a reminder, Atlas is often billed monthly in arrears versus the annual in advance billing terms we see with our Enterprise Advanced customers.
Quarter-over-quarter comparisons of deferred revenue could also have some level of variability due to the timing of events that may occur. I'd now like to turn to our outlook for the third quarter and full fiscal year 2019. For the third quarter, we expect revenue to be in the range of $59 million-$60 million. Non-GAAP loss from operations is expected to be in the range of -$21 million to -$20 million, and non-GAAP net loss per share to be in the range of -$0.40 to -$0.38 a share based on 52.3 million weighted average shares outstanding. For the full year fiscal 2019, we are raising our revenue outlook to $228 million-$230 million.
We are reiterating our non-GAAP loss from operations is expected to be in the range of -$84 million to -$82 million, and non-GAAP net loss per share to be in the range of -$1.66 to -$1.62 per share based on 51.6 million weighted average shares outstanding. Our increased revenue guidance reflects strong underlying trends in the business, and given the high ROI investment landscape we see, we've maintained our full-year outlook for non-GAAP loss from operations. Please note that our updated outlook reflects approximately $1.5 million of incremental public company expenses in the second half of the year, in part driven by the anticipated loss of our emerging growth company status under the JOBS Act. In closing, MongoDB delivered a strong second quarter performance and we're well-positioned as we enter the second half of fiscal 2019.
The company is performing well at a high level, and we are pleased with the attractive returns we are generating from our investments and the resulting growth. With that, we'd like to open it up to questions. Operator?
Thank you. At this time, if you do have a question, that will be star 1. Again, star 1 for questions. We'll hear first from Raimo Lenschow with Barclays.
Hey, congrats from my side. Two questions on Atlas, if I may. First, Dev, can you talk a little bit about the partnerships and what they're bringing to the table that you're seeing around Atlas distribution around AWS and IBM? I know IBM is a little bit early, but just what has been the reception there? What's AWS doing to help you? That's my first question.
Sure. Just to be clear, so with regards to IBM, our relationship with IBM today does not include Atlas. It is designed for our on-prem MongoDB Enterprise Advanced product. In terms of AWS, what AWS has really helped on the demand fulfillment side, because customers can choose to procure Atlas through their marketplace program. What allows the customer to do is really reduce the friction in the process of basically procuring Atlas when they decide that MongoDB is their preferred choice. We also do obviously participate in a number of AWS summits around the world. Obviously, they tend to bring lots of people, especially developers, to these conferences, and we view that as an opportunity to basically speak about what we're doing with MongoDB and Atlas in particular.
Okay, perfect. The next one on Atlas is, if you think about the, now that you're starting to have the enterprise features available, what are first examples in terms of how people are going to adopt this? Is this going to be like a lot of tests in development initially? Are people quickly moving over and using it? Can you just give us a little bit of feedback how you see that? Thank you.
I think, the enterprise features in Atlas is just allowing us to go after even workloads that have very strict, for example, security requirements. With the new features we have in Atlas, like enterprise key management, customers can bring their own keys and have comfort that no one else can see their data. We allow integration to LDAP. We allow you to do very sophisticated auditing of the database. For those customers who have those extra level of security requirements, it really enables them to feel very comfortable of moving their workloads to the cloud on Atlas. It really expands the, what I'd say, the addressable market of Atlas.
Allows customers to just be more and more comfortable of going to the cloud using MongoDB Atlas.
Perfect. Thank you. Well done.
Thank you.
We'll hear next from Sanjit Singh with Morgan Stanley.
Thank you for taking the questions. Congrats on the accelerating growth trends of this quarter. I wanted to follow up on Raimo's question, and just sort of talking about the enterprise opportunity, not just with Atlas, but given multi-document ACID support, you're rolling out global clusters. Dev, maybe can you help us understand, where does a customer lean more towards Enterprise Advanced versus Atlas, and what is your sort of view on how enterprise adoption's going to unfold throughout the balance of the year versus your commercial business? Thank you.
Yes. Our strategy, one of the key differentiating points about MongoDB is really give customers the freedom to run their workloads anywhere. Today, we have customers who run MongoDB on the mainframe. We have lots of customers who run it on-premise, and as you can obviously see with the Atlas results, we have lots of customers who are now consuming MongoDB as a service. I should also say we also have lots of customers who buy Enterprise Advanced, but self-manage it in the cloud as well. We literally run the gamut of all the variety of options, and we just believe that it's important to give customers choice. Every customer is at a different stage in their journey to the cloud. We have lots of government agencies who are very careful and frankly, cannot use the public cloud infrastructure today.
We have lots of financial services customers who, for regulatory reasons, cannot use the public cloud today. We address their needs through our capabilities on-prem. We have lots of other customers, even large enterprises to emerging startups, who are moving either select workloads or their entire business to the cloud. Having that choice really allows us to serve a wide spectrum of needs. In terms of directionally, we clearly see everyone is on some journey to the cloud. We see the cloud becoming an increasingly important part of the business for MongoDB. Obviously, the Atlas results speak for themselves. The other advantage I think that we give customers is not just freedom to run on the cloud, but to run on any cloud provider.
One of the things that we hear, and we see a lot of enterprises do now is try and work with multiple cloud providers. They may have a primary and then a secondary. The comfort they have with going with MongoDB is that it's very easy to move applications from one cloud provider to another cloud provider. They don't have to worry about being locked into any one particular cloud. That's another big advantage of using MongoDB.
I appreciate that. I appreciate the answer. Maybe a follow-up question and sort of thinking down the road in terms of serverless. I know you guys are rolling out Stitch as well. Just maybe more higher level, as customers gravitate more towards serverless computing methods, what do you see as sort of the impact on the business in terms of the demand for database services from MongoDB's perspective?
Yeah, I mean, the company was basically founded to make a developer's life really easy, to really let developers and organizations move very quickly in being able to develop applications that drive the business. What basically serverless does for us is that it really allows developers to avoid all the mundane and tedious back-end work that they normally have to do, and basically only focus on value-added coding. That becomes really important because as customers, and specifically developers, think about what platform to use, they'll naturally gravitate to platforms that make their lives significantly easier.
MongoDB's popularity was driven by the fact that the document model and our approach just makes a developer's life so much easier by giving them a very easy way to work with data, by making it very easy to move and put data where you want it from a scalability, reliability, availability point of view. Stitch just takes that to the next level, where they can basically not have to deal with all the back-end tedium work they have to do to build any web or mobile app. What Stitch does is allow you, for example, to essentially expose the power of the database through front-end code, where you can basically query the database from the client side.
It allows you to easily integrate to third-party services, whether it's a payment service like Stripe or a notification like Twilio, or even an internal service that you may have. With Stitch now, you can use Stitch to sync data between your mobile device with MongoDB Mobile to the back-end. There's even things like with Triggers or what we announced previously with change streams, you can now easily enable the ability to take action on events or changes in your database. When you think about where the world is going, JSON is becoming the synonymous with the word modern applications. MongoDB is the preeminent JSON database, and you should think about Stitch as really the lubricant that allows people to move very quickly and faster in building applications.
Makes a lot of sense. Congrats on the strong quarter.
Thank you.
We'll hear now from Heather Bellini with Goldman Sachs.
Hi, great.
Hi, Heather.
I had two questions, if you will. Hi, how are you? I wanted to follow up on what you were talking about with Stitch and talking about serverless. I was just wondering if you could give any color on how you're seeing people deploy applications, kind of momentum between serverless and containers. Give us your take. Also, I wanted to ask a little bit about the NoSQL competitive landscape and just see how you would stack things up right now and the breadth of your product offering and how it stacks up versus the competitive universe, if you've noticed any changes in you guys pulling ahead of the competition. Thank you.
Yeah, sure. I want to just clarify. Containers, basically the world is moving to containers because it's just an easy way to manage infrastructure. Kubernetes has become the de facto platform that everyone is gravitating to. There were a few other options a few years ago, but Kubernetes has become the standard. What we have done is basically create an operator for Kubernetes, where people from the Kubernetes platform can basically manage provisioning and orchestrating and basically migrating databases on a containerized environment. Customers are incredibly excited about that because as people move to containers, it becomes as easy to manage MongoDB, because we support those containerized environments. Stitch is all about enabling developers to basically become much more productive and move much more quickly in building applications. Everyone is under pressure to try and increase the development velocity of the development teams.
The way you can do that is by giving them a very modern platform that allows them to build applications quickly, to add features quickly, and to basically reduce the need to do a lot of what developers consider a lot of mundane and tedious tasks. For example, with Stitch, you don't have to use an app server anymore because typically the app server is where you program the application logic. Now you can do that from front-end code, where the intelligence moves to the client side and basically query the database and basically eliminate the need for that middle tier. That makes a developer's life very easy. Plus, invariably, as you move to a microservices architecture, there may be third-party services or internal services you want to integrate to. Stitch makes that incredibly easy.
There may be things that you want to do when there's changes happening to your database. For example, I'll use an example where, say you're an airline company, and you decide to move the flight from New York to Phoenix from one gate to another. When that database event happens, you can automatically generate a trigger that sends a notification to everyone's mobile app saying, "This gate has changed." Today, it's done on a pull notification. Now you can push those notifications out. These are all things that if you didn't have Stitch, would make a developer's life a lot more complicated, and they have to spend a lot more time coding these applications. Stitch allows developers to really abstract all that mundane work and really focus on value-added development.
Great. Just the competitive sphere with all this that you're putting out there, have you noticed a widening in your lead? Any comments on kind of the competitive universe that you could share?
Yes. We do not frankly see other NoSQL vendors in deals anymore. I'm sure that they're getting deals, but we frankly see them less and less. I can't remember the last time I had a sales rep complain to me about a competitive situation with another NoSQL competitor. I think it's become clear to everyone that we have become the de facto leader in the modern database space. Now customers are just contemplating what workloads do they move to the cloud and what new apps do they build on MongoDB. That's where our salespeople are spending the most time.
Okay, great. Thank you.
Thank you.
From Stifel, we'll hear from Brad Reback.
Great. Thanks very much. Dev, the last few quarters, I think the last three in a row, you've added about 1,000 Atlas customers sequentially. Should we think about that as the sustainable rate going forward, or is there an opportunity to step that up? Thanks.
There's two parts to our Atlas business. It's our self-serve business and our sales-serve business. Our self-serve business, we started first, we got a lot of traction very quickly. For the last, I would say, year, we've been really focused on enabling our sales force to drive Atlas deals, those deals tend to be significantly bigger than the self-serve deals. We're seeing material progress and growth on the sales side. I think you're going to see us continue to invest and innovate on both sides of the business. We think the self-serve channel is a very unique channel for us. It's basically servicing the long tail of our business, especially in markets that we don't necessarily have a presence in. You'll see us, we already are investing even more aggressively in our self-serve business.
You're going to see us invest in both aspects of the business. I think what we're really pleased with today is just the uptake on the sales side, where we're seeing material contribution and bigger and bigger deals happening more quickly and quicker up-sells from the sales organization, which we're very happy about.
Maybe one quick follow-up. As you think about your future acquisition strategy given the recent capital raise, are there any real pressing needs or will it be very much a tactical type of execution going forward?
Yeah, we really considered the ability to raise capital last quarter as really opportunistic. We didn't have any near-term needs to deploy that capital for either M&A or any other kind of operational needs. We just found an opportunity to raise a lot of cheap capital. It clearly allows us to be more aggressive should the opportunity arise. Right now, we have no near-term pressing needs to use that capital.
Great. Thanks very much.
Thank you.
Again, for questions, that is star one at this time. We'll hear now from Jack Andrews with Needham.
Good afternoon. Thanks for taking my question. Dev, on the last earnings call, you referenced some 20-plus conversations you were having with C-level executives in terms of just the increasing strategic importance of MongoDB. I was wondering if you could update us on the amount of conversations you're having and just where are those conversations leading today?
I would say that those conversations are frankly increasing. We have changed our sales methodology, where we're asking our salespeople, once they do sufficient homework on an account, to go high in the organization as quickly as possible for a number of reasons. One, to qualify where the real demand and interest is in potentially using MongoDB. Two, to educate those senior-level stakeholders on our differentiation and value proposition. Three, to basically increase the velocity of business. Even if you get a deal, if you have the air cover, it's much easier to go ask for the follow-on deal because the senior-level stakeholders are now fully aware of the value we can add. Now we've changed our engagement model, where we've institutionalized that, where we try and get high very early in the sales process, and that's starting to pay big dividends for us.
Thanks. Then just as a follow-up, could you update us on terms of how you're thinking about the mainframe modernization opportunity in particular? What's the sense of urgency from customers around mainframe-based applications?
Yeah. It really varies. As I said, we do have some customers who are happily running their mainframes and want to run MongoDB, because at some point in time, they do recognize that there's a certain half-life to their mainframe real estate. So they want to potentially migrate their applications while running on the mainframe, then have an easy glide path to a more modern compute environment, whether it's on-prem or in the cloud. That's point number 1. Point number 2, we do see in many situations where the use cases or the changing nature of their needs of the business is requiring them to consider offloading workloads from the mainframe to a more modern computing architecture. That's where customers are very interested.
We have lots of proof points where we have customers, large banks, large tech companies, service companies, and so forth, who are moving workloads off the mainframe onto MongoDB. What we try and figure out is what is the problem or the pain that the customer is having, whether it's a cost problem because the MIPS utilization on the mainframe is getting too high, whether it's a performance problem because they can't really address the needs of their users. Then we will then obviously work with them and help them think through all the available options. The mainframe offload use case is a very popular one in our sales force, but there's many others as well. It's really depending on what's going on in that particular account.
Great. Thanks for taking my questions.
Thank you.
We'll hear next from Brent Bracelin with KeyBanc.
Thanks for taking the question. Dev, maybe for you, I wanted to go back to the quarter. If I look at just the revenue growth, 61% growth is the highest we've seen here in two years. On a sequential basis, 19% growth is the highest we've seen also on record here in the last couple of years. My question is, why now? Why are you seeing this acceleration in the business? Is it a confluence of internal factors that are driving it? Even if I look at the Mongo business ex Atlas, it also accelerated. Walk us through why you think this is happening, how much of it is company-specific things you're doing internally versus just the external factors and the market being ready for a more modern database. Thanks.
Thank you. We do feel good about our position. We do feel good that every quarter we're getting more and more credible with customers and being really the default modern database for all their use cases. We do feel like we, as an organization, are executing better. The efficacy of our go-to-market efforts are just getting better. We're expanding to different regions. We also think the product roadmap and product execution has been incredibly strong. We feel very good about not just the core product, but obviously Atlas has grown really quickly. We've added new features and capabilities. We've rolled out new products like Stitch and Mobile. We feel like it's not one thing.
I would also say, Michael talked a little bit about this in his prepared remarks, there were some one-time events that happened, I would say, in Q2 that we just didn't expect. I wouldn't want you to extrapolate that this is the new normal. We obviously feel very good about the state of the business and the trajectory of the business.
Helpful. Then as a follow-up for Michael, maybe if I look at the gross margin profile here, I guess it's a little surprising that you're able to hold the gross margins even with the strength that you're seeing in Atlas. Can you just walk us through with that material mix shift to Atlas, how you're able to sustain the gross margin profile here? Thanks.
Yeah, sure. As I mentioned earlier, we've made very good progress on the Atlas gross margins relative to our expectations, and we're tracking well ahead of plan, in terms of gross margins. Atlas is still lower gross margin than the balance of the business. We still have plenty of levers to flip or turn and dials to adjust on the business. We mentioned that the first thing that we had done, which we'd said we'd do by the end of the year, is we've introduced some of the premium features in Enterprise Advanced, meaning principally the advanced security features, into availability in Atlas. We've not yet seen the benefit of that because we only just introduced that. Over time, that should be very accretive, both from a revenue perspective as well as from a gross margin perspective.
There are some internal cost optimizations that are also available to us. I think the short answer is we've had very strong execution relative to our kind of margin game plan for Atlas. We've got more work that we want to do on that front, but we're very pleased with the progress to date.
Very helpful. Thank you.
Thank you.
From JMP Securities, we'll hear from Pat Walravens.
Oh, great.
Hi, Pat.
Thanks. Let me add my--
I think we lost you, Pat. Pat, are you still there? Operator, I think we may have lost Pat.
We'll move on to Brian White with Monness Crespi.
Hey, Dev. I'm wondering how we should think about competition from the leading public cloud vendors. They both had conferences over the summer. Database was a major focus, a lot of new innovations. I know Google was playing up the Cloud Firestore, NoSQL database, and they did an update recently. Maybe if you could just give us some color on how we should think about these big competitors. Thanks.
Obviously, we have great relationships with the cloud providers themselves. Just to remind you, they're the ones who helped fund the development of Atlas onto their particular cloud platforms. They did so because they saw the amount of MongoDB usage on their specific clouds. I think the second thing I would say is that, one of the things that's always been a strength of MongoDB is the developer mind share that we've had and the popularity of the platform. I would say that doesn't happen overnight. We've been shipping product for over 10 years now, almost 10 years now. The people are very familiar with the product. The feature set is far superior to any other modern database. I would say most of the database offerings from the cloud providers have two core limitations.
One, they tend to be built on key value stores, which have far more limited functionality in terms of the expressiveness of the query language and other features that they just don't have. The second thing is they really lock in a customer onto that specific cloud platform. I think most customers today are much more sensitive about lock-in than they have been in the past, especially given the state of their relationships with legacy database vendors. That's another consideration. With MongoDB, you truly have the freedom to run MongoDB anywhere. It is truly one of the most popular, in fact, it's the most popular modern database in the world today. They've also seen just the rapid innovations that we've had to offer, we feel very good about our positioning.
With support for ACID on 4.0, are there new use cases, I know it's early, but that are coming into the conversation that maybe you didn't see before?
Oh, most definitely. The level of conversations and the tone of conversations has changed radically since we announced support for ACID. I think it's taken off the potential objection people had is that could they really use us for certain use cases where ACID-type data guarantees was required. It's really helped change the nature of the conversations, we feel like it's only expanded the aperture of use cases we can go after.
Great. Thank you.
For questions, that is star one. We'll move next to Tyler Radke with Citi.
Hi there.
Hi, Tyler.
Thanks for taking the question. Hi there. Can you hear me okay?
Yep. Yes.
Okay, great. Sorry, I'm running around different calls today. Apologize if my question's been asked already. I just wanted to ask you about among your existing customers, just what that looks, I guess, in terms of Atlas, what that looks like in terms of adoption by existing customers that are using the self-managed version of MongoDB versus net new, how that's kind of split today?
Well, just so we're all clear, Atlas is a different consumption model. You have to have chosen MongoDB for your database, for your application before you would consider using Atlas. What Atlas does, it allows you to basically outsource all the ongoing provisioning, management, backup, patching, updating of your infrastructure, and really allow you to focus on allowing you to build better apps that can address the needs of your business. We tend to see all types of customers. Customers moving new workloads onto Atlas. We see customers migrating existing workloads onto Atlas. We see customers who are using MongoDB on-prem which spin up new instances on Atlas. We see development workloads on Atlas, we see test workloads on Atlas, and we see production workloads on Atlas, and we see this globally. Atlas is the most widely available database service offering.
Today, I believe it's available in 57 different regions. No other database service vendor can claim that because of the virtue that we can run across Amazon, Google, and Microsoft's real estate. In terms of geo coverage, we are the most widely available offering. We tend to have customers almost across every industry, nearly every geography, using Atlas in some way, shape, or form.
Great. It sounds like combination of existing as well as new. Just a follow-up. On the competitive environment, I was just wondering if there's any update there either from the legacy players, and maybe a comment, I might have missed it, on just what % of your deals are involved in legacy displacements. Also, I'd be curious to hear your take on the competitive environment in the non-legacy world and in the NoSQL world, if you will. Thank you.
Yeah. We tend to see about 30% of our business typically on average every quarter be migrations of legacy workloads to MongoDB. We continue to see lots of existing workloads move to MongoDB. Obviously, we also see lots of new workloads coming to MongoDB because it's so much easier to build application to MongoDB than a relational database. In terms of the new vendors, this question was asked before, we typically are not seeing some of the other NoSQL players anymore. I think the market has clearly consolidated around MongoDB, and we see that in terms of people standardizing on MongoDB, at minimum as one of the core database platforms that they plan to use in their enterprise.
From a competitive point of view, I would say the legacy vendors are more competitive from a wallet share where they have an existing share of the wallet. From a technology point of view, they're becoming less and less relevant.
Okay. Thank you.
Thank you.
We'll go back to Pat Walravens.
Great. Thank you.
Hi, Pat. Welcome back, Pat.
Hi. Sorry about that. I'm sorry. I accidentally hung up on myself. I have two questions. One is sort of following up on these competitive questions. If you look specifically at, Oracle seems to be trying to react. They have the self-healing functionality, and they're pushing the database in the cloud, and the database in the cloud is cheaper. What's the customer's reaction to that? Is it going to work? Do you think the pace of migration from Oracle to Mongo accelerates?
I would tell you that, since I've been with the company, now I'm coming close to my four-year anniversary, I would say the antipathy towards the legacy vendors has never been higher. We just see customers very motivated to move off their legacy platforms as a function of their relationships with those vendors. That's one big reason. The second big reason is that the architecture of these legacy databases is frankly old. The relational database, the first white paper came out 50 years ago, Oracle was founded 41 years ago.
Yes, they've obviously added lots of features and capabilities, but if you want a very modern platform that allows you to scale gracefully, that allows you to add features very quickly, that allows you to move data easily all around the world to serve your user base, you can't really do that easily on a legacy database. When you look at the computer science programs that the leading colleges have, MongoDB is one of the most popular technologies that students develop on today. I had one customer state publicly at MongoDB World that once you go MongoDB, you can't go back. Right? MongoDB is a much more compelling platform to build applications on than relational databases. We see that happening as well. That's a big driver to why customers are going with MongoDB.
Great. My follow-up is more specific. How important are graph databases and how does that work for Mongo?
Graph databases were designed for certain use cases around mapping, say, social profiles and independent relationships between who your friends are or social interconnections. We've actually already embedded a bunch of graph functionality into MongoDB, and you'll see us continue to add more functionality over time. We don't believe it makes sense for a customer to choose a net new database for every net new use case. It just doesn't become scalable. It's hard to manage, hard to support. It's hard for your developers to learn all these different technologies. We see customers increasingly standardize on MongoDB because we address the widest set of use cases available in the marketplace.
All right. Great. Thank you very much.
Thank you, Pat.
Thanks, Pat.
At this time, I'd like to turn things back over to Dev Ittycheria for any closing remarks.
Well, thank you again for joining us on this call. I'd like to reiterate, we feel really good about the business. We're very proud about what we accomplished in Q2, but we know that we have a huge opportunity in front of us, and it's back to the grindstone for us. Thank you again for joining the call, and we wish you well. Take care.
That does conclude today's conference. Thank you all for joining us.