Good day, and thank you for standing by. Welcome to MongoDB's Fourth Quarter Fiscal Year 2026 Earnings Conference Call [Operator Instructions]. Please be advised that today's conference is being recorded. I would now like to hand the conference over to your first speaker today, Jess Lubert, VP of Investor Relations. Please go ahead.

Thank you, operator. Good afternoon, and thank you for joining us today to review MongoDB's fourth quarter and full year fiscal 2026 financial results, which we announced in our press release issued after the close of market today. Joining me on the call today are CJ Desai, President and CEO of MongoDB; and Mike Berry, CFO of MongoDB. During this call, we will make forward-looking statements, including statements related to our market and future growth opportunities, our opportunity to win new business, our expectations regarding Atlas consumption growth, the impact of non-Atlas business and multiyear license revenue, the long-term opportunity of AI, our financial guidance and underlying assumptions and our investments and growth opportunities in AI. These statements are subject to a variety of risks and uncertainties, including the results of operations and financial conditions that could cause actual results to differ materially from our expectations. For a discussion of material risks and uncertainties that could affect our actual results, please refer to the risks described in our quarterly report on Form 10-Q for the quarter ended October 31, 2025, filed with the SEC on December 2, 2025. Any forward-looking statements made on this call reflect our views only as of today, and we undertake no obligation to update them, except as required by law. Additionally, we will discuss non-GAAP financial measures on this conference call. Please refer to the tables in our earnings release on the Investor Relations portion of our website for a reconciliation of these measures to the most directly comparable GAAP financial measures. With that, I'll turn the call over to CJ.

Thank you, Jess, and thank you, everyone, for joining us today. To begin, I would like to provide some observations from my first full quarter at MongoDB. Over the last 100 days, I have spoken to more than 200 customers globally, spanning from AI natives to Fortune 500 enterprise customers that are leveraging the MongoDB platform to drive innovation that is critical to their business. Whether it's an AI or digital native looking for a highly performance solution that dynamically scales, a large enterprise looking for multi-cloud resiliency for their modern mission-critical applications or a customer seeking an integrated offering for AI agents with features such as search, vector search and embeddings in a single intelligent data layer, customers are excited about the strength of the MongoDB platform. My key takeaway is that MongoDB's foundation is in great shape, and the company is well on its way to become the generational data platform of choice in the AI and multi-cloud era. Now on to this quarter's results. We generated total revenue of $695 million, up 27% year-over-year, beating the high end of the guidance by 4%. Top line strength was driven by Atlas, which grew 29% year-over-year crossing the $2 billion run rate mark for the first time and generating a record $114 million in net new revenue in the quarter. Non-Atlas grew 20% year-over-year, our best growth quarter in the last 2 years. We signed several large deals in the quarter, including an approximately $90 million transaction with a large tech company that plans to expand both core and AI workloads on Atlas and a greater than $100 million transaction with a large financial institution for Enterprise Advanced referred as EA, representing the largest TCV deal in the history of MongoDB. We delivered a non-GAAP operating margin of 23%,…

Thank you, CJ, and good afternoon to everyone on the call. I will begin with a review of our fourth quarter fiscal '26 results and then finish with our outlook for the first quarter and full year fiscal '27. In order to spend more time on the fiscal '27 outlook, I'll be a little more concise on my fourth quarter comments. I will be discussing both GAAP and non-GAAP results. As CJ mentioned, we had another strong quarter as we exceeded all of our guidance ranges and finished our fiscal year on a high note. In the fourth quarter, total revenue was $695 million, up 27% year-over-year and above the high end of our guidance. Our income from operations was $159 million for a 23% operating margin compared to 21% in the year ago period. We achieved positive GAAP operating income in the fourth quarter. We are very pleased with our stronger-than-expected operating margin results, which benefited entirely from our revenue outperformance. Net income in the fourth quarter was $143 million or $1.65 per share based on 86.5 million diluted shares outstanding. This compares to net income of $108 million or $1.28 per share on 84.6 million diluted shares outstanding in the year ago period. Shifting to our product mix. Atlas revenue momentum remained strong with year-over-year growth of 29% in the fourth quarter, which accounted for 72% of total revenue, up from 71% in the year ago period. Atlas growth was driven by continued strength with our largest customers in North America and Europe, where we saw strong momentum with growth of new and existing applications. We believe this strength reflects the growing strategic importance of Atlas to many existing customers and is a positive indicator of future growth. You can see the success with existing customers in our…

