Executive readout · one minute
Webcast research workspace
Read the call alongside every captured source. Transcript, audio stay in one workspace.
Conference · 2026-09-09
You came from your AI assistant. Add Equibles to it and ask about this data directly, free.
Executive readout · one minute
Read the call alongside every captured source. Transcript, audio stay in one workspace.
Research coverage
2 live sources
Switch sources without leaving this page or losing your listening position.
Open the source you need; every reader stays inside this workspace.
You're making the appearance at the conference. CJ, it's great to see you. I thought we'd just kick things off. It's been almost a year since you've taken over the helm of Mongo. Just give us some of your observations about the business, and what are your top priorities for the year ahead?
Absolutely. First, great to be here. Thank you for hosting us. You know, we had a print last week on Q2. We felt that overall revenue acceleration and first time hitting 30% total revenue growth in a long time was just fantastic. And as I have been here for a year, there are two or three things that I'm seeing very clearly. So, number one is I wanted to make sure once I joined the company where we have the biggest potential, right, where we have the biggest potential and the why behind the potential. And what I saw in the last 10 months or so is that, number one, in enterprises, we are definitely becoming a standard for modern databases, whether these are financial services institutions, insurance companies that have a lot of unstructured data, and they want to modernize and move it to multi-cloud estate. We also saw over last year or so that public sector demand is there. It's early, but public sector demand is there in large enterprise. And then as I traveled in Tyler, Europe and Asia Pacific, India was very interesting to see a lot of new digital native companies building on MongoDB like Zomato and others. And then in Europe, sovereign cloud, us having that flexibility that you can run anywhere, so you can self-manage MongoDB, was very prevalent in the UK, France, and a few other places. So that's in the enterprise environment. The second learning I had was that many AI-native companies are building on MongoDB, which was a new thing to me after I joined. And when I spoke to folks at Mercore or whether you look at 11 Labs, and there are many others like that that we shared even last week, like EU, Harvey, and others, these are AI-native companies. And once they started hitting decent scale, we were the only answer. So that was very encouraging to see, even though some of them did not start with MongoDB, they hit scale limits on Postgres or whatever first-party database from Hyperscaler they were using, and then switched to MongoDB, and now MongoDB is just a foundational operational data layer that they don't even think about. So that's my second bucket. And then the third bucket that we shared last week is seeing early traction, and early is an important word, early traction with the labs, as in specifically Frontier Labs. And why are they using Mongo? What does that look like? Because, you know, they have many products. All these labs now have many products. So what are specific use cases they use us for varies by lab by lab. And again, fairly early. We don't have history with them for multi-years. So that was very encouraging to see that one of the smartest teams at one of these labs said they have looked at every alternative they thought they should be built something on open source and decided Mongo was the answer. And that just gave me a lot of conviction that this is a great technology for AI workloads. So that's how I would classify it in three buckets, and that's the learning I have.
That's great. And I remember when Dave made the handoff to you a little under a year ago, obviously you've had an impressive background, Cloudflare and ServiceNow, kind of calling on the C-level of the Fortune 500. And I think that's not something Mongo necessarily had in its DNA, kind of that top-down selling. So how have those conversations been going? How would you sort of characterize where we are in potentially some of those larger expansion opportunities? Maybe some of them were using Mongo departmentally. Where are we at in that adoption?
Yeah. That is absolutely a focus where I wanted to leverage the relationships I had and the customer focus I had in my prior chapters of career. And calling on to the CTOs, the CIOs, those are typically the two or line of business CIO at a bank or an insurance firm. It's going very well. So one is they appreciate having that relationship to say, okay, Tyler, my biggest thing is that some of the large enterprises who are spending, whether it's seven-digit ARR or eight-digit ARR, didn't even know that they were spending that much and that they were using MongoDB for some of their mission-critical workloads. So once you establish that relationship, and what I noticed is while MongoDB, like you said, was workload by workload, and our sales team did a fantastic job with the product because developers loved the product, and now you come, I don't want to say top-down, but at a C-suite level, the biggest learning I had was that AI decisions were being made top-down with the enterprise architect, Chief AI officer, chief data officer, pick a title, or somebody like that. And that's when you go in and say, hey, do you know we have vector search integrated and text search? We have now voyage embeddings. And almost all of those conversations, I do approximately 10 to 12 conversations a week. They're like, oh, we did not know this, right? So we are now gaining traction to say, I'll just give an example, large biotech company, I meet the chief data officer in South San Francisco. Next thing, he's like, talk to my enterprise architect. Fast forward four weeks later, let's do a POC on our AI workload to see why we need real-time operational data via MongoDB. So that has started. So that's one. And then the second thing we are discovering when I talk to the C-suite CTO, CIOs, the modernization that they need to do to get AI ready in the enterprises is a real thing. And how can we help them? So that's where also we are a little early, but I'm like, hey, we can help you modernize from a particular relational database that's end of life or whatever. And they're like, oh, I didn't know that. How fast can you do that? And my answer is that we believe that our teams can reduce it from years to months or months to weeks or modernization effort on the workload. And we have a set of tools and products for that. They're like, okay, let us get started there. So these are the things that make me really, really encouraged about the market size that MongoDB has and where we can play.
Okay. And going back to some of your points you referenced earlier around the AI natives and AI labs, I think it's sort of an interesting observation that maybe these companies didn't necessarily start on Mongo, right? But now you're actually seeing more traction, you know, maybe a couple of years into the AI adoption cycle. So, like, what are the use cases that you're seeing the labs, I guess, use you for? And I know some of the recent announcements, like some of the wins that you announced in the most recent quarter, there was, you know, perhaps a win to kind of distance themselves from one of their larger partners that they use on the database side. So can you just talk about the use cases and kind of why you're winning and how you see the potential in those large labs?
I would say, first, the strengths of the platform is the reason we are winning, whether it's AI Native or whether it's Frontier Lab. And I'll tell you what, specifically three things that always stand out to me when I speak to an engineer who makes a decision to use us for a particular workload. So document model and JSON and document model just make it super easy because that's the language of AI. And us being JSON native is definitely an advantage. And that not being rigid, I worked for Oracle for eight years. And in Oracle, the DBA has a lot of power still when you want to make a change in any database, tables, queries, views, things like that. MongoDB is very agile. So the document model combined with agility of it, because your AI use cases change all the time, you're trying to move really, really fast. If you look at these labs, they are trying to ship products so fast compared to a typical software lifecycle that we have seen in the past, right? They're almost like at a consumer company level. So agility of MongoDB definitely stands out. Second is just scale. We can scale out. We can scale out to massive, massive amount and not fall over because it's a scale-out architecture. And then the third thing I would say is Run Anywhere. Run Anywhere does help because one lab or one of the use cases, when they saw that we can run nodes across two hyperscalers, that was a big advantage to them because they were running out of capacity in one hyperscaler, and they're like, okay, so are you saying that we can have redundancy in this other hyperscaler that is really meaningful to us? And so they choose for one of their workloads us. So these are the three reasons, Tyler, that still why, whether it's labs or AI native company, chooses document model, scale, and run anywhere. And then in terms of use cases, sometimes, you know, if you're interacting with agent, you have lots and lots of conversations going on. Next time you interact with agent, it's almost like they forgot that you had that conversation with that agent. So, sometimes for one particular product, one of the labs is using us as a conversational memory layer. For one of the AI-native companies, we are completely what I would describe it as just the operational data layer. And what they told me specifically, having search in a different, having a pipeline for search, search in a different database, operational data layer separate that they were using before. So they had multiple moving pieces. And for that 75 million agents, this is 11 labs, growing like crazy. They just could not scale because they had to maintain the pipeline between the ETL, the data out, put it for search, then sync it back in. And now we are the underlying operational data layer for real-time agents, and they do speech-to-text and text-to-speech, so a lot of unstructured data. So those are the kind of use cases where we stand out. There is really no competition, because even if you use, I would say, our competition for these kind of AI-native companies, where they are making an explicit or implicit decision, is sometimes what a coding agent may tell you something, and then you just choose that. That database or a first-party database from a hyperscaler, and then eventually you hit scale limits. Right.
So even where you are running into Postgres being used, it's not from a large Postgres-specific vendor, right?
It's just kind of either open source or from- Or the first party from a hyperscaler.
Yeah, I see. Okay. And going back to your results last week, as you pointed out, total revenue growth, the highest in many years, north of 30%. I think you look at bookings, customer ads, net retention, all improved quarter over quarter. Yet, I think investors focused on Atlas growth. It stayed consistent versus we look at some of your peers in the space are seeing more meaningful acceleration. So how would you just encourage folks to kind of dissect those results? And, you know, I guess if you're, we're sitting here a year ago and Atlas is bending that growth curve going higher, what are the things that could make that go even faster?
First, you know, what I want to touch on for our investors, and this really matters to us, this will be the second year that our revenue is accelerating, total revenue.
Yeah.
Revenue is accelerating. And that is meaningful to us. And our operating margin, cash flow, all the numbers that we printed last week, fundamentally, the business is very good, right? The business is very good. When you look at the overall business, it's durable growth, while profitability is increasing. That is always hard to achieve. But the teams are able to do that. So I'll touch on that from a total revenue comment perspective. Second thing I would say is, what would you need to believe? You know, when people say, okay, CJ, your peer group of a data warehouse company or peer group of an observability company, Tyler, I have done technology for a long time. Those are very different things than an operational database, right? Understood, but we are put in that peer group, totally fair, and they will say, hey, AI is accelerating XYZ, which is totally fair and a lot of credit to them. Most of the data warehouse use cases are employee-facing, right? MongoDB, when a bank or an insurance company or an AI-native company like Eleven Labs uses us, they are almost always customer-facing use cases. And in customer facing use cases, as companies, enterprises build more agents for customer facing use cases, that's when you will see our growth curve starts to bend. And we still feel, like I said earlier, I speak to banks, insurance firms, healthcare companies all the time, and they are still not doing customer facing agents at scale. Sure. When they do customer-facing agents at scale, you will see our consumption go up and so on, right? Compared to right now, you do a query on data warehouse using one of the AI agents and you get better answers in natural language. Great. That's great. But if the answer is not accurate, you don't have to deal with regulators and others for internal-facing application. Versus for external-facing, the bar is very high, including your firm we talked to and many others. So that's number one. When will agents that are true customer facings start to scale built on MongoDB? So that's one. Second, I definitely feel that our vector integrated with now auto embeddings that we just released a few weeks ago will also be a tailwind. We are still early in that. But many of the banks I talk to, they have a different vector database. They have different operational database. Then they're using embeddings from a frontier lab or somebody else. All of those being unified in Atlas is definitely going to help out when enterprises start. That's where the big TAM is. Start building agents at scale. So that's second. Third, from a growth perspective on Atlas, is we just released fully managed MCP functionality for CloudCode, Codex, and GrokBuild, which was on August 13th, not even a month ago. And we are seeing it's been only now three and a half-ish weeks. We are seeing higher traffic on Atlas. Once that we provided fully managed MCP capabilities on August 13, we launched it at GA. So we will provide additional updates on how that is going on Investor Day on September 29, which will have six weeks of data points on what we are seeing. But I personally feel that that is something super important that we had to do. We got it done. I would argue that we are a little behind on that compared to the other startups and others who did that. But now you can work in Atlas via cloud code is a pretty big deal to us. Same thing with Codex. And that will be received very well by developers who want to either build, provision a cluster on Atlas and so on. So it's early, but that was definitely necessary. We had to get done, as in Musk had done, and Pablo and the team did a great job to get it out there, including with Vercel V0, which we are behind. You had called this out with me many quarters ago, and also Cognition Devon. We are really excited about our partnership with them, technical partnership with them, and what they are trying to do to also modernize databases and so on.
Right, right. Now, that's super interesting. So those two kind of big product releases you called out, the auto-embeddings, that sort of, think of that as maybe more, you know, a tailwind for the enterprise customers and then fully managed MCP server. I mean, that could even be a tailwind for the self-serve.
That's exactly correct. That's exactly right. And what is encouraging, you asked me, hey, what's your observation in the first year? Like, to add a new customer, paying customer, is really, really hard. And when we added these many customers in the last few quarters, over time, they are almost all on Atlas. Yeah, probably 99% of new customer ads are Atlas, meaning in cloud. And Voyage has clearly been received really, really well. Because you know why? When we looked at why Voyage customers are being added at such a rapid pace, most of those customer ads came via referral from CloudCode and Codex, which was not happening for Atlas. And that now acts as top of the funnel for us to potentially upsell Atlas. So that new customer growth, when that also kicks in, when they start building workloads in a meaningful way, will also help Atlas.
I see. I see. Okay. And, you know, I guess as you just think about the, we talked a lot about kind of your view on when we see the enterprise ramping and all that. I guess, like, do you have, it's difficult to put timeframes on it. It varies by industry. Certainly, I would say we're seeing customer facing use cases ramp at the AI labs. I mean, you talked about RV. We had Lagora on stage yesterday. I mean, these companies are really inflecting this agentic labor opportunity. You know, customer service is another big area. We just talked to Salesforce. You know, you have companies like Sierra as well. So, you know, sounds like you're partially participating in the AI lab customer-facing use case, but where do you think, you know, the non-AI labs are in terms of that? And again, we understand like a big bank like Citi is regulated, but maybe something, you know, retail, e-commerce could be a little faster than a big bank. Like what's the general timing?
Yeah, I think that's a fair question. One of the places where we are seeing higher enterprise rollout on MongoDB for customer-facing workload or product basically at the end of the day. So if you look at 11 labs, whether you argue that they are a lab or whether they are a product company, I mean, millions of agents running on MongoDB, they were, Tyler, exactly a year ago, they were not a customer, okay? And now they are a customer that is growing very rapidly, right? So that's number one. Number two, where I see higher traction among the industries, so bank would be behind from customer facing perspective, is tech companies. So tech companies, cybersecurity companies that are built on MongoDB, whether they are cybersecurity companies out of Israel or cybersecurity companies, some out of United States of America, we are seeing them building agents on top of MongoDB and rolling that out for them. But we are the operational data layer. So tech is a vertical where I have seen higher traction. It's still this year is when I saw the growth with some of these cybersecurity companies that are built on MongoDB because we do unstructured data very well. So like logs and things like that. So that's tech is vertical. Retail, airlines, others, I have not seen massive customer facing agents still. Being rolled out. Telecommunications company, some internal facing, but not external facing yet. So when I look at that enterprise bucket, what I personally feel is that after tech, most likely it's going to be retail and financial services that would follow, including insurance, before like consumer product goods company or manufacturing go there. Right, right. Okay.
That's super helpful. You know, I guess going back to the strength in the new customer ads, which, you know, again, really impressive. I think 2,900 new customers, the highest you've ever added. Many companies out there are talking about top of funnel. Yes, right? Maybe a little bit more on the application side. But what are some of the things you're observing in what's driving such outsized top of funnel strength? And, you know, I think you alluded to this dynamic earlier, whereas if you go on to, you know, Claude or ChatGPT, it might initially default you to recommend to Postgres. But I presume you've been working hard at, you know, getting Mongo more in those conversations. So just talk about the top of funnel, the things you're doing, and how you see that durability of the strong customer ads. Absolutely.
So first bucket, I would say us getting new Voyage customers for embeddings, which are typically almost always AI use cases for the companies that use Voyage, right, obviously. And when we see that, that is, I almost guarantee you, mostly driven by Cloud Code or Codex recommending, please use Voyage, right? They say it on Anthropics' website. On Anthropics' website, they say it, but Codex, I mean, OpenAI has their own embedding model. But if you say what's the best embedding model to use, you get pointed to Voyage. So I would say the cause and effect on Voyage customer ads is primarily driven by coding agents. And then it is the opportunity for Ryan and the team, our sales team, to now upsell them on Atlas. So that becomes a very meaningful top of the funnel for Voyage. Now, when we are getting Atlas customers on top of the funnel, those customers are still very human-driven because we didn't have this managed MCP functionality that we just released four weeks ago. So human will say, I want to spin up Atlas, and then they will use Atlas in the customer ads that we continue to get, and then they scale over time. I mean, one of the labs told me that they actually came via self-service channel, and then we noticed it, and then we put team on it to make sure that they can scale nicely and so on. So with this managed MCP functionality, Tyler, I'm optimistic that we will continue to see new customer ads. Now, you cannot game prompting. You just cannot with these agents. If you use certain words, of course, it will pick MongoDB in the prompt. If you don't pick certain words, it will default to a Postgres or things like that. So yes, the teams are working hard because we also want right use cases to be built on MongoDB. If it is some employee-facing apps with 1,000 users, we really don't want that workload. We want the workload that can scale a quality workload versus a quantity workload. I see. So that's the focus we have.
Okay. And you brought up go-to-market a bit. I did want to touch on that, just given some of the changes this year. You brought in Ryan McBann. What's sort of the state of go-to-market? I mean, I think as we look at the commentary over the last few quarters, you've kind of consistently called out strength in North America. I'm sure there's, you know, areas that are not performing as well as North America. Like, give us a sense on his priorities and how do you kind of see the productivity and, you know, the ramping of the reps that he's brought on.
Absolutely. I'll do that. Jesse, you want to touch on regional performance, and then I'll go into the details.
Yeah, I mean, we've continued to see strength, particularly with our largest customers in North America. That's a very encouraging sign. North America, obviously, our largest region. There are some areas for opportunity for us to improve. So one is U.S. Federal. We're investing in FedRAMPi, and that will hopefully open up incremental opportunities. That's one of the reasons we did the Clarity Business Services deal. And then APAC. APAC is an area where there's an opportunity for improvement. Japan is a very large database region. It's one we're going after, still very early stages. And we definitely see opportunities to accelerate our success in Asia. That's an area that Ryan's made some changes, and we're optimistic that they'll have positive results on a go-forward basis.
And specifically, what I will tell you is, when I look at the NRR number, and you cover Tyler's software industry, you see that's a very important metric on the retention rate, 122 NRR. But even when I look at NRR underneath for our self-managed as well as Atlas, both are very healthy. It's not that one is driving the other. They both are very healthy. So the blended rate is 122. In terms of Ryan and GoToMarket, if Asia is a smaller percent of the total business, but it's a very important business because you have a lot of digital natives in India, you have digital natives in China, Korea, all these places, and most of those regions love MongoDB. But we also need to serve the large enterprises that really well. So that's some of the changes that he's making in Asia.
Okay.
Okay.
Got it. And as we think about the migration opportunity, right, we've talked a lot about these new use cases, and clearly there's going to be way more new database use cases than existing. But migrations have been an important part of the story over time. And, you know, you've rolled out a number of initiatives there. You talked about partnership with Cognition. This MAP program has been announced, I think, over a year ago. So how do you kind of see the migration opportunity today? Is that something you're investing more resources in, or does it make more sense just to prioritize new workloads?
So being in the database industry for a long time, both as a customer and as a provider, I mean, Oracle is going to be 50 years old Next year. I mean, think about it. So 50 years old company and database industry around 60 years. So we have the most modern database. So the opportunity, Tyler, just to answer, absolutely exists. The change I made once I joined with Mike and the team is that we had taken this very people-centric approach on migration. Hey, we will help you migrate from Oracle to MongoDB for the right set of Use cases are some relational database. So what we decided that this year, as in this current year, we are in fiscal year, we are going to get the product right. And we want to provide a product to our customers that you can migrate from a relational database to MongoDB faster. And the people portion is a smaller portion of that engagement. When we announced it, it It was very people-driven, services-driven approach. We are changing that to product-driven approach, and AI definitely helps with that, whether it's Cloud or PickOne, as well as partnership with folks like Devon helps. You do that, and then you go to customers and say, now we can migrate faster. So we are going to put fuel into that in the next fiscal year once the product is ready. But the product, we are currently working with very large customers on very specific, what we call design partners, to make sure that our product really works so that they can migrate to Atlas.
Yeah. And CJ, in sort of the closing question here, if we're sitting on this stage a year from now, which you're definitely welcome back, what are the two or three things that you hope to have accomplished by then?
I would say you touched on this on the priority. First, we have to be the best database. Whether it's self-managed, whether it's Atlas, it has to be the best database that can run anywhere, and we just want to continue to focus on that. The best product always wins in the market. Number two that I have shared, human developers love MongoDB. I want coding agents to love MongoDB. And managed MCP was the first big progress we made, but we'll continue to invest in that so that, hey, I want to do this. Of course, you should build on MongoDB. So that would be the second. And then the third thing is you will see some of the exciting product announcements on September 29th, which is 20 days from now, around what else we want to do so that we are the default real-time operational data layer for AI. I mean, those are the three things. Yeah.
Great. Well, let's wrap it there. CJ, Jess, thanks so much for coming to the conference and appreciate everyone for joining the session. Thanks, everyone.