MongoDB, Inc. (MDB) Earnings Call Transcript & Summary
January 16, 2025
Earnings Call Speaker Segments
Michael Cikos
analystGreat. Thank you to everyone for joining us as part of the Needham Growth Conference. My name is Mike Cikos, I'm the lead analyst here covering MongoDB. Pleased to say that we have with us the management team for the -- which should be a 40-minute fire side. I have some prepared questions on my side that I'll try to get through, but obviously, you guys have a ton more questions, which are way smarter than mine. So please feel free to log those in, and we'll get them to Michael and Serge while we have them. The boiler plate stuff out of the way, Michael and Serge, thank you very much for participating in the conference today. We really do appreciate it.
Michael Gordon
executiveThanks for having us. It's great to be here as always.
Michael Cikos
analystThe easiest question you'll get out the back. Super high level, what does MongoDB do?
Michael Gordon
executiveSure. Do you want to go, Serge, or you want me to go?
Serge Tanjga
executiveIt's your last rodeo, you go.
Michael Gordon
executiveSo for those who don't know, we're the leading modern general-purpose database platform. So if you think about the database market, it's a very well-established large market, you have $90-plus billion annually being spent. So sort of real actual TAM, not like someday, one day, maybe it will be there. And that's a market that's existed for years. And it was really based off of technology today called relational technology that was important and necessary and critical at the time in the 1970s when it was pioneered, but things have evolved, and so there's a need for a modern alternative. And that's really what we at MongoDB provide. And if you think about the database market, not only is it large, but it's also growing pretty significantly, kind of low double-digit growth. And normally, you think isn't this market has been around for decades, shouldn't a market like that grow more like GDP. Why is the market growing so quickly given that it's so big? And the reality is -- the reason for that is because databases are at the heart of all applications, right? Each application has a database at its core. And you hear phrases like software is eating the world or every company trying to become a software company. And those all point to the fact that the way that companies derive competitive advantage today is principally as a result of their proprietary applications, the technology that they build, right? If it's off-the-shelf technology, like a standard SaaS application, it's available to everyone, that doesn't really provide a lot of benefit. So the way they drive their benefit and drive competitive advantage is by virtue of building software. And that database at the core of that application determines how scalable, how agile, how nimble, how quickly can they innovate, all those things. And so that's part of the reason why the market is so strategic, and we see such significant growth in the market. Lastly, maybe I'll just talk about sort of why was there a need for a new alternative, right? Now, we've had relational alternatives around for decades. Why do companies, why do developers need a modern alternative. And the reason is because the way that relational databases were so successful initially was they were solving for the constraint of the day which was storage, right? In the 1970s, storage was exceptionally expensive. And so if you could store things efficiently, that was very helpful. Unfortunately, that's the way that you store things is you break them out, right? I won't even use any database speak, but I'll just sort of try and give a generalist kind of a view. If you owned a parking garage and you wanted to store as many cars as possible. When the car drove in, you would disassemble the car and you'd put all the steering wheels with the steering wheels and all the fenders with the fenders and you break apart the car and all that and you get way more cars into your parking garage. The challenge is the parking lot attendant when you gave them your ticket, had to reassemble your car and remember, where did I put the steering wheel for this car, and then they look at the sheet and they'd say, "Oh, it was basically in sell BC 478 and have to go look and retrieve that. And that's basically the challenge that a developer has when working with the relational database. So all the data is stored very efficiently, but it's not natural and intuitive to a developer in terms of how to use it because developers use object-oriented programming languages. And so they have to map all this complex data. Whereas today, storage is cheap. And so we, MongoDB, to continue with the parking analogy, just park your car as one whole car. We store it as a document, and then the developer can think of that document as an object. And so it works naturally and seamlessly. And so one of the reasons why we've had success breaking out because we certainly weren't the only one who saw this opportunity. There are many companies that drew a lot of funding and everything else to go and kind of tackle this market. But the reason why we have excelled and kind of broken out is we had a better product that captured kind of the hearts and minds of developers. So there's been developer preference for MongoDB. And then we've married that with solid execution, and that's sort of what's brought us here today to just under $2 billion in revenue. It was still a big, large opportunity and single-digit market share where we are. So why don't I stop there? I can go on and on, but hopefully, that's a helpful framing of it, Mike.
Michael Cikos
analystNo, no. Thanks for that, Michael. And then again, just in the interest of kind of dusting off numbers for folks, given how long ago the quarterly print felt like at this point, but what were some of the key highlights from the October quarter earnings? Just again, a quick recap.
Michael Gordon
executiveYes, sure. Yes, yes. No. No, we're obviously at the end of the cycle, but still that's the most recent quarter as we head into the quiet period and everything else here. So revenue for us was up 22% year-over-year, above the high end of our guidance. Atlas, which is our database services and offering, grew at 26% on a year-over-year basis. It's a little over 2/3 of the revenue at 68% of revenue. Non-Atlas, which is mostly comprised of Enterprise Advanced and some other things, was up 14% on a year-over-year basis. That benefited from more than $15 million of multiyear license versus a year ago. It was a strong income quarter. So non-GAAP operating income was just over 19% and sort of had healthy free cash flow. So we were -- felt like we had a strong quarter ahead of our expectations. The new business environment continued to be healthy for us and executed well, both for Atlas and EA. The non-Atlas business, as I mentioned, significantly exceeded our expectations. Atlas consumption was sort of slightly ahead of our expectations in what we would call sort of a stable environment. We saw a modest seasonal rebound versus Q2 and consumption growth is slower on a year-over-year basis, the same as it was for the first half of the year. So I think those are probably the key highlights right?
Michael Cikos
analystAnd I know we're in the new year as far as calendar. I know everyone is doing their work. There seems to be a growing sense of optimism. It seems like IT budgets might be up slightly versus where they were last year. But interested to the extent you can provide some color, how are -- what is the tone of customer conversations today? Where are they centered? Does there seem to be an uptick in any capacity? Or is it -- again, macro has not significantly changed, but just curious what you're hearing out there?
Michael Gordon
executiveYes. So generally, I would describe the conversations as constructive. We continue to see good kind of customer -- our value prop resonating well with customers. I would say I think that we're not necessarily perfectly indicative of some sort of like macro IT budget, right? Like back to my earlier comments, we're still a pretty small share. And so to the extent that there are like tweaks up or down in IT budgets, we're still a net share gainer and have so much opportunity that we can have success, and that's not necessarily an indication that budgets are growing because we're just -- we're such a small player even at almost $2 billion relative to the opportunity set. But certainly, people are judicious with their dollars. People are thinking about how to get the most bang for the buck, if you will. That's obviously generically always true, but probably more true over the last 2 years as people think about it. But we feel that the value prop and where we kind of sit in the technology stack continues to resonate and be an important part. We've talked about the success we've had in new business despite the kind of macro turndown coming up on 2 years ago or 3 years ago. And we've continued to persevere there given the mission criticality of the platform, what we offer, our position as a modern player in the technology stack, the relevance of MongoDB, while it's still early for AI and how we can help and be an important part of people's technology going forward and sort of the future-proofing aspect of it. So in general, we feel good about those conversations, but I wouldn't take anything like -- I'm not sure that I can give you like a crystal ball on like macro IT budgets just because, again, we're a pretty small player amidst the grand scheme of things, and we tend to be at the higher priority stack of opportunities.
Michael Cikos
analystGot it. Got it. And I'll throw myself on mute after the questions because I hear the fire trucks in the background. New York City, you got to love it. But a question for you on the new capabilities and functionality as well. Like you guys have obviously announced Sector or streaming for that matter. Is there any significant change for like new logos acquired as far as -- are they -- are you noticing that they're coming in Q4, these newer features? Or no, is that still maybe additive but not why they would initially land with Mongo in the first place? The genesis of the question is, I don't want to overinflate the innovation taking place, but if you could color that, that would be great.
Serge Tanjga
executiveYes. Maybe I'll take a crack at that. So I think it depends a little bit by product. First thing I would say is that they are all still relatively early on. And when it comes to Vector Search and Stream Processing, they're both playing in markets that are nascent as well. So unlike our core market where it's well established and large, these particular features or products compete in small but fast-growing markets. And so on Vector Search, we've had a very positive feedback in terms of NPS scores and some of the sort of independent surveys out there. It's obviously a part of our sort of AI value proposition, but not the entirety of it. There is some evidence that on the self-serve side, customers are coming to us maybe not because of the Vector Search product, but that they are taking it up -- the new customers are taking it up sooner, which maybe indicates some amount of proclivity towards it. And then on streaming, it's really just exceptionally early stream processing. So it's hard to tell whether that's going to drive new business or just new workloads in existing customers or even just add-on spend to existing workloads, probably some combination of all, but too early to tell.
Michael Cikos
analystGot it. Got it. And that overindex on the prior quarter, but again, just wanted to get a better sense if we think through Atlas for a second. Mongo discussed strong new business, solid new workload acquisition. Can you help us think about the cadence of business through the quarter or workload trends, if any, to call out? Like does the October quarter tend to be pretty evenly distributed? Or is there anything to consider?
Serge Tanjga
executiveYes. I mean I'll come at it 2 different ways. The first way is a little bit of sort of walking and tackling inside the quarter. What we've said before and what's true now is that the second half of the quarter tends to be better than the first half because the seasonal recovery that we usually tend to see in Q3 happens in the back half. It's really usage growth post the summer holidays that sort of we see a bit of a pickup. And then second is, however, that seasonal recovery was more muted than expected. I think Michael mentioned that. And so the -- there was a bit of an improvement, but not as much as in years prior on an intra-quarter basis. And that partially impacts our guidance and sort of how we think about sequential growth of Atlas because consumption in Q3 really gets reflected in revenue in Q4 because consumption is sort of like -- the most real-time measure of the business and revenue comes a little bit after that. And then the other way that I would put it is, and obviously, this is top of mind for the investor community and we get it, is what Michael has said is that consumption growth has been slower than the same period prior year in Q3 as well as Q2 as well as Q1. And generally, we described -- obviously, we had a disappointing Q1 and sort of revised our Atlas consumption expectations then. And I won't belabor the puts and takes, I'm happy to, but maybe as a follow-up. But since then, we sort of generally found the consumption environment to be stable. Nothing on the second derivative to call out one way or the other. But consumption growth does remain below prior year.
Michael Cikos
analystMaybe one element to hedge out there, but I know we've spoken about macro, but why do you think that consumption element would be slower. Like what are we attributing to that slower growth from a consumption standpoint?
Serge Tanjga
executiveYes. So there was 3 pieces to it that we called out in Q1 and all remain true. First is, we've seen a broad-based -- modest, but a broad-based usage deceleration sort of across the base, which is reminiscent of other times when we've sort of seen a bit of a macro pressure in the business. It's smaller compared to the last 2 times we've seen this, one at the beginning of COVID and the other one, whatever that was, fiscal year '23 midway. But it was noticeable and just because of its breadth, it was important for us to call it out. So that's just in the , if you will, macro category. The second piece is, we have seen workloads we acquired in fiscal year '24 grow more slowly than expected, and those workloads are relevant for consumption this year because they are still early enough in their journey that they're growing meaningfully while already -- well, they're not growing from 0 like they tend to in the beginning. So they're in this kind of sweet spot. And so the fact that those are growing more slowly has an impact on consumption. And then finally, and only Q1, we had a disappointing quarter in new business. And if you think about that cohort, the fact that it was smaller, that's just the tax on your consumption growth going forward. So that remains the case, and those elements add up to consumption growth being slower on a year-over-year basis.
Michael Cikos
analystAnd to that, I think it was the second point, when we were talking about the new workloads acquired last year, just growing slower versus what previous cohorts have demonstrated, right? Has there been any improvement on that front? Or no, that still holds from where we are?
Serge Tanjga
executiveNo, no, some minor puts and takes, but overall, they're performing sort of along those sort of revised growth curves after Q1.
Michael Cikos
analystAnd then again, let's come back to the fact that October quarter did cite strong new business trends. What is management attributing to that strong new business trend then? Is it the fact that we've -- has there been some sort of change from a go-to-market standpoint that we're executing against? Was it just execution? Were there additional marketing campaigns? Just anything there?
Serge Tanjga
executiveNo. I would say differently. Overall, with the exception of Q1, we've been happy with our ability to acquire a new business, and I think Michael sort of mentioned that in his opening remarks. So it wasn't so much that Q3 was the exception or something unusual happening. It was more that the onetime we didn't kind of live up to our standards was the exception. That's it. But it's sort of a combination of all the things that we do day in, day out.
Michael Gordon
executiveI think maybe one thing, Mike, that's related to that, that sort of [indiscernible] to the investor crew is one of the things that we got and kind of took away or processed in the immediate heels of our December earnings call, was this question of like, are you changing things in go-to-market because we provided an update on things we've said at the beginning of the year, but somehow people didn't hear the update part, and I think maybe married some dots that don't get connected together in that with my departure, pending departure, we elevated Cedric into President of Field Operations and elevated one of his deputies, the guy named Paul Capombassis, to CRO. And I think people mistook that as some sort of much bigger reorg as opposed to sort of the natural evolution. And that combined with the fact that we are providing an update on some of our changes that we made at the beginning of the year in terms of go-to-market, about moving upmarket and things like that. People kind of heard that was new and said like why would you make new changes in the fourth quarter? And is something going wrong? Or are you rejiggering things or everything else? And so we spent time in those first few days at the relevant kind of conferences and one-on-ones trying to help people understand that maybe they were not hearing it correctly or connecting the dots in the wrong way. And so I think we got to most of that, but we do still hear that. As kind of part of the cleanup, I just want to make sure that people understand that we really haven't changed anything. There are no changes in strategies. We were simply providing an update on what we talked about at the beginning of the year and things like that. So hopefully, that helps a little bit, but we haven't gotten that question or at least adjacent questions [indiscernible] to properly address those.
Michael Cikos
analystGot it. Got it. On the consumption front, too, just wanted to call out, again, most recent quarter, consumption trends were slightly better than the revised assumptions that you guys had out there. And just to make sure the consumption that you guys did see broad-based across all workloads, was it maybe specific to a geography or a specific fleet of applications. Can you provide some more color on that front as well?
Serge Tanjga
executiveYes, it was slightly better and really nothing to call out in terms of a particular source. And I know this is a little bit of a cognitive dissonance, but I'm going to try it anyway. It is slightly better than we expected consumption growth. It was slightly better than expected in Q3, but it was nonetheless weaker than a year ago. So both things remain true.
Michael Cikos
analystOkay. Okay. And then just the route, like I know we've been talking about Relational Migrator. Can you provide an update? Like are you seeing an increasing volume of workloads coming through that Relational Migrator route? Or is it still in its infancy from where we sit today?
Serge Tanjga
executiveYes. It seems like Michael is having some WiFi issues. So I'll kind of take a first stab and hopefully, we get him back. So I would divide the relational migration story sort of into 2 chapters. The first chapter has sort of been around since before we've been public, which is we always had some amount of relational migration business. We talked about in our filings, roughly 20% to 25% of new business on EA usually is from relational migrations. It's less on Atlas only because the friction on onboarding new applications is so much lower on Atlas, that's really what our reps focus on. But relational migration has always been a portion of the business because for some number of applications in the normal course of business in a market that's $90-plus billion, the pain of running on relational becomes so acute that the company or the IT decision makers make the decision to transition. It's either because the app is so slow that it's impacting revenue, it's so slow or so fragile that it's impacting whatever regulatory environments you might have. Cost is occasionally the issue, but it's usually something about just the thing is crumbling. It's not working anymore. So I'm going to hold my nose and replatform it. And I say hold my nose because replatforming is not an easy thing to do. So that's the historical sort of story, and it's been with us for a long time. More recently, really in the past year, we've become increasingly bullish about our ability to combine some of our tooling, some of our professional services and the AI tools that exist out there to meaningfully lower the cost and the time and the risk of relational migrations. And this is what we talked about a couple of pilots that we ran early in the year that we basically found customers who are willing to partner with us, dedicate their own resources alongside our resources to pick a few of their existing relational applications, very old ones, and work hard to replatform them using the combination of services and tools that we sort of brought to the table. And the early results are very encouraging in that not only are we reducing cost in time, but we're reducing risk using AI tools because you can really use AI to test application to understand how it works and then you can -- when you rewrite it, you can test a new application to make sure that it works exactly like the old one. So that ends up being very powerful story for the IT decision-maker and one that's resonating, frankly, not even at the level of database administrators or developers, but at the C-suite level because the brittleness of an architecture, the cost and the complexity of it is a meaningful problem. So we're seeing demand. We're doing more of those engagements, a, for us, obviously, to help customers, but more importantly, for us to keep getting better at the process. We're encouraged by the interest that we're seeing from the customers. And right now, the focus is really just on doing more of them, developing a playbook, ensuring that we get all of them right because that's very, very important. But the signs for the market is that there's sort of -- in the fullness of time, there is significant demand for this, but we still have a lot to figure out.
Michael Cikos
analystUnderstood. Understood. And I know on the -- again, MongoDB has been citing, I guess, these strategic initiatives. And one of them, you can call it go-to-market, but I guess, this investment in the enterprise. Not surprising, larger organizations have stickier budgets, might be tougher to crack that, not initially, but once you're in, you're in. And we've seen this across our broader coverage. People are just moving up market. How has this expanded strategic account program tracking for Mongo versus expectations? Because you guys have been piloting or tooling around with this before making it a more concerted effort, right?
Serge Tanjga
executiveYes, yes. So first of all, thank you for the setup because you got it all right, but let me just expand a little bit so that everybody is on the same page. We started our strategic account program in fiscal year '21 as a pilot. And the general idea was pick some of our most promising accounts and give them more resources, either more rep time or more technical resources or customer success resources or marketing resources or some support resources and to see if we can get a disproportionate return on that investment because to your point, we already have significant traction in the account. And by and large, that effort has been successful. Not every account worked. But on average, the incremental return more than justified the incremental investment. So we've been slowly and deliberately growing that program over time. And really, what we've learned that is key is that you got to keep the bar high of what makes a strategic account. You need to have a certain amount of spend. You need to have visibility into some near- to medium-term pipeline. You need to have very strong technical champions. It really helps if they already signed their cloud services agreement, which means you've gone through their procurement and security org. And then you might be in a position to make the incremental investment and get the incremental returns. Like the way that I try to paint a picture of it is strategic account investment is like pouring gasoline. If you pour gasoline on a dry piece of wood, nothing happens. But if you pour gasoline on a piece of wood that's already on fire, you get a bigger fire. So that existence of fire is sort of key ingredient. And so what we're seeing is -- what we're doing in fiscal '25, but really going into fiscal '26 is increasing the size of the strategic account program. That's our version of dedicating more resources upmarket. So it's not generic. It's not broad-based. It's really at the very high end in our largest customers. And it isn't because we're seeing poor returns elsewhere or that we are seeing something happening elsewhere in the market that requires us to pivot. What we are seeing is a greater opportunity to invest in strategic accounts, not because we're lowering the bar, but because we're seeing more accounts clear the bar. And more accounts are clearing the bar, partially because we keep evolving and maturing as a business in the eyes of IT decision-makers. So more people are willing to bet on us. But also, what we just talked about, relational migration is getting kind of more C-suite attention, which is allowing us to just have a more holistic conversation of what we can do for them. And then finally, AI. Customers are working through what their AI strategy is and looking for companies that they can help them. And certainly, some of our largest, most promising customers look at us as a partner to not just provide them the OLTP layer, but just to be sort of a strategic resource as they think through all the pieces. So the tenor of the C-level conversation is changing, and that's the opportunity to invest more in the strategic account. And what I like about what we're doing is that not -- that isn't just some sort of a top-down idea that the senior management came up with and is rolling out, but there's actually demand from the field. And our bottoms-up planning, there was complete support from the field organization to do this. But that's what it means to us. And then the second chapter of that is money isn't infinite. So if you're going to invest more of it in the strategic account program, you got to pull back somewhere. And it's classic capital allocation. We're adding to our best payback channels and reducing payback in channels that are sort of near the bottom of the pecking order, which for us happens to be -- and by the way, always has been the mid-market. So that's what -- I know a lot of people are "moving upmarket." But to us, it has a very specific flavor and it's driven by specific positive signals that we're seeing in the market that didn't exist a year or 2 ago.
Michael Gordon
executiveWell, I think that's the thing. And hopefully, it's obvious and folks can probably connect the dots, but just to make it super transparent. As Serge was saying, those strategic accounts are the ones we always fund to the maximum that makes sense initially, like in any planning process because if they are your highest returns and your fastest payback, like why wouldn't you prioritize those? But the key thing is based on a whole bunch of factors, including investments we've made over the last few years, relational migrations, all the things that Serge was talking about, there's just more opportunity to do that now and we're trying to take advantage of that.
Michael Cikos
analystGreat. And has the company -- and apologies for not having this, but has the company in any way quantified either the size of the initiative from a manpower perspective or how many people are being reallocated for this or not?
Serge Tanjga
executiveNo. Keep in mind, this is really a sort of an elite program for a small minority or a 7,000 direct customers.
Michael Cikos
analystAnd the thought process then too -- I know you said it's nothing against mid-market. It remains fine there, but is the thought process then for mid-market better served by channel or maybe in a self-serve motion? Is that how we should think about that?
Serge Tanjga
executiveAs well as scaling some of our human teams to cover more of it. So it's seeking efficiency as opposed to pulling the plug, if you will.
Michael Cikos
analystOkay. And the second piece as well, again, I'm just trying to go through the initiatives that I have on my side. But one of them was maybe around building up the Proserve capabilities, either directly or through partners. And I just wanted to get a better sense. Is that -- should we interpret that as helping enable in any way the strategic account initiative? Or no, does that...
Serge Tanjga
executiveThat's related to relational migration. So that's related to the app modernization because services is part of the equation. Particularly early on, you really need people there. The tooling is not enough and AI models aren't enough either. You need your people on the ground to connect with the customers. And the reason is because relational environments are very heterogeneous among customers in terms of programming languages used, in terms of the actual relational database use, ORM layer on and on and on. It's very multiplicative. And we're early on. We're still -- have done this for a relatively small number of customers. So each is still bespoke. And although, obviously, as we sort of acquire more knowledge in this process, there will be more templates and more things that we can automate and kind of do effectively and automatically. But for the time being, there is a human element, and that's what the professional services investment is about.
Michael Cikos
analystGot it. I think one of the other things that I know the management team here has called out is the idea that, yes, there's a lot of experimentation for some of these AI-based applications, but the majority, it's still unproven whether or not -- how many of these attain product market fit. And so I was wondering, do you guys -- is there a parallel that we can draw for, I don't want to say non-AI , but the original or initial cohorts that maybe didn't have such an AI-based flavor to them, like do the majority of those not have product market fit and then eventually some of them hit? Like how do I -- is there even an analogy there or no, is just really...
Serge Tanjga
executiveYes. Let me start with just telling you how we see the AI market at this moment in time. So first thing I would say is not very many people in the world knew what ChatGPT was 24 months ago. And so this whole AI revolution is really 2 years in the making. And 2 years, it seems like a long period of time if you're reading the newspaper every day, but in the world of enterprise IT, it actually is -- things are just getting started. However, we are living in this very interesting cognitive dissonance moment from our perspective, and this is the following. There's a relatively small number of very, very popular AI applications that have caught popular imagination, right? #1 ChatGPT and #2 Anthropic, right? And those have billions of dollars of revenue associated with them and everybody is using them, right? We are using them, our children are using them and on and on and on. And they paint the picture of the world of AI. But once you move past those relatively few highly popular and visible applications, there is relatively few that have truly made a product market fit as revenue measured in the tens, forget hundreds of millions of dollars. And so if you think about the company to be a 7-figure customer for us, probably does need to have -- $10 million in revenue won't be enough for you to have database spend on $1 million plus, right? So like you need companies to generate their own business and their own revenue to be a meaningful contributor to us. And simply, the number of them right now isn't particularly large. We talked about one 7-figure customer in our call. But it's really an indication of the relatively few AI applications or companies that have reached that meaningful mass. Will that change in the fullness of time? Absolutely. Will that number be higher a year from now than it is today? Absolutely. And we think for reasons that Michael covered that we have every right to win a disproportionate share of those, mean disproportionate to our current market share, right? And that's the opportunity we're excited about. I don't know that I can give you a parallel around prior sort of product adoption cycles or technologies and sort of what it means for product market fit other than to say that nothing that we're seeing with AI as unusual in that new technology is being deployed. First, it needs to make it into production, then some and then more will make product market fit. It's really just about the moment in time that we was. The only thing that's perhaps different is that there are these relatively small number of very large and very successful applications that are maybe painting popular perception around how far along we really are in this AI journey.
Michael Cikos
analystUnderstood. And I do want to be true to my word here. We did get a question in from a client that I want to ask while we have you. Question goes. I know it's early, but can you speak to customers that have GenAI in production and are therefore doing inference. Is MongoDB being used on that inference component? I would think large organizations that are starting to tinker might be using Mongo for that purpose. Anything you can share?
Serge Tanjga
executiveIt's really premature. There's really very little in terms of patterns that we can infer, either in terms of the intensity of the use case or anything that the sort of general asset does. Obviously, we're eager to find out ourselves, but at the moment in time that we are in is still early.
Michael Gordon
executiveAnd we've talked about this, and it's not unique to MongoDB, but it's broader in that there's a lot of enthusiasm, there's a lot of experimentation. Obviously, in investor settings and conferences and everything else, people talk about it a lot, but that's sort of like reasonably ahead of where like the day-to-day reality is. And I think Dave gave an example of one of the largest financial services companies in the world, tens of thousands of developers. And I think last time I heard they had something like 20 AI applications in production despite having tens of thousands of developers and 0 of them were customer-facing because they just didn't trust them, right? So there's a lot of enthusiasm, but a lot of concern, especially about how it impacts reliability, hallucination, all those kinds of things. And so it will take time for it to play out, and that's not a unique to MongoDB thing. I think that's sort of a broader thing, but we're eager to capture or kind of more than fair share, if you will.
Michael Cikos
analystExcellent. And maybe time for one more here, but this is kind of just a little question I had. So I'm happy I can stress test it against you guys while we have you. With GenAI, does that place a greater emphasis or greater demand on a time-series-based capabilities given the need for real-time insights or not necessarily?
Serge Tanjga
executiveNo time series is specific use case. You're right in real time, but it doesn't -- real-time and time series partially overlap, but not fully. So we're happy with the traction that we're seeing on our sort of time series offering. But the -- it's particular type of use cases that we build and we would expect AI to be broader than that.
Michael Cikos
analystUnderstood. Okay. And I will keep it -- I said it was the last one, that will be the last one. But thank you very much for the time, guys. I really do appreciate it. Michael, been great working with you. Thank you.
Michael Gordon
executiveLikewise, thanks for everything. I apologize for a little bit of WiFi issue in the middle there, at the hotel here, but thanks for everything, and I appreciate you always taking the time.
Michael Cikos
analystExcellent. Have a good day, guys. Take care.
Michael Gordon
executiveThanks.
Read the full transcript via the API
You're viewing the first half of this call. Get the complete MongoDB, Inc. transcript — plus 248,000+ transcripts from 12,000+ companies, speaker segments, AI summaries and full-text search — through the EarningsCalls.dev API.
Get the API View API docs →This call discussed
For developers and AI pipelines
Programmatic access to MongoDB, Inc. earnings transcripts and 248,000+ others is available through the
EarningsCalls.dev REST API. Plans from $24.99/month — full transcripts, speaker segments,
full-text search, and the recently-added /api/v1/transcripts/recent polling endpoint for ETL pipelines.