[Operator Instructions]. And our first question comes from the line of Raimo Lenschow of Barclays.

Congrats great fourth quarter. Two quick questions. One for you, CJ. At your big event in January in San Francisco, what were your impressions about developer buy-in? Part of the reason for the doing is like to increase mind share again, like share a little bit your experiences there? And then one for Mike. On EA, next year had a bigger cohort than this year, I'm just wondering if the strength in the second half of this year, was that earlier renewals for next year? Or is the cohort still in place?

Thank you, Raimo. Appreciate it. So January 15 event, our dot local San Francisco, I would consider a great success and I would put that in 2 buckets. Number one, we exceeded even though it was a week day, many, many founders, builders who came to the event, and there was a long line outside for people to get into the conference that give me really, really good feeling that we invested in the right area. Number two, when we looked at the attendees, Raimo, I would say, compared to other typical dot local events where people who are already customers or builders of MongoDB. Here, around 70% had not used MongoDB. And that's what gave me a lot of conviction that it was a successful event where we are increasing the mindshare of the builders in the San Francisco Bay area where a lot of AI native companies are being built. The last thing that I'll touch on is that because of the success of that event, and continue to make sure that we are on top of mind for all these AI native companies, whether they are in security, whether they are in fintech, whether they are in domain-specific AI, we are going to repeat dot local in San Francisco, again, in August this year, which we have not done before based on the success. Mike?

Thank you, CJ. Raimo. Thanks for the question. So on EA, a couple of things. So we're super excited about the year we had fiscal '26 was a very strong year and especially Q4, not only in the run rate business, but obviously, all the multiyear deals. So it's a big business, thankfully. There's always some puts and takes in terms of renewals. I would say there's no material change to the cadence of early renewals. And keep in mind that even if there is one, you won't see it in revenue until that deal comes up. So you shouldn't see any major impact in cohorts next year.

Our next question comes from the line of Matt Martino of Goldman Sachs.

CJ, maybe to start with you. You noted the transition for Cedric and Paul has been in the works for some time. Given that visibility, can you provide more color on the current status of the CRO search? And specifically, what are the primary attributes you're looking for in a successor that led you to announce Erica's appointment today while the search for a new revenue lead remains ongoing.

Absolutely. So Matt, here is how I would describe it. Personally, being here, as you have seen that I've spent a lot of time with not only our customers, but with our go-to-market team. So we are in the final stages, but we want to make sure that we get an excellent candidate for our Chief Revenue Officer. Erica's focus will be as a Chief Customer Officer to ensure that customers who purchase or decide to use MongoDB platform, they get to value by providing all the post sales support functions, whether it's technical success, technical support, many other things like professional services. So one, Erica is going to focus on customers who have already bought MongoDB or expanding with MongoDB, how do they get to value and how do they get to success. In terms of the CRO search, Paul is staying fully through Q1 and help us transition through Q2. And from the attributes perspective, I want somebody who is very focused on high end of the enterprise, understands how things work at MongoDB from a Main Street perspective, but also working with the management team as we expand into both the AI natives as well as enterprises who are building more mission-critical workloads on MongoDB, including AI. So that's the mix, I would say, is somebody who is strategic, who understands consumption-based models on how MongoDB really operates, of course, our Enterprise Advanced business, and has relationships into the high end of the market where we are getting significant traction besides AI native companies, which is hardly.

Okay. Very clear. And then Mike, maybe for you, just a couple of major EA deals were announced this CJ talked about the renewed importance of on-prem. I guess under that backdrop, should investors be recalibrating expectations around growth for the EA business as we look out over the next couple of years?

Yes. Thanks for the question, Matt. So as we talked about -- so 2 things, I think, of importance in the prepared remarks. One was CJ walked through some very large deals. As you look especially at regulated industries, governments, it is a very important product that we have, and those are some of the largest customers at MongoDB. In addition, we're starting to see more of the bundled deals. The on-prem piece is a huge part of it. So what I would say is yes, it will continue to be of importance. We are actually investing in EA to bring it to parity to Atlas. So certainly, our expectation and hope is that we continue to grow that and can even accelerate it in the future.

And Matt, I would say in speaking to customers, because this conviction is over a large set of very important customers that is definitely the trend that I'm speaking from our customers is, number one, that because of a variety of issues related to also AI that for mission-critical application, there is this trend I'm seeing where they do want to keep their critical data estates on-prem. And this is not just only in financial services, we are seeing that in health care and other verticals like government. But when I was in Europe and even in Asia, I'm also seeing there that there is a preference for those industries to also use MongoDB potentially with EA and only certain workloads in the cloud. So this will play out and all we wanted to outline in today's call is to say this is strategically very important as in the product line for our customers, and we need to invest in it because it is strategically very important.

