MongoDB, Inc. (NASDAQ:MDB) Q4 2019 Results Conference Call March 13, 2019 5:00 PM ET
Brian Denyeau – IR, ICR
Dev Ittycheria – President and CEO
Michael Gordon – COO and CFO
Conference Call Participants
Keith Weiss – Morgan Stanley
Heather Bellini – Goldman Sachs
Brad Reback – Stifel
Brent Bracelin – KeyBanc Capital Markets
Richard Davis – Canaccord
Hannah Rudoff – DA Davidson
Tyler Radke – Citi
Good day, ladies and gentlemen, and welcome to the MongoDB Fourth Quarter Fiscal 2019 Earnings Call. Today’s conference is being recorded.
At this time, I would like to turn the conference over to Brian Denyeau, ICR, Investor Relations. Please go ahead, sir.
Thank you, Keith. Good afternoon and thank you for joining us today to review MongoDB’s fourth quarter and 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 Chief Operating Officer and Chief Financial Officer.
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 first quarter and full year fiscal 2020, our fiscal 2020 priorities, our market opportunity, database market dynamics, the anticipated benefits of our products for our customers, our ability to expand our leadership position, our growth strategy, the impact of the adoption of ASC 606 on the future financial results and our ability to generate margin expansion.
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 constitute 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 could cause actual results to differ materially from expectations.
For a discussion of 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 30, 2018, our quarterly reports on Form 10-Q filed on September 7th and December 6, 2018 and our other periodic filings with the SEC.
These documents are available on 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 their most directly comparable GAAP financial measure.
And with that, I’d like to turn the call over to Dave.
Thanks, Brian, and thank you to all of you for joining us today to review our fourth quarter and full year results.
The fourth quarter was a tremendous finish to what was a milestone year for MongoDB. Our results reflect broad-based performance in all geographies, across industries and amongst small, midsize, and enterprise customers through our sales-led and self served channels.
I will be discussing our results for the fourth quarter and full-year on an ASC 605 basis only. Later, Michael will review our results under ASC 606.
To quickly summarize our fourth quarter results. We generated revenue of $83.1 million, an 85% year-over-year increase, which was above the high end of our guidance. We grew subscription revenue 87% year-over-year.
Atlas revenue grew more than 400% year-over-year and now represents 34% of revenue. And we ended the quarter with over 13,400 customers, up approximately 130% compared to a year ago.
For the full year, we generated revenue of $253.8 million, a 64% year-over-year increase, which was above the high end of our guidance. We grew subscription revenue 67% year-over-year. And Atlas revenue grew more than 400% year-over-year and represented 24% of annual revenue.
While we constantly seek to get better at what we do, we are quite pleased with our performance last quarter and last year and are well-positioned for fiscal 2020 and beyond. We have established MongoDB as the next generation database platform of choice.
And our goal is to maximize the massive market opportunity in front of us. We believe our wide appeal, the success of our customers and our financial performance continue to clearly highlight that MongoDB’s document database offers the best way to work with data.
Documents correspond directly to objects and mainstream object oriented programming languages, so developers can store and organize data according to the natural relationships among entities in the real world. This enables developers to focus on building applications the way it makes the most sense, not on working around the limitations of their database.
Our document-based architecture addresses a broad range of popular data models, enabling a wide variety of use cases. As a result, MongoDB is experiencing accelerating adoption with developers.
The total number of MongoDB downloads from our website alone is now more than 60 million with more than 20 million occurred in the last 12 months, up from more than 12 million in fiscal 2018. It should be noted that there are between 20 million to 25 million developers in the world today.
Clearly, developers, customers and the broader market are now starting to understand what we at MongoDB have known for a long time that documents, not tables are the future of this market. Because of our enormous popularity, there are other solutions that now try to emulate MongoDB’s capabilities. However, none of these imitation databases are built on a true document architecture.
Because there are fundamental architectural differences between MongoDB and these other imitation databases, customers have to deal with severe feature and performance trade-offs in addition to the deep vendor lock-in with these imitation offerings. Using MongoDB dramatically increases developer productivity, enabling organizations to innovate more easily and deliver more value, more quickly to their own customers.
What was particularly exciting about our results in the fourth quarter and fiscal 2019 was the breadth of customer adoption and the wide variety of use cases employed. The common theme we see across our customer base is that businesses today are incredibly motivated to find new ways to innovate, either to pursue new market opportunities or to respond to new competitive threats and need a platform that lets them do so quickly and efficiently. Increasingly, the answer for customers in nearly every industry and geography is MongoDB.
I’d like to spend a few minutes highlighting just a small sample of the customer wins and interesting use case in the quarter. Last quarter, we added another business unit of IHS Markit’s financial services division. The fixed income pricing business selected MongoDB Atlas to support its migration from legacy services and provide a data platform with rich currying capabilities, multi-region distribution and end-to-end encryption. WirelessCar, the world’s leading innovator of connected vehicle services is migrating core components of their IoT platform, which gives automotive companies real-time visibility into vehicle performance. MongoDB Atlas will help reduce the time it takes to bring new features to market from weeks to days and dramatically cut on-boarding times for new customers.
LINE, one of the biggest messaging platforms in Asia is in process of expanding its offerings to financial services. They chose MongoDB for the scalability of the platform and how easy they can develop and manage their applications.
BBVA, a global banking group, has 37 applications running on MongoDB including a financial aggregator, customer data hub and analytics. With MongoDB, BBVA is able to easily offload applications from their mainframe, develop new capabilities more quickly and leverage valuable data such as data and customer buying behavior in real time.
Ulta Beauty, the largest beauty retailer in the U.S., chose MongoDB Atlas to support a new artificial intelligence application. Transics, a WABCO company, develops fleet management systems for truck, driver, trailer, cargo and subcontractor management. They are using MongoDB as a platform for their IoT data hub.
Breuninger, a German top retailer migrated from monolithic legacy system to MongoDB Atlas in order to support their omnichannel integration plans.
Catapult Sports which creates technology to help athletes and teams reach their true potential is migrating their IoT marketing platform to MongoDB Atlas. Atlas Global Clusters are expected to improve overall application performance and increase customer satisfaction in each region.
Nationwide, the UK financial institution and the world’s largest building society built an open banking mobile app and a data speed layer that has improved data resiliency and increased speed to value for new applications on MongoDB and MongoDB Atlas.
Mizuho International relies on MongoDB as an integral part of its core backbone to help scale large amounts of trade data and provide a secure platform for risk reporting. The flexibility, dynamic schema and extensive currying capabilities allow Mizuho to make greater use of their own data.
As you can see from these examples, the common theme is that customers are increasingly selecting and expanding the use of MongoDB to innovate more easily and bring new capabilities to market more quickly.
Furthermore, many of these customer wins cited above, demonstrate the tremendous market demand for MongoDB Atlas. We achieved a significant milestone this quarter as MongoDB Atlas is now at an annualized revenue run rate in excess of $100 million and growing rapidly. The growth demonstrates the wide popularity of MongoDB and the strong private market fit of Atlas.
Before we move on to our 2020 priorities, I wanted to provide an update on the licensing change we announced last October with respect to MongoDB Community Server, the free to download version of our database.
It is very important for investors to understand that since we own all our IP, unlike other open source companies, we have full control over how we license our software. As big believers in open source, we introduced the Server Side Public License or SSPL to address the risk facing companies wanting to make significant investments in open source in the modern Cloudera.
In the months since we launched SSPL, it has become clear that many others in the open source community share our concern. However, there’s not currently a consensus around how to address the issue of open source strip mining. In lack of this consensus, we recently decided to withdraw the SSPL from the OSI license approval process.
We have decided to focus our efforts on working with other stakeholders in the open source and broader tech community to either refine the SSPL or develop an alternative license that addresses these issues. To be very clear, current and future versions of MongoDB Community Server including patch releases to prior versions will continue to be offered under SSPL, until there’s a broadly accepted alternative license that is designed for the Cloudera.
Our performance in fiscal 2019 has given us even more confidence about our ability to capitalize on the large market opportunity in front of us. As a result, in fiscal 2020, we plan to focus on extending our product leadership as a modern general purpose database, expanding our different go-to-market channels, including adding sales capacity in our field inside sales channels, along with growing our self-serve business and increasing the number of partners and deepening our relationships with our existing partners to further increase our reach and improve our sales efficiency.
In fact, in the fourth quarter, we deepened our partnership with IBM by expanding our technology and go-to-market agreement on the heels of a number of customer wins, including a large hospitality brand, a notable bank, a large government agency, and a recognizable healthcare company. Clients are responding to the combination of IBM’s product suite and MongoDB as a modern multi-cloud data architecture.
We are fortunate to have a highly scalable business model. So, even as we invest more in the business, we expect to continue to generate operating margin expansion in 2020. To build a world class software business a company needs a large market, strong product market fit and a highly effective distribution channel. While the first two elements are evident for MongoDB, we’re also very proud to have built a formidable go-to-market organization that has yielded strong results.
To lead our sales organization for the next stage of growth, we were pleased to recently announce the promotion of Cedric Pech to the role of Chief Revenue Officer. Cedric Pech led our EMEA sales team which has delivered compelling results over the past few years. Prior to join MongoDB, he was the CRO at Fuze, a cloud communications and collaboration company. Earlier in his career, Cedric worked with me at both BladeLogic and BMC. He is one of the best sales executives I know. And I believe he will do a terrific job scaling our sales team to drive sustained growth.
To summarize, the fourth quarter was a great finish to a traffic year. We enter fiscal 2020 in our strongest position yet. We are at the early stages of a once in a generation shift in the database market. We are confident that if we continue to execute at a high level, MongoDB will be one of the clear winners.
With that, let me now turn the call over to Michael.
Thanks, Dave. As mentioned, we are very-pleased with our fourth quarter performance, which reflects strong, continued growth at significant scale. I’ll begin with a detailed review of our fourth quarter and full year results and then finish with our outlook for the first quarter and full year fiscal 2020. Before I jump into the numbers, I would like to take a minute to explain the impact of the adoption of ASC 606 that will have on our financial results.
We’ve implemented ASC 606 on a full retrospective basis, which means we have recast our prior results for fiscal 2019 and prior periods under the new revenue recognition standard. There are two primary ways ASC 606 impacts our financial results. First, revenue recognition. Enterprise Advanced transactions will now have a portion of the contract value recognized upfront while the remainder will be recognize ratably over the contract term.
As a reminder, most contracts are annual. However, for an illustrative three-year contract under 606, we will now recognize the term license component for all three years upfront. This will result in greater variability and reduced comparability in our quarterly revenue results. It’s important to note that the adoption of 606 will not impact how Atlas revenue is recognized.
Second, sales commission capitalization. 606 broadens the scope of capitalized commissions. Now, under 606, all incremental costs, including commissions and payroll taxes, as a result of closing a deal, are capitalized. Previously, only direct, deal-specific commissions were capitalized under 605. Additionally, the estimated amortization period is generally longer under 606 as compared to 605. This has the impact of modestly lowering our reported sales and marketing expense.
For fiscal 2019, the adoption of ASC 606 resulted in a $13.2 million increase in revenue or approximately 5%, a $6.6 million reduction in sales and marketing expense, and a $19.9 million increase in both non-GAAP operating and net income loss.
There are additional dynamics that investors should keep in mind under 606. First, when we sign multiyear Enterprise Advanced deals, we will need to recognize the term license portion of the future year license revenue upon initial delivery, regardless of whether they prepaid the entirety of that contract.
Second, as a result, our year-over-year growth in any given period may be more variable when the year ago compare had a greater amount of upfront revenue due to the timing of multiyear deal signings. To be clear, this would not be indicative of slowing business momentum on a function of revenue recognition accounting dynamics. One example of this will occur in Q3 of fiscal 20, which faces a very difficult compare under 606 as we signed several, very large multiyear deals in Q3 of fiscal 2019.
Third, revenue will more closely follow the pattern of historic booking trends. Q3 has historically been our largest quarter for new bookings and consequently subsequent renewals with Q1 historically the lowest. As a result of this, sometimes Q1 revenue under 606 will decrease than the prior Q4. This happened in the Q1 of fiscal 2018.
I’ll turn to our fourth quarter results which I’ll first review on an ASC 606 basis. Total revenue in the quarter was $85.5 million, up 71% year-over-year. Subscription revenue was $80.6 million, up 73% year-over-year and professional services revenue was $4.9 million, up 37% year-over-year. This was the first quarter results that included the acquisition of mLab.
We’re pleased that mLab performed modestly better than our expectations for the quarter. This is on top of very strong organic results which drove the large majority of the outperformance relative to guidance and reflected accelerated organic revenue growth rates. Our revenue performance was strong across the board and also benefits from stronger than expected Atlas consumption including a number of customers who consumed well in excess of their contractual run rates.
The strong growth in the quarter was driven by a healthy mix of new logos and upsell activity by Enterprise Advanced customers as well as the rapid adoption of Atlas. Atlas represented 32% of revenue during the quarter, up from 10% in the fourth quarter last year and up from 21% last quarter.
During the fourth quarter, we grew our customer base by over 5,000 customers, bringing our total customer count to over 13,400 customers, which is up from over 5,700 in the year-ago period and over 8,300 at the end of last quarter. This reflects the broad appeal of MongoDB and diversified customer base across industries and geographies.
Of our total customer account, over 1,750 are direct sales customers, which compares to over 1,700 at the end of the prior quarter and over 1,450 in the year ago period. The growth in our total customer account is being driven in large part by Atlas, which had over 11,400 customers at the end of the quarter compared to over 6,200 at the end of the third quarter. This includes approximately 4,200 customers acquired from mLab.
The growth in total customers includes growth in our Enterprises Advanced customers as well as new Atlas customers. It is important to keep in mind that the growth in our Atlas customer account reflects, both new customers to MongoDB, as well as existing EA customers adding incremental Atlas workloads.
We continue to see healthy expansion from existing customers. Our net AR expansion rate in the fourth quarter remained above 120% for the 16th consecutive quarter. We ended the quarter with 557 customers with at least $100,000 in ARR and annualized MRR which is up from 490 in the third quarter and 354 in a year ago period.
We also saw significant increase in customers spending more than $1 million annually, which increased from 22 last year to 39 this year. Driving expanded adoption and spend among existing customers is a key component of our growth strategy and has been a consistent area of success.
Moving down the P&L, I will be discussing our ASC 606 results on a non-GAAP basis unless otherwise noted. Gross profit in the fourth quarter was $61 million, representing a gross margin of 71% compared to 76% in a year ago period.
As expected, gross margin in the quarter was negatively impacted by mLab, which has a lower gross margin than Atlas. This impact will dissipate by the end of fiscal 2020 as we migrate mLab customers to Atlas. Overall, we’re very pleased with the continued gross margin improvement of organic Atlas during the fourth quarter. However, we continue to expect that we will see some modest reduction in overall gross margin as Atlas continues to be a bigger portion of our revenue.
Our operating loss was $9.7 million or negative 11% operating margin for the fourth quarter, compared to a negative 29% margin in the year-ago period. The more than 1,800 basis points improvement in our operating margin reflects the significant operating leverage we drove in the business this year while investing in our continued growth.
Net loss in the fourth quarter was over $9.1 million or $0.17 per share, based on 53.8 million weighted average shares outstanding. I will now quickly review our results on a 605 basis. Please note that we will no longer be reporting our financial results under 605 beginning the first quarter of fiscal 2020.
Total revenue in the quarter was $83.1 million, up 85% year-over-year; subscription revenue was $78.3 million, up 87% year-over-year; and professional services revenue was $4.9 million, up 54% year-over-year. Again, we were pleased with the modest in mLab but the organic results powered the quarter, resulting in an acceleration of our organic growth to the highest year-over-year rates in our publicly reported results.
Gross profit in the fourth quarter was $58.6 million, representing a gross margin of 71% compared to 73% in the year ago period. Operating loss was $14.6 million or negative 18% operating margin for the fourth quarter compared to a negative 46% margin in the year ago period. Net loss in the fourth quarter was $14 million or $0.26 per share, based on 53.8 million weighted average shares outstanding.
Turning to the GAAP balance sheet and cash flow. We ended the quarter with $466.5 million in cash, cash equivalents and short-term investments, and restricted cash. Operating cash flow in the fourth quarter was negative $9.5 million. After taking in account approximately $3.1 million in capital expenditures, free cash flow was negative $12.6 million in the quarter.
Short-term deferred revenue on a 606 basis was $122.3 million, up 45% year-over-year, while total deferred revenue of $137.7 million was up 36% year-over-year. Please note that the adoption of 606 had a material impact to our deferred revenue balance. This is a result of some Enterprise Advanced revenue that was previously deferred under 605 that is now recognized upfront at the time of the subscription start date.
We have provided recast balance sheet by quarter for fiscal 2019, which reflects changes to deferred revenue as well as modest changes to other assets and deferred commissions. We’ve also provided deferred revenue balances for the past eight quarters on a 606 basis. Also keep in mind that Atlas is a usage-based model and generates less deferred revenue than Enterprise Advanced.
As a reminder, Atlas is often billed monthly in arrears versus the annual advanced billing terms we see with our Enterprise Advanced customers. Lastly, quarter-to-quarter comparisons of deferred revenue can also have some level of variability due to timing.
I would now like to turn to our outlook for the first quarter and full year of fiscal 2020, which as a reminder is being provided on a 606 basis. For the first quarter, we expect revenue to be in the range of $82 million to $84 million.
We expect non-GAAP loss from operations to be negative $14 million to negative $13 million, and non-GAAP net loss per share to be in the range of negative $0.25 to negative $0.23, based on 54.5 million weighted average shares outstanding. For the full fiscal year 2020, we expect revenue to be in the range of $363 million to $371 million.
This includes an updated revenue forecast from customers acquired from mLab of $20 million for fiscal 20, up from $18 million we indicated at the time of acquisition.
As mentioned earlier, year-over-year growth comparisons and quarter-to-quarter results will likely be more variable under 606 due in part to the timing of multiyear contract signings in prior periods. As you will notice when you update your models for 606 results, we are facing notably larger compares in the second half of fiscal 2020, particularly in the third quarter.
We expect non-GAAP loss from operations to be negative $59 million to negative $55 million, non-GAAP net loss per share to be in the range of negative $1.06 to negative $0.98 per share, based on 55.2 million weighted average shares outstanding.
As Dev mentioned, we are investing additional resources into our product development and go-to-market efforts in 2020. Given the size of our market opportunity, the strength of our product market fit and the attractiveness of our unit economics, we believe these investments will generate strong returns for the Company. We expect to again generate operating leverage in fiscal 2020, even as we make these investments, which underscores the inherent scalability of our business model.
In closing, MongoDB finished fiscal 2019 with its strongest quarterly performance in years. We are executing at a high level and generating best-in-class growth. The database market is in the early stages of a transformational shift and MongoDB is well-positioned to be one of the primary beneficiaries of it.
With that, we’d like to open up to questions. Operator?
Thank you. [Operator Instructions] We’ll take our first question Raimo Lenschow with Barclays.
Hey, guys. This is [indiscernible] for Raimo Lenschow. Congrats on a incredible quarter here. My first question, can you talk about the product evolution for Atlas in terms of enterprise features, what you’ve achieved so far, and where do you see Atlas evolving to in fiscal 2020?
Yes. So, thank you for the question. So, obviously, we’re really pleased with the growth of Atlas. I think, what it really speaks to is the popularity of MongoDB and the strong product market of Atlas, because customers really want to focus on differentiated work, being able to focus on innovate and building applications and not have to deal with a burden of operational and database management.
In terms of the enterprise features, we’ve added a number of security features. And I think we’ve signaled since the IPO that we were in the process of moving a bunch of features in Enterprise Advanced to Atlas, and we’ve done that including lot of security features, things like auditing, access control, authorization, et cetera, including things like monitoring and auto scaling, and so forth. So, all those features now are embedded in Atlas. And there’s a variety of different service offerings, depending on the SLAs and the features that customers want.
Okay. And as my follow-up, a little bit more of a boring question, but on 606, what percentage of the total contract do you – are you recognizing upfront for the enterprise contracts? And does your guidance assume a similar percentage of multiyear contracts for FY20 versus FY19?
Sure. So, there’s certainly been some variability. We have not assumed any major changes in terms of the mix. So, certainly to the extent that that mix varies, that will impact the results. It varies in terms of the question of how much of the upfront license, obviously it effects on the duration of the contract as well as on the product mix but in general it’s roughly in the area of [technical difficult] is the current estimate, although obviously as things continue to move to change, we will update that accordingly. And as you can see from a macro perspective, if you look at the full year, it has effect about 5% on overall revenue.
We will take our next question from Sanjit Singh with Morgan Stanley.
This is actually Keith Weiss sitting in for Sanjit. Two questions, one, kind of looking backwards on Q4. That was a pretty amazing quarter, really strong acceleration. Anything in particular kind of turn on for you guys, any kind of catalyst to that acceleration in the performance that you could point out to us what happened in Q4? And then, the second part of the question, looking forward in FY20 with Pech now sort of taking that Chief Revenue Officer and heading into new fiscal year, any significant changes you guys are making in sales structure or go-to-market strategy with sort of the new sales leadership into the new fiscal year?
Thanks, Keith. Glad to have the big dog on the call. I just wanted to respond to the two questions. So, I would say, our performance is really a function of the flywheel effect. I think we’ve seen a number of advancements on the product. And so that’s given customers a lot of confidence, especially around asset transactions and the fact that we are now – it’s clearly understood that we are truly a general-purpose database and wide variety of use cases that customers employ us for is clear evidence of that.
I think, the fact that we have notable marquee references across a wide variety of industries gives customers even more confidence. And I would say, the efficacy of our go-to-market channel has just gone better and better over time. Clearly, there is a little bit of seasonality in our business. And so, the fourth quarter tends to be a big quarter in general. But, we were quite pleased with the performance that we saw. And I still believe that there is lots of things that we can get better at over time.
And in terms of Cedric’s appointment, I was quite thoughtful about looking at a successor for our last CRO. And I did talk to a number of people outside the organization. But as I looked at how quickly our business was changing and the complexity of our business, it made much more sense to promote someone from within. Cedric is also someone I’ve known for a long time. He did a fantastic job in really driving the European business.
And since his appointment, he has really won over the rest of the sales force. I would say that there is going to be no major changes to sales force. We have a really strong bench in North America and Asia and the rest of the world. I think, what Cedric is really going to focus on is just taking our sales process and our ability to scale the sales organization to the next level to drive sustained growth. You’re not going to see any wild changes in terms of how we go to market.
Yes, more just about scaling the current organization?
We will take our next question from Heather Bellini with Goldman Sachs.
I was just wondering if you could share with us – there has been a lot of debate in the market about mLab and customers potentially leaving. And I just was wondering if you could help set the record straight and just kind of walk us through whether or not you do expect some customer migration. I mean, there has been different versions of what’s going on in the market. I was just wondering since we’re on this call, maybe you could just kind of level the playing field for everybody and just kind of tell us what you’re expecting from that acquisition, and if you did have one or two customers leave, what would be the driving force in that and kind of any other feedback you’ve heard from their installed base? Thank you so much.
Thanks Heather. The reason we acquired mLab was really, they were the pioneers in the MongoDB as a service offering and they did that way ahead of us. And the other thing that they did a really good job of was build their entire business on a self-serve basis. They didn’t have one salesperson. So, those two things were really big reasons why we acquired that business and the talent that we’ve acquired from Will Shulman on down, has been very impressive and really pleased to have the team as part of MongoDB.
When we did our diligence, there was clearly some understanding that there were some customers who may be moving in different directions, currently some of those customers were working on really old releases of MongoDB that had not upgraded to more recent versions of MongoDB. And so, we factored in some of that attrition into our guidance and estimates. And so, we don’t see any material impact to any of the potential changes that you may have heard. And we are now starting to build relationships with many of these customers.
Obviously some of them are very small customers, some of them are larger customers, and it’s going to take some time for us to get them to understand the benefits of upgrading to the latest releases of MongoDB, and we shall see about how those relationships evolve. But, we have taken a very conservative posture and there’s no impact on our guidance.
The only thing I would add, just so that people understand is, we just shared the customer count for mLab, which is approximately 4,200 customers. And when you look at the revenue that that’s driving, the math for that works out to be around, $5,000 a year. So, these are typically not large customers. Yes, there are a couple of outlier customers that are larger and have brand names, but the vast, vast majority of the customer base is of a much smaller level. And clearly, we’ve been pleased, there was a modest beat in Q4. We upped the fiscal 20 guidance just on this call from the $18 million to the $20 million. So, I think it’s going sort of well and better than expected. And so, that’s all I think very healthy.
Okay, great. And then, just one quick follow-up would be, is there any way you could share with us your lands kind of the pace of your lands and how those initial lands might be increasing, especially with some of the new enhancements to the product over the last year?
Yes. I would say, our lands are definitely increasing. I think, it’s for a number of factors. One, I would say is we clearly made some pretty significant product enhancements over the last few years. It has given customers more confidence to use us for mission critical workloads. I would say, two – I think I’ve mentioned this on prior calls. We’ve become – clearly view it as a very strategic partner to many customers. So, the level at which we engage with, in these organizations, tend to be at a quite a higher level. And so, that allows us to go after bigger deals.
And then, I would just say in, general, the efficacy of our go-to-market process where we try and you do a lot of discovery early on in engagement with the customer, but then use that information to go find [ph] organization to present the potential benefits we could offer and the clear understanding of the pain that they’re going through, whether it’s trying to consider building a new application or the struggling with the performance or the brittleness of the existing legacy application.
All those things are impacting our ability to get bigger land. So, that is definitely happening. But, this is still a land and expand business because this is not a win or take all market, we still have a very small percentage of wallet share of some of the largest customers that we have, and we still have to go and earn more business from them. But, we feel very, very confident of our ability to do so, given our track record to-date.
We will take our next question from Brad Reback with Stifel.
Dev, with respect to the DocumentDB announcement, have you seen that have any impact on your ability to build top of funnel pipeline.
We see no impact, Brad. In fact, I think it’s frankly raised MongoDB’s awareness. I have to remind people that 98% of the market today is built on relational databases that technology that’s over 40 years old. So, when you have people now trying to emulate MongoDB, what are really signals is one that we’ve become incredibly popular and the reason we’ve become incredibly popular is that the document approach is now being viewed as the best way to work with data.
And so, now, our customers starting say, well, instead of using relational databases, I want to use document databases and they want to do a bake off. We feel very confident about our ability to go head-to-head with any other alternative out there. And so, we think that actually this has been great for awareness and great for customer education and we see no impact on a negative basis whatsoever.
And just one quick follow-up, and I know it was sort of asked in aggregate. But the Atlas business accelerated 100 basis points sequentially, the 400% growth from 300% last quarter. Is that a function of some year-end true ups with customer contract or just a function of that level of acceleration in the install base? Thanks.
So, Atlas benefited from a number of dynamics and we’re very, very pleased with the quarter. Obviously, we had the addition of mLab for the first time in the quarter. But even if you skip that out, it was a very strong and accelerating quarter from an overall Atlas performance. It’s strong addition of new customers, it’s consumption of existing customers.
The other thing that we did try and call out in the prepared remarks, though was that we did benefit from a number of customers in Q4 who were consuming Atlas at rates in excess of their contracted amounts. And so, we always keep an eye to that in terms of like what is a relative run rate and how does that compare relative to the contracted rate.
And so, we don’t have enough history with Atlas, yet to know as to how much of that is sort of pulling forward or actually establishing a new run rate level. And so, we just – we want to keep an eye on that and want to make sure that sort of expectations don’t go out of control as you all extrapolate things because I do think that’s a dynamic, that’s a play but it was really very, very strong across the board.
[Operator Instructions] We will take our next question from Brent Bracelin with KeyBanc Capital Markets.
Thank you. And one for Dev and a follow-up for Michael. Dave, I wanted to drill down on Atlas. It’s kind of hard not to discuss just given the momentum of the business here. Few businesses we see at $100 million run rate growing this fast. And even if I back out mLabs, it looks like growth accelerated again. You talk a little bit about consumption, but I was wondering if you could just drill down a little bit more relative to why this business is accelerating now and at this pace? Is there something that happened in the quarter, are you seeing higher catch rates of the add-on security services. Any sort of additional color on Atlas, and I know you talked a little about the customer spend over $1 million are going into 39. Are there any Atlas customers now spending a million plus on that category? So any color on what drove the momentum in Atlas would be helpful.
Yes. Thanks for the question. I would say the fundamentals are the following; one, obviously MongoDB has become incredibly popular and two the product market fit of Atlas has been incredibly strong. I mean, we have seen high growth rate since we launched the product about two and a half years ago. So it just exceeded our expectations.
I would say what has also now kicked in is two things, one our sales organization, it took some time for sales organization to know how to sell a cloud service. And what we are seeing by the results is that the sales organizations acumen around doing that has become better and better.
And the other thing is the introduction of the enterprise features, the enterprise features have allowed two things to happen; one allowed us to get bigger deals and also has given comfort to
To a certain type of customer who is very, very concerned about, say things like security and data security in the cloud.
In fact, we had a very large notable financial services institution who basically contracted a quite a large deal with Atlas and they tend to be pretty conservative, they are moving very slowly into the cloud. And this was a consumer facing application to have a very, very sensitive consumer data.
And they spent an enormous amount of doing a lot of assessments and of our technical architecture. And they got convinced about the strength of the product and the best-in-class security features and that resulted in a large transaction.
So that is just one anecdote. But there is lots of anecdotes like that where large, sophisticated customers who now want to move workloads to cloud are moving towards Atlas. And the other big benefits for customers is that there is no lock into any particular cloud provider.
So while they may choose one cloud provider today, they recognize that those relationships may evolve overtime and they like the flexibility of being able to move from one cloud to another cloud.
And frankly, moving that application back in-house where I will have to rewrite one line of code. So that gives customers enormous amount of comfort and optionality in terms of what they can do in the future. So all those factors are driving I think the acceleration of MongoDB Atlas.
Very helpful color there, encouraging to hear some larger opportunities pop into Atlas as well too. I guess for Michael is a follow-up gross margins kind of look like it did downtick, kind of this is the first quarter with mLabs, is that the big contributor there and how should we think about kind of the gross margin here in the low 70s, is this kind of a sustainable rate or do we still have a little bit of a mix shift we need to think about relative to that gross margin profile going into fiscal 2020.
Yep. So thanks Brent. Yes, there will definitely continue to still be mix shift. The higher percentage that is driven by Atlas is acting as a short-term drag on the overall gross margin. mLab though, to your point is meaningfully lower gross margins than Atlas and so that is a particular kind of incremental drag that you know by the end of the year should dissipate.
But I would not say that this is not the bottom, we will continue to see as at Atlas, assuming it continues to grow faster, we will see some short-term gross margin compression, but we continue to see increases in organic Atlas, Atlas ex mlab, gross margins, and we have been very pleased with the performance there and we will continue to work towards driving those higher over the next several quarters.
Thanks. That is all I had.
We will take our next question from Richard Davis with Canaccord.
Thanks very much. So I think you guys recently partnered with Datadog, I think it was on Atlas but could you talk briefly about that relationship and just more broadly. Could you provide some like color as to what are obvious places where future technology partnerships make sense, because obviously you don’t need to build every single items out there so. Thanks very much.
Yes. So thanks, Richard, just in full disclosure, I’m actually on the boards of the Datadog and I have been there for quite some time, but frankly this announcement we just made was really function of organic interest by our customers obviously Datadog has done incredibly well, as a private company and their monitoring tool has become very popular.
And so be able to get visibility into MongoDB database statistics, because the databases is probably the most important layer of the application that is critically important for customers and so providing a integration made a lot of sense for customers.
And so in terms of other partnerships or potential integration is integration to other complementary management tools that may help customers, for example, we integrate with Kubernetes that has become the container of choice for lots of customers to orchestrate and virtualize their application environments.
We have built that integrations to customers have a Kubernetes operator to basically invoke MongoDB and all the functionality with the MongoDB. So there is a bunch of other types of integration that we have done.
And so we feel basically work backwards from what a customer is looking for, how can we help customers better manage their infrastructure or how can we do better on their behalf and make it easy for them to building applications and that drives our integration priorities.
Thank you very much.
We will take our next question from [indiscernible] with Oppenheimer.
Thanks Ittycheria. Congrats, great quarter guys. A couple of questions for me first on the services revenue and other one on [indiscernible] such a great quarter, but growing only a miserable 37%. Help me understand the disconnect between the add and subscription is it just because Atlas is a little bit more self-service than [indiscernible] business, how do I think about the correlation of that going forward to subscription revenue.
I think the most simple explanation is the subscription revenue is recurring revenue whereas the services revenue is typically one-time. And so you really sort of starting all over again and so when you think about the amount of services that you are delivering in the aggregate it’s actually a pretty healthy growth rate given the fact that your usually starting over.
That is probably the biggest factor. Qualitatively we do also see a little bit lower services attach rate on Atlas, but the principal driver really is around how much of this is recurring revenue versus one-time revenue.
Very good and as a follow-up Dev, just want to make sure I understand your IT comment about SSPL, the growth from the OSI approval process. Can you explain – during the implications for this outside of just the headline that you I guess you cannot call yourself right now open source officially what the implication of this?
I would say the implication is the following. We own all our IP, so this is important, like any other software who own IP, we can control how we license our software, we also big believers in open source and so it’s clear that the concerns we raised and we try to codify this concerns in our new license called SSPL there has been a lot of receptivity to that, but it’s clear that the industry needs more time to coalesce around what the right answer is long-term.
So rather than trying to force people to use SSPL as the answer we said let’s rather be a good partner to the rest of the community, we want to work with the community and come up with an answer that makes sense for everyone and so long story short, our software is still licensed under SSPL not only current and future versions, but also any patch releases to prior versions will be licensed under SSPL, so that is an important point.
And we believe we are still open source, whatever name you may want to apply to it, source available free to use, you know we still conform to the forest offer freedoms that the open source principles points out the freedom to run for any purpose, the freedom to study, exchange and have access to the source code, the freedom to redistribute copies and the freedom to distribute copies of modified versions and all those freedoms still apply. So from that point of view, we are still an open source company.
Very good. Alright, congrats. Good luck.
We will take our next question from Rishi Jaluria from DA Davidson.
Hi, guys. This is Hannah on for Rishi. Thanks for taking my questions. First question. I was just wondering on functionality, if you have gotten any feedback from customers, or if on your end, there is any sort of functionalities still like to build out on the core enterprise advanced product?
Oh, yes. So I mean, obviously, we have a very strong and robust roadmap. We are investing a lot in R&D. And so for example, you know, we are introducing asset transactions for – asset for shorted clusters so that adds another level of asset capability.
We have field level encryption coming out. We have something called [retravel rights] (Ph) it adds more resiliency to your application, so you don’t have to worry about if right tales, you don’t have to worry about building logic to deal with that that is going to be built at the database.
So the whole bunch of features that are coming out in our two release later this summer, and we are very excited about that released. Obviously, we continue to innovate on the Atlas front. We also have products like stitch that enable developers to more quickly build applications.
So you are seeing us continue to expand the aperture of what we do to help customers use MongoDB for more and more use cases. And I won’t comment on this now, but I think you will hear some really interesting announcements of something that we are going to be expanding into that we are really, really excited by. And I will save that for another time.
Okay, that is really helpful. Thanks. And then second question, I was just wondering if you could expand a little on your deepened partnership with IBM. And if the go to market strategy changed at all, and how the partnership differs from what it was in previous quarters?
Sure. So one of the reasons we struck an agreement in IBM is, while we are growing really quickly, and we are building out of Salesforce relative to the market, you know, opportunity in front of us, we still have a fairly small sales organization.
So one of the things that we are trying to solve for is reach, because we see this once in a generation shift happening in the database market and the things that we worry about are deals that are happening that we are not even privy to.
And so the thing that IBM does for us is really expand our reach especially in markets that we don’t have presence in or accountant that we don’t have presence in. And the other way they help us is that because of the deep history and knowledge of key IBM accounts. They can also accelerate deals and make deals bigger and more quickly than say we could do on our own.
So both those factors has really allowed us to have a really a win-win relationship. As I noted in my remarks, we have closed a number of deals, momentum is very strong. So we further deepened our relationship and we feel very excited about what that relation can deliver for us in fiscal 2020 and beyond.
We will take Tyler Radke with Citi. Please go ahead.
Thanks, good evening. I was wondering if you could talk about the impact of the licensing changes, have you seen that obviously the companies that were using your software and reselling it like scale grid, compose, object rocket. Have you seen a positive impact from those customers actually moving over to Mongo or any other companies you are aware of where customers have transitioned because of the licensing change.
So I would say that we have some fruitful conversations and expanded some relationship with certain cloud providers who did not have a commercial relationship with us and we are engaged with some of the others and hope to do so in the next few quarters.
I would say that in general, the receptivity of SSPL has been very positive and I would also say that if you are a customer of MongoDB SSPL doesn’t really matter, because you end up having commercial relationship with us.
So this is really for the people who are using our free to use download version of our software and so as you will see from results, we feel really good about the business today and how its positioned for the future.
Great and then a follow-up. Just if you look at next year ahead, how big do you think Atlas could ultimately be as a percent of revenue, and sorry if I missed it, but are you making any changes just from a sales incentive plan around Atlas, I know you are comping on the same on dollars previously, but given that Atlas is typically 2X the ASP of an enterprise advance. Just curious if you are making any changes there.
Again I want to remind people that one of our philosophy is to help customers run their workflows anywhere. So you literally could MongoDB on your laptop if you are developing application, you could run it on premise and use enterprise advanced and you can run in the cloud using Atlas.
And so we are very committed to enabling customers to run their work load’s wherever they want and obviously you can choose your cloud provider depending on where you want to run your workload in the cloud.
And so that will not change and we have not given incremental incentives for our salespeople to sell Atlas over enterprise advanced. I think what we are seeing is that obviously the megatrends is people are moving more and more workloads to the cloud and clearly our customers are following that trend.
And they like the fact that MongoDB Atlas is the most widely available global cloud database in the world. Its available in over 60 regions as a virtue of being able to run on AWS, Azure and GCP and so the fact that customers not only have a choice of cloud providers, but can really choose to run their workloads almost anywhere in the world.
That makes along with the power and the benefits of MongoDB’s document model and the query language. And so given all those benefit there is a reason why Atlas has become so popular.
And ladies and gentleman this will conclude today’s question-and-answer session. At this time I will turn the conference back to Dev Ittycheria for any additional or closing remarks.
I want to thank everyone for joining us on our fourth quarter call. We really appreciate all the support and we thank you and we look forward to speaking to you again. Take care. Bye-bye.
Ladies and gentlemen this does conclude today’s conference. We appreciate your participation.