Our next question comes from the line of Jason Ader of William Blair.

For CJ, my main question is, how is your product and go-to-market strategy changing, if at all, ahead of the growing reality that agents are going to be the things that are spinning up most databases and not humans in the future.

I would say, Jason, I have a very simple philosophy here. And the philosophy also was validated by one of the AI native companies that has completely built on MongoDB. They had many choices in many clouds and they chose MongoDB. And my initial intuition was the same as you outlined, is that MongoDB's success over the last many years since the company was founded in 2007 was that builders or developers love MongoDB. And if that's the premise, there was a lot of work done in the product to ensure that it's a very natural way, flexible way while keeping the business agile as in the database agile so that it can move with the business. We want to do the exactly same thing for agents. Agents also need to love MongoDB. That requires to ensure that we have all the right integration with the right places, whether it's NCP or whether we are looking at making sure that our APIs in how you manage how we auto scale, how we auto perform during the peaks and valleys. All of that truly needs to be autonomous and driven by machines. And that requires absolutely the focus from the engineering team that how would machines look at this if they want to provision an additional node or if they want to manage cluster because of resiliency across multiple clouds. So that will be the North Star for us that our agents will love MongoDB as much as today, human developers love MongoDB.

Okay. Great. And then just one quick follow-up on that. Just is that -- is that going to come in a future release of the database? Or how should we be thinking about sort of the deliverables on that vision, CJ?

Jason, we do have ambitious road map, of course. Today, we are already leveraged by some of the AI-native companies and some of them I outlined this time and also last time. And we are learning a lot from them. So we have ambitious road map in terms of truly machine friendly APIs or making sure that our protocol integration across a variety of protocols that machines demand and how do we Auto Scale, Auto Shard. All of that will be throughout this coming year. And what we are going to do is that our dot local conferences throughout this year, we will use that as an opportunity to announce new innovations that will show you that machines should also love MongoDB. So it will be throughout this year.

Our next question comes from the line of Ryan MacWilliams of Wells Fargo.

CJ, great to hear about Anthropic as a customer at the MDB local event. I'd love to hear how you think about the opportunity for Mongo to grow within large AI natives from here. And there's also mention at the event that Agentic workflows require heavier storage and memory requirements. Would love to hear why you think MDB architecturally is best suited for these growing types of AI use cases.

Absolutely. Ryan, one of the things I would say is Mike and I look at the entire cohort, AI natives, frontier model companies, others, many of them choose MongoDB for performance, scale, security and other things. And I would say that the good news here from my standpoint is that we are not concentrated in any one customer when it comes to AI native cohort. So that's number one. And as they scale, we will scale with them, but we are not concentrated. Even when I look at the growth as a percent of total, we were not concentrated. The thing that I'm seeing, Ryan, very specifically is that People are making initially database decisions in this AI native companies without realizing that they will run into scale issues or potentially there was one of the choices that people could have gone with as an AI native companies founders had a massive security concern over the weekend where a couple of governments blocked them from being used. So what I find is that truly enterprise-class database that can scale. And when I say scale specifically, as for these AI native companies as their weekly active users or monthly active users continue to grow, like the example we had with Emergent or 11 labs and so on, they find that MongoDB scales better with them, right performance as well as query performance really matters, and us being a native JSON with search vector search and embeddings in one rather than multiple moving pieces -- if I have to just simplify that, that is the strength because it's an integrated platform that scales both for read and rights that as you scale your AI native company, they can rely that MongoDB will scale with them.

Excellent. And then a follow-up for Mike. The Atlas seasonality in the fourth quarter seemed a bit lighter than typical. Were there any holiday impacts to the fourth quarter for Atlas revenue or any other onetime items in the quarter besides the Atlas and EA bundling?

Yes. Thanks, Ryan. So looking back at Q4, the holiday seasonality played out largely as we expected. There were really no surprises or deviation from the historical trends. So it largely played out as we expected.

Our next question comes from the line of Karl Keirstead of UBS.

Mike, let's stick to Atlas in the fourth quarter. A couple of questions. One was the 2-point beat roughly the framework you would advise the Street to think about going forward? And then secondly, if you could just perhaps describe the bundling impact that, as you said, nicked a point off of Atlas. Just maybe you could explain why that happened and were you anticipating that?

Sure. So all right, let's take a step back, Karl, on Atlas. So Q4 played out largely as we expected, as Ryan's question was, there were really no big surprises during the holiday season. We feel good about Q4 with 29% growth again with the bundled thing. I'll talk about that in a second, would have been a little bit higher. As Atlas has gotten bigger, we are seeing less variability in the business. And in addition, we're getting better every day at forecasting the Atlas business. So from that perspective, the size as well as customer cohorts don't make as much of a difference in variability has helped. So on the bundling thing, so entering Q4, we certainly have our forecast as it relates to how we think Atlas will do. There's -- we always do bundled deals in a quarter, absolutely. This was a little unique in that we had one large transaction that once it closed, and thank goodness again, it's a really good thing that it did, we had to attribute more of that revenue to EA versus Atlas, and that took a little bit off the growth rate. We did not expect that entering the quarter. So we typically won't walk through those kind of details because we always do bundled deals. This was an exceptionally large transaction, Karl, that did move the needle.

Okay. That's helpful. Yes. And then maybe, Mike, as a quick follow-up. You reiterated the medium-term guidance that you gave at the Investor Day. Maybe I missed it. I didn't hear the reiteration of the high teens total revenue growth. Is that still on the table, just to be crystal clear.

Thank you for asking the question. Yes, we have not backed off on that total revenue growth from September. Sorry, we missed it.

Our next question comes from the line of Ittai Kidron of Oppenheimer.

Michael, I want to follow up on the last questions here mainly around EA. Clearly, you had a very strong fourth quarter here with 2 very large deals and also the bundle that you mentioned that weighed a little bit more towards EA rather than Atlas. I guess I'm trying to think about your guidance for fiscal '27. It seems like you have a lot of momentum there. You're closing some feature gaps. I'm kind of wondering why low mid is still the target for '27, why we hold this momentum in the fourth quarter and in the bundling and the feature parity you hope to achieve, that number is not higher.

So thank you for the question. So we did have a very strong year in EA and Q4 especially. As we look out to the rest of the year, keep in mind that the product enhancements and bringing EA to parity with Atlas will occur throughout fiscal '27. So we are excited about that. And there was an earlier question about the cohorts. Keep in mind, it is a large business. There's a lot of moving parts here. The biggest variability to the business is not the cohorts, it's what ends up closing as a multiyear deal versus a 1-year deal. That still is difficult to forecast. And as we have said repeatedly, and we'll continue to say it. We will always bake in more upsides than downsides in that number. We sure hope to do better than that, but we don't want a negative surprise because a deal does not close on a multiyear basis, and that has such a big swing factor. So we feel great about the business. We're going to continue, as CJ talked about, a lot of big customers are asking about it. It's a key part of our portfolio, and we certainly hope to do better.

Fair enough. And then maybe as a follow-up, just for both of you with the changes in the leadership on the go-to-market side and the CRO and the field, I guess to you, Mike, a, is there any more level of conservatism built in your guide because of this transition? And b, to you CJ year-end, any changes to count structure that you're thinking about also in light of who you're looking for as far as the CRO is concerned?

Yes. So I'll answer it first. So when we do guidance, we obviously take into account a lot of things. The economy all kinds of different things. So we have tried to bake everything in. It's certainly -- while it adds a level of uncertainty, I want to underline what CJ said in his prepared remarks. We've been working on this for a while. We feel very good about the team that's in place, and we don't expect any material disruptions. But certainly, that is a factor that we took into account when we did guidance.

And Ittai, what I would tell you is that personally, after joining MongoDB, I have spent disproportionate amount of my time with our go-to-market teams to really understand what is working really well and of course, where we can improve. And I would say that the bench we have -- so our leaders for Americas, our leaders for Europe, Middle East and Africa as well as our leader for now APJ, I have very high confidence in them as we go through this transition. And these are the folks that really, really executed very well in fiscal '26 when you look at the regional performance, and I am really optimistic about their ability to execute as we move forward. In terms of overall go-to-market, how sellers are motivated, what we are looking for in the candidate to work on the main street with all these sellers and serve our customers, what I said to Matt, is just remains the same, that no changes. We want disruption to be minimum. And with these 3 theater leads who exceeded even that number in Q4 greatly from a net new business perspective, I have confidence in them.

Our next question comes from the line of Alex Zukin of Wolfe Search.

CJ, maybe first for you, given some of the increasing inflection points that we're seeing in kind of the agentic coding space and autonomous coding that's happening. Has that, in any way, changed the dynamic of how fast or how quickly you think that the enterprise modernization could start occurring? And then maybe just a quick follow-up for Mike. To the point about the increased -- maybe some of the surprising bundling, particularly with a large deal in the quarter, is there maybe a little bit less visibility on specifically the Atlas guide for both Q1 and the full year, given that increased potential for variability around bundling.

Yes. So Alex, I'll touch on the first one. I -- what I would like to say, so I was talking to a large financial institution in the U.K. And the Head of Transformation, she told me that, hey, CJ, I have 50% of my real estate that I want to modernize, I know that some of the AI tools can get me to some level, but I really, really need your help and your team's help to make sure that for these mission-critical applications, we take help from MongoDB to help us land once you prove this out for the first workload, a very critical workload that is moving to MongoDB. The same thing happened, Alex, with a large customer in Spain when I was there a couple of weeks ago, this individual said, "Hey, we are relying on MongoDB, as we are modernizing. This is extremely critical workload, once you do that, we are going to open up the aperture and I know that AI will help us modernize, but we still need your help because the destination we want is absolutely MongoDB. So what I'm seeing is the feedback is the modernization and the need for modernization is still very much relevant in the high end of the enterprise, whether it's a health care company, financial services or even government for that matter or health care. Number two, they know that AI tools can help you to some extent, but they definitely want to get there on a modern database to get AI ready where they want help from MongoDB to be on MongoDB. And then the last thing I would say is that even with some of the use cases, they try it and they're like, hey, sometimes this is too hard to assure the reliability, security and all of those things for the application we build. So I consider this as an opportunity in early stages, and this is definitely a top-down work that we have to do as MongoDB with the CTOs and Head of Transformation, but the opportunity still exists and it's massive.

Alex, thanks for the question. It's something that we will certainly watch. What I'll reiterate is we always do bundled deals. It's part of what we do. Q4 was unique given the size of that, I'd love to sit here and tell you that there's a whole bunch of those that we'll do every year. I do think right now it's unique, we'll watch it. We get better and better at forecasting the Atlas number every quarter. So at this point, we don't think it adds variability, but it's something we'll watch going forward.

Operator, we'll take 2 more questions.

And our next question comes from the line of Tyler Radke.

Just going back to the EA and Atlas bundling. I guess I'm wondering, were these existing workloads that moved from Atlas to EA? Or was this sort of plans for new workloads? Just a higher bias on EA. And just curious like why do you think that customer, in particular, chose to do more on EA as opposed to Atlas?

So it's always going to be customer-specific, Tyler. And a lot of these transactions will have renewal as well as upsell also. So it's very specific to the customer, and it really depends on their internal plans as it relates to how they want to use MongoDB going forward. So there's no pattern there. It's very specific.

Yes. And Tyler, what I would say is that with this specific customer is that they have, in the past, moved some of their EA workloads to Atlas. Some of their Atlas workloads are growing incredibly well, and they want to continue to do that. And they are currently also getting ready for some of their workloads, AI-ready where they are using vector search and embeddings in the future. So it is a kind of classic case of truly hybrid infrastructure on how they are dealing with their core product strategy and some is built on EA and some is on Atlas. And from my standpoint, when we look at the numbers and the transaction, which was meaningful, as Mike said, very meaningful, is that what we also saw was the expansion because this customer besides making a long-term commitment continues to grow their data estate with MongoDB.

Great. And CJ, a follow-up on the go-to-market changes. Clearly, your background at ServiceNow has one of the more successful partner ecosystems out there. I think on the on the database side, particularly for Mongo, the partner ecosystem, I think, has been tried, but certainly it's not nearly as robust. And given that being more of a focus on some of the new go-to-market leaders bringing in, can you just help us understand maybe some of the challenges with the prior approach that didn't lead out to as robust of a partner ecosystem and what makes you and gives you the confidence that this approach is going to be successful?

Yes. Tyler, absolutely, and I have been told what he just outlined. So I would put this in 3 buckets, Tyler. First bucket, which is super important is our hyperscaler relationship and how we work with them. And as you know, that we work with them very closely because when we win, they win, whether we are running on GCP or AWS or Azure or others, okay? So one bucket is just continue to still stay focused on hyperscaler. And in today's world, the multi-cloud resiliency, whether it's on-prem and cloud or between multiple public cloud, which is an advantage we have, it is proving out more and more important between the outages that happened last year with some of the hyperscalers and the geopolitical issues that we are seeing being played out. So that's number one. Number two, system integrators, which is where we scale at my previous company, that is definitely -- when you think about the modernization and the real estate on modernization to move to MongoDB, we could definitely benefit by focusing on 2 or 3 of them to start with, and that is something that our teams are saying, we do need help as we think about this 2 or 3 system integrators. And make no mistake, the third bucket is also equally important is this AI native ecosystem that are framework providers. There are other providers like LLM providers, and what can we do with them and truly create partnerships that really matter. Those are the 3 buckets. And that will allow us to scale for a long time. So hyperscalers, a few system integrators who wants to lean in on the modernization and the AI ecosystem where we really need to make strong technology friends is how I look about it, and I think it is extremely essential to do that on -- and this is the inflection point.

And our last question comes from the line of Sanjit Singh of Morgan Stanley.

So CJ, I wanted to just get your latest thoughts on a couple of topics. Given that the business has been accelerating, execution has been improving in the past several quarters. As we look forward, do we start to see like the kind of AI part of the story start to play a bigger role in terms of the growth equation you guys have a number of AI customers as sort of we discussed on this call. But in terms of contributing growth, does that become more important as we think about potential upside to this guidance that you laid out? Kind of feel like over the last couple of weeks, we've seen a step-up in terms of agentive momentum, not necessarily in the enterprise, still feel kind of consumer personal productivity. But just wanted to check your thoughts on the importance of the AI app story coming to fruition maybe a little bit earlier than maybe you anticipated?

Yes. I would tell you it's not if but when, okay? So right now, we do consider, I mean, Sanjit, one of the advantages that I have in speaking to all these customers, I ask them that simple question, where are you on your Agentic workloads? And I'm talking about Fortune 500, okay, or big retail companies, health care companies pick one and ask them -- where are you on agentic workloads? And are they really scaling? And the answer is still not yet. Yes, they have done a few productive productivity types of apps internally, but nothing of scale that is customer-facing, even including with a large retailer on agentic commerce and so on. So my first thing is, one day, it is going to hit in a positive way where you will have agents making a meaningful difference to the growth of our customers for either new product lines or existing product lines. We are not seeing that today in the large enterprises across pretty much most of the verticals that we speak to because as you know, MongoDB is across every vertical. So my simple answer is it will be someday, not seeing that yet and don't want to predict it because it was supposed to be the 2025 was supposed to be that year. And what we saw in 2025, it was only mainly around coding and some vertical-specific AI, but nothing meaningful in the enterprises. Mike, would you?

And just as a follow-up, and maybe Mike, you can hit on this. It sounds like Atlas consumption more or less came in line with your expectations, controlling for this large deal. You mentioned this potentially lower visibility in the second half. And I wanted to assess that comment in context of how the sort of calendar year '25, fiscal year '26 applications and workloads, how are they ramping relative to your expectations? Maybe the -- if you look at the first half of last year and those applications ramping into this year, are you satisfied with the quality of that growth in that cohort of application?

Yes. Thanks for the question. So I think a couple of questions in there. One is, yes, Q4 largely came in as we expected, except for that small thing that we talked about. It was -- there were really no abnormal things in Q4, which is great. On the comment about the second half, that's just more of a general macro comment, Sanjit, and that it is a consumption business. While we -- visibility is always a little bit better earlier. We're also cognizant of, hey, it's harder to forecast the back half of the year. That does not tie directly to any concern around the workloads that we've signed in the last couple of years. And yes, those continue to perform as expected. As we've talked about strength that we've seen is really in the larger customers, especially in the U.S. and Europe. So all that is going as expected. That second half was more of a general comment, not specific to any set of workloads that were signed in the past.

This concludes the question-and-answer session. I'd like to turn it back to management for closing remarks.

Thank you, operator. In summary, we delivered an exceptional fourth quarter, highlighted by strong Atlas and non-Atlas growth, robust customer additions and operating margin outperformance. We are issuing strong guidance for Q1 and full year fiscal '27 across Atlas and non-Atlas revenue, and we expect to continue expanding profitability while investing for growth all in line with our long-term financial model. Our results demonstrate MongoDB's foundation is in great shape, and the company is well on its way to become the generational data platform of choice in the AI and multi-cloud era. Thank you very much for everyone joining, and we'll see you soon.

Thank you for your participation in today's conference. This does conclude the program. You may now disconnect.