Hi, everyone. Welcome to the Confluent Q1`` 2 023 earnings conference call. I'm Shane Xie from Investor Relations. I'm joined by Jay Kreps, Co-founder and CEO, and Steffan Tomlinson, CFO. During today's call, management will make forward-looking statements regarding our business, operations, financial performance, and future prospects, including statements regarding our financial guidance for the fiscal second quarter of 2023 and fiscal year 2023. These forward-looking statements are subject to risks and uncertainties, which could cause actual results to differ materially from those anticipated by these statements. Further information on risk factors that could cause actual results to differ is included in our most recent Form 10-K filed with the SEC. We assume no obligation to update these statements after today's call except as required by law. Unless stated otherwise, certain financial measures used on today's call are expressed on a non-GAAP basis, and all comparisons are made on a year-over-year basis. We use these non-GAAP financial measures internally to facilitate analysis of our financial and business trends and for internal planning and forecasting purposes. These non-GAAP financial measures have limitations and should not be considered in isolation from or as a substitute for financial information prepared in accordance with GAAP. A reconciliation between these GAAP and non-GAAP financial measures is included in our earnings press release and supplemental financials, which can be found on our investor relations website at investors.confluent.io. Please also note that we will host Investor Day 2023 in New York City on Tuesday, June 13. To join in person, please contact IR for the registration information. The program will also be webcast live on our IR website beginning at 1:00 P.M. Eastern Time. With that, I'll hand the call over to Jay. Thanks, Shane. Good afternoon, everyone. Welcome to our first quarter earnings call. I'm pleased to report a strong first quarter with results once again exceeding all of our guided metrics. Total revenue grew 38% to $174 million. Confluent Cloud revenue grew 89% to $74 million. non-GAAP operating margin improved 18 percentage points. These results are a testament to the mission-critical nature of our platform, our strong TCO value proposition, and the solid execution of our team despite a volatile macroeconomic environment. Over the last year, Confluent has continued to show very strong gross retention, even through a substantial change in the economic environment, including abrupt changes in interest rates and economic slowdown, significant drop in funding for private tech companies, and the recent challenges in banking. Environments like this show which products have true durability and which are simply fads or nice to have. I wanted to take the opportunity to explore what drives this durability for Confluent. The first factor is that Confluent serves mission-critical custom software applications. These are high-value projects that customers invest their expensive software engineering resources in. Because of this high investment, the applications tend to target the most valuable use cases and last a long time. We often hear from customers about applications lasting not just years, but decades. Naturally, the underlying data platforms used by these applications tend to persist along with them. The second factor is that unlike a database, Confluent isn't just a platform for one app, but acts as an interchange between multiple teams and applications. This is inherent in the core use case of the technology, publishing streams of data so multiple other applications and teams can consume those streams. This kind of multi-team, multi-application platform gets more and more sticky as it gets more heavily used and displays very different dynamics than a platform that each application can choose or abandon independently. The reason for this is very obvious. The migration to another platform would require a coordinated effort across many teams all at once, which becomes harder and harder to imagine as there are more and more producers and consumers building against the streams of data in the platform. By analogy, think of the cost of switching to a new incompatible telephone system. The challenge isn't buying a new phone, it's getting all your friends to do the same thing at the same time so you can still call them. This pattern of cross-team interaction and cross-application interaction is a unique and positive characteristic of data streaming and isn't shared by most other data systems. The third factor of our durability comes from the inherent TCO advantage of our cloud offering. I'm gonna dive into this factor at length as it's critical to understanding the deep technical moat that Confluent has built. Initially, it might seem that a customer when faced with budgetary pressure would want to migrate off the cloud data service back to open source. Open source, after all, is free. Why isn't this happening? It is no doubt in part due to the comprehensive features and functionality our platform offers. We've talked about this at length in prior earnings calls. You would imagine that customers might choose to forego better functionality when faced with severe budget pressure. Why isn't this happening? The answer to this may be somewhat counterintuitive. The cloud data service has the opportunity to not just be better than an open-source offering, but also be meaningfully cheaper. To understand this, it's important to understand what drives the cost structure of self-managed data systems. This is an analysis we do frequently since we offer both a self-managed software offering and a cloud service. We've worked with thousands of customers, both on-premises and in the cloud, to analyze and compare the cost structure of open source self-managed software and a fully managed cloud service. I'll walk through this analysis and show where our substantial TCO advantage comes from. There are two easily quantifiable areas of spend around a self-managed software system. The first is the cloud infrastructure for running Kafka. This spans compute, storage, networking, and any additional tooling needed to keep Kafka up and running smoothly. These costs tend to increase rapidly, eventually representing the largest portion of cost when usage is at scale. The second is the software engineers and operations people responsible for configuring, deploying, and managing Kafka. Like any data system, and particularly like any large scale distributed data system, Kafka requires full-time staff to manage it. The cost of these individuals is significant, particularly for people managing Kafka. A 2022 study from Dice.com listed Kafka as the 5th highest paying technical skill. That's great for engineers doing Kafka DevOps, but not so great for companies hiring teams with the experience to operate Kafka as a production data system. These costs will scale up with the usage of the system. The larger tech companies that have built significant streaming platforms around open source Kafka have teams of 20 or more engineers attending to their data streaming platform. It's not inevitable that a cloud service will improve on these costs. After all, if we were running the same open source software and operating in the same way, our costs would be no different from theirs. However, Confluent has rethought the problem from the ground up and has built a deeply differentiated stack that's able to drive compelling savings in both of these areas. I'll start with infrastructure savings. Confluent's Cloud has rethought and reimplemented the core protocols for data streaming in a way that is built natively for the cloud to drive significant savings. I'll enumerate a few of these. First, multi-tenancy. Multi-tenancy is the key to SaaS margins, but many investors don't realize that the majority of data systems in the cloud, especially services offered by the cloud providers around open source, aren't actually capable of multi-tenant operations. Our offering runs multi-tenant for the vast majority of customers. This is a very significant re-architecture, touching virtually every tier of the stack, allowing us to pool our thousands of customers on shared infrastructure to drive higher utilization and a serverless experience. Next is elasticity. Our intelligent tiering of data between memory, local storage, and object storage helps manage the costs of stored data and allows instant scalability, enabling higher utilization of compute resources. Next is our facilities for sophisticated data balancing. Confluent uses the real-time performance data of our customer base to intelligently optimize the placement of data and the routing of traffic to maximize performance, utilization, and cost. Finally, networking and data replication. Confluent has optimized the replication of data in the networking stack, routing data to drive the cost of networking, the most expensive aspect of cloud operations for streaming. In addition to this, at-scale discounts targeting our unique workload help reduce spend. Confluent is now at a larger scale than most of our customers, and we are able to drive discounts targeted to our workload. These significant architectural advantages, combined with thousands of small continual optimizations at every layer of the stack, help drive our significant cost advantage in operations. Those who have watched our gross margins progress over the last few years have observed this continual progress at work as we have continually driven additional technical improvements and improved utilization from multi-tenant operations as cloud has become a bigger and bigger portion of our revenue base. Next, I want to discuss the advantage that comes from our innovations in at-scale operations. Confluent operates our fleet with a set of tools and practices vastly different from our customers. First, our infrastructure improvements do double duty here. The improvements I outlined previously drive vastly higher utilization, and hence we manage an order of magnitude fewer servers than we otherwise would. The big difference in our operations is that it is done by software, not people. We orchestrate rollouts with a sophisticated feedback-driven system that allows safe rollouts across 1,000s of machines and hours. We are able to automatically detect and remediate the kinds of rare problems that become common at scale, and we have real-time monitoring and checks for every aspect of the integrity of the system. These capabilities provide us with a dramatic advantage in the cost of human management. For example, in our Kafka service, the centerpiece of our offering, Confluent has less than 5 Kafka engineers on call for our 10,000s of production Kafka clusters. This gives us a cost structure for operations that we believe is over 1,000 times better than our customers. The combination of these savings across infrastructure and operations allows us to offer our service at a price point that makes our product not just better, but also cheaper. We think that's a winning combination, especially in times like these. We've gone to great lengths to ensure we are TCO positive across the customer journey, from their first use case to large scale central nervous system. We believe this TCO advantage is not just a factor in driving retention. It will also help us drive far greater monetization of the user base of open source Kafka. This is a point often missed by investors looking to make analogies from on-premises open source models to the cloud, which in fact are quite different. Traditional on-premise open source business models offer a premium product, better features for more money. As a result, they typically are able to capture only a fraction of the open source users as paying customers. A cloud product, however, isn't just replacing the free software. It's also replacing the expensive infrastructure and people costs. This is driving a general mindset shift among software engineers and IT departments who are increasingly looking for managed services first, trying to avoid ongoing operations wherever possible. As this shift takes place, we think there is an opportunity to grow from our modest penetration into the hundreds of thousands of open source Kafka users to a much more complete coverage. This higher conversion rate is already apparent. Despite being a much newer offering and despite the much higher bar of maturity for a cloud service, today Confluent Cloud is already used by more than six times as many customers as Confluent Platform, our self-managed software offering. In fact, we are so confident in this value proposition that we invite prospects to come and take an assessment where we jointly do analysis with them to prove to them that choosing Confluent will be a more economical decision than self-supporting open source Kafka on their own. A great example of the TCO benefits of Confluent for a customer in the earlier stages of the customer journey is a SaaS-based billing startup that helps companies scale their consumption, subscription, and hybrid pricing models. This customer's data and billing platform is built on Kafka to compute usage and invoices in real time for millions of end customers and is scaling rapidly to accommodate expected growth. They quickly found that managing open source Kafka was costly and diverted expensive engineering talent from innovation to low-level infrastructure management. With Confluent Cloud, they are able to reallocate at least 60% of their engineers' time managing Kafka to delivering new product innovation without over-provisioning infrastructure. As a result, they've reduced deployment times from months to weeks, while reducing the total cost of managing open source Kafka. On the other end of the spectrum is a large Q1 deal with a top 10 U.S. bank. Confluent powers thousands of this customer's applications across hundreds of teams, spanning digital, fraud, payments, analytics and more. The bank is now going all in on the cloud, undertaking a massive cloud migration to operate more efficiently and introduce new innovation to their customers faster. To accelerate their cloud migration, they closed a seven-figure Confluent Cloud deal to connect their data from on-premise environments to the cloud. Despite the turmoil in the banking industry, this customer accelerated their cloud transformation with Confluent. Another example of the many use cases that make data streaming a critical tool for modern organizations, even amid macro uncertainty. We are very excited about the opportunity for similar expansion in other customers as the financial services sector moves to the cloud. In closing, the significant product and cost advantages of our platform put us in a strong position to tap into the hundreds of thousands of users of Kafka with a product that is more than 10 times better and meaningfully cheaper than open source. These dynamics put us in the enviable position as the leader of a $60 billion market opportunity. I look forward to seeing many of you at our investor day, where, among other things, we'll dive deeper into the significant product innovation driving the success of our platform. With that, I'll turn the call over to Steffan to walk through the financials. Thanks, Jay. We kicked off fiscal year 2023 beating our guided metrics, delivering high revenue growth and strong margin improvements in the first quarter. These results demonstrate another quarter of consistent execution from our team in a tougher economic environment. Turning to the results, RPO for the first quarter was $742.6 million, up 35%. Current RPO, estimated to be 64% of RPO, was $477 million, up 44% and accelerated from last quarter. Growth in RPO, while healthy, was impacted by a decline in average contract duration, additional budget scrutiny, which elongated our deal cycle, and a tough comp against the eight-figure TCV deal closed a year ago. Moving on to NRR. Starting this fiscal year, we moved to consumption-based NRR for Confluent Cloud, which provides better alignment and insight to the underlying consumption trends of our cloud business. Total NRR for Q1 was above 130% and gross retention was above 90%. NRR for both cloud and hybrid customers remained higher than the company average, and NRR for cloud was the highest. We added 160 net new customers, ending the quarter with approximately 4,690 total customers, up 14%. The growth in our large customer base continued to be robust, driven by use case expansion. We added 60 customers with $100K or more in ARR, bringing the total to 1,075 customers, up 34%. These large customers contributed more than 85% of total revenue in the quarter. We also added 8 customers with $1 million or more in ARR, bringing the total to 135 customers, up 53%. We've included historical results for NRR and customer count relating to the ARR methodology change in our IR presentation on our website. Turning to the P&L. Total revenue grew 38% to $174.3 million. Subscription revenue grew 41% to $160.6 million and accounted for 92% of total revenue. Within subscription, Confluent Platform revenue grew 16% to $86.9 million and accounted for 50% of total revenue. Confluent Platform outperformed relative to our expectations and was driven by a strong performance in the public sector vertical. Confluent Cloud exceeded 50% of total new ACV bookings for the sixth consecutive quarter. Cloud revenue grew 89% to $73.6 million, representing a sequential increase of $5.3 million, exceeding our guidance. Cloud accounted for 42% of total revenue, compared to 41% last quarter. The modest increase in cloud revenue mix relative to historical trends was due to the outperformance in Confluent Platform in the quarter. Turning to the geographic mix of revenue. Revenue from the U.S. grew 32% to $103.9 million. Revenue from outside the U.S. grew 49% to $70.4 million. Moving on to the rest of the income statement, I'll be referring to non-GAAP results unless stated otherwise. Total gross margin was 72.2%, up 250 basis points and modestly above our target range of 70%-72%. Subscription gross margin was 77.5%, up 200 basis points. Our healthy gross margins were driven by the continued improvement in the unit economics and scaling of our cloud offering, offset by a continued revenue mix shift to cloud. Turning to profitability and cash flow. Operating margin improved 18 percentage points to negative 23.1%, representing our third consecutive quarter of more than 10 points in improvement. Q1 operating margin was driven by our revenue outperformance, which we let flow through to the bottom line and our continued focus on driving efficiency across the company. We drove improvement in every category of our operating expenses, with the most pronounced progress made again in sales and marketing, improving 11 percentage points. Net loss per share was negative $0.09, using 291.9 million basic and diluted weighted average shares outstanding. Fully diluted share count under the treasury stock method was approximately $350.1 million. Free cash flow margin declined 1 percentage point to negative 47.5%. As expected and discussed on our last earnings call, free cash flow in Q1 was negatively impacted by charges related to our restructuring, the Immerok acquisition, ESPP, and our corporate bonus payout. We ended the fourth quarter with $1.85 billion in cash equivalents, and marketable securities. I'll turn to our outlook. The demand environment for data streaming and the solutions we're offering to the market continues to be robust, even in a choppy macro environment where it's taking longer to close deals. Mid last year, we were early to flag the increase in the volatility of the business environment and incorporate those dynamics into our outlook. Looking out to Q2 and the balance of the year, we're expecting to deliver on the commitments we outlined on our last call. We are assuming there's a continuation of additional budget scrutiny, and there will be no improvement in the business environment through the remainder of this year. We'll continue to proactively allocate capital to drive efficient growth and are managing the rate and pace of investments. For the 2nd quarter of 2023, we expect revenue to be in the range of $181 million-$183 million, representing growth of 30%-31%. Cloud sequential revenue add to be in the range of $7.5 million-$8 million. We continue to expect cloud sequential revenue add to increase every quarter for the rest of 2023. Non-GAAP operating margin to be approximately -16% and non-GAAP net loss per share to be in the range of negative $0.08 to - $0.06, using approximately 297 million weighted average shares outstanding. For the full year 2023, we expect revenue to be in the range of $760 million-$765 million, representing growth of 30%-31%. Non-GAAP operating margin to be approximately negative 14% to - 13%, and non-GAAP net loss per share in the range of - $0.20 to - $0.14, using approximately 300 million weighted average shares outstanding. Additionally, for Q4 2023, we expect to deliver 48%-50% of total revenue from cloud and achieve break even for non-GAAP operating margin. The timing for free cash flow break even will roughly mirror that of our operating margin. In closing, I'm pleased with the strong start to fiscal year 2023. While the macroeconomic environment remains challenging, we're continuing to deliver innovation and value to our customers, which would not be possible without the excellent performance of the members of our team. Looking forward, we remain focused on driving efficient growth and building a profitable business. Now Jay and I will take your questions. Thanks, Steffan. To join the Q&A, please raise your hand on Zoom. When you're selected, make sure to unmute and turn on your video. We'll now pause a few seconds to assemble the Q&A roster. Today our first question will come from Sanjit Singh with Morgan Stanley, followed by Wells Fargo. Sanjit, please go ahead. Thank you for taking the questions. Congrats on the very solid results in what is a pretty difficult environment out there. To that point, Steffan, I was wondering if you'd just give us some color on how the quarter progressed, particularly post Silicon Valley. What trends did you see in terms of booking trends, you know, customer engagement, and what's been sort of the early reads April going into May? On the booking trends throughout the quarter, we saw a typical linear-linearity pattern that we would see in most Q1s. January started off as typical, which is usually a little bit slow, and then it ramped up from a booking standpoint, and we had a good strong month three. From a consumption basis, we did see a little bit of an impact relative to some of the consumption trends in our cloud business in the second half of March. You know, and we saw that manifest itself in the financial vertical. What we did see though in April is a nice bounce back. We saw a return to normal patterns for the consumption business in the financial vertical. Jay, I don't know if you have other things you'd like to add on to that. I think that was a good summary. Yeah. You know, broadly, the results were not too surprising, even though I think, you know, in some customers, both in tech and in financial services, there was a fair amount going on in the organizations. Yeah, I appreciate that. It makes a lot of sense and encouraging, you know, to hear about the trends, you know, post-March, on the consumption side of financial services. Jay, you did a fantastic job of sort of, you know, explaining the value proposition of Confluent Cloud and the TCO advantages that Confluent is bringing to bear the market. I guess the other side of the coin in terms of what we're trying to better understand is the impact of generative AI. If you're thinking about the classes of applications and the interfaces of those applications, what do you think is the impact on real-time streaming? Is that a forced accelerator for the category in terms of the apps, or is that a potential headwind? Yeah. It's absolutely an accelerator. I mean, it's early in terms of production deployments, as you would expect, but already we have, you know, customers that are doing this for real. You know, including a large travel company that's, you know, building real-time context data and using that to power chat interfaces for their customers. I expect that to be a pattern that is more common. You know, generally speaking, when there's a new major area that data may need to go towards, that's a powerful thing for Confluent. You know, the more new things, the better for us. I know in some areas it's actually a bit of a disruptive force, but for us, this is actually a powerful thing. You know, our role in that architecture is kinda, you know, helping customers assemble that real-time context data that would go into, you know, asking the right questions, powering the right queries, you know, getting the right context into the interface. You know, that's where we fit into that architecture. Of course, you know, the same as any enterprise company, there's a lot of interesting use cases internally. You know, we have a number of organizations, whether that's support, engineering, legal, where, you know, there's a significant amount of work that is basically text in and text out, that, you know, all of those teams could potentially be made more productive, you know, kind of up their game, as a result as some of these tools come into practice. If I could just clarify and get your feedback on this sort of logic. When we're interacting with these question and answer type interfaces, right? Is the simple point that we need up-to-date data and that you guys are gonna be able to provide that. I mean, to the extent that we're dealing with the public ChatGPT, we're dealing with outdated data, right? Potentially data at rest in other use cases. Is what Confluent going to do is bring that data sort of up to date so we're getting the most up-to-date answers to our questions? Yeah, that's right. you know, the architecture for these is both, you know, some amount of training that's usually done entirely by the centralized company, say an OpenAI's case, you know, followed by maybe some amount of pre-training on data specific to that customer. Then most importantly, assembling the right information about the particular customer at the time of the question, right? That last bit is the part where we're most relevant, and that's actually quite important. Just fitting this into, you know, a business that serves particular customers in particular ways that would have particular context about them that has to be incorporated in any response. I appreciate the thoughts, Jay. Thank you very much. All right. Thanks, Sanjit. We'll take our next question from Michael Turrin with Wells Fargo, followed by Piper Sandler. Hey there. Good afternoon. Appreciate you taking the question. Nice job on the Q1 results. Steffan mentioned the ARR restatement. It looks like it's tied to consumption. Maybe just help level set where those changes show up? On NRR, it looks like using the old method, that number did continue to come down a touch. Maybe walk through what you're seeing there and what you're assuming on the expansion side for the rest of the year. The NRR change really impacts our cloud business. Prior to making the change, we had a commit-based NRR calculation, which didn't really capture the underlying momentum of our cloud business. With the consumption change to the NRR calculation, we're now capturing really the consumption-based strength of our business. It's better reflective of the actual underlying growth drivers, and it's also very consistent with what our peer group companies are doing that have a consumption-based model. Think of MongoDB, Datadog, Snowflake, they all have moved to a consumption-based NRR. Where it shows up is in our cloud business and then also in our hybrid customer NRR cohort, because those hybrid customers are running both Confluent Platform and Confluent Cloud. Confluent Platform will continue to be on the older methodology, which is the committed contract basis. For the portion of their business that is Confluent Cloud, we'll calculate it using the commit basis. As far as the older methodology, we did come in just slightly below the 125% metric that we established as a goal for total NRR. What we saw in the underlying drivers, the gross retention of our business continues to be very strong, above 90%. Considering the current macro environment, we just saw less expansion driving that was driving through the committed contract part of the business. What we did see, and what's better reflected in the new methodology is the consumption patterns of our customers are exceeding the committed contract spend. Those are some of the dynamics at play. Going forward, we will be reporting a consumption-based NRR metric, and that is, again, better reflective of the underlying performance of the business. That's super useful detail. If I can just follow on with just a quick point on what you're mentioning, Steffan. I think sometimes the visibility you have into cloud consumption patterns is maybe underappreciated. The commentary is consistent around sequential improvement on the cloud side throughout the course of the year. Just any color you can provide around what visibility you have and what provides confidence in that progression continuing? We've taken great steps at organizing our business around a consumption-based approach, and that starts with our sales and go-to-market motion. Our sales folks have a consumption-based element to their quota. We've been a cloud first company in terms of development cycles, and then we've done a lot of instrumentation around systems and process around forecasting. As we look through the balance of the year, what we said at the beginning of the year still holds up. We see net sequential revenue add for Confluent Cloud each quarter throughout the balance of the year, even in a tougher macro environment. We feel really good about our ability to drive roughly about 48%-50% of total revenues coming from Confluent Cloud, exiting the year. That gives us the confidence to put that stake in the ground. Thank you very much. Appreciate it. Yep. Thanks, Michael. We'll take our next question from Rob Owens with Piper Sandler, followed by TD Cowen. Rob? Thanks, Shane. Thank you guys for taking my question. Good afternoon. Steffan, I know you just spoke to it to some degree, but you called out gross retention rates. You said they're above 90. Can you walk us back a couple years, you know, the last time we saw disruption around COVID, and talk about what the experience with retention was then versus now, and is this becoming a much stickier application at this point? It definitely is a much stickier application today than it was a couple years ago. A couple years ago, the product that we had in the marketplace was while it was good, it didn't necessarily have all of the mature feature functionality that we do today. The amount of innovation, our product and development organization has driven over the last couple years, there's a marked difference between our product today versus what it was two years ago. A couple years ago, the gross retention rates were lower. The net retention rates were lower. Now we have really healthy net retention rates, and gross retention rates due to the product maturity. Then also, if you layer into the equation the improvements we've made to our go-to-market organization, we have this customer growth go-to-market journey that we've socialized with the investment community. How we land customers is very important, and then how we develop them over time through the progression that they start with from paygo all the way up through a fully mature implementation of our solution. It just has become much more sticky. Because we're an infrastructure play, this is not something that can be easily ripped and replaced or downgraded to the open source version. There's a vast difference between our Confluent Cloud offering and anything that you could get in open source. In therein lies the big differential. Great. I guess taking the other side of that for Jay, maybe talk a little about customer acquisition right now and just what's convincing new customers to move in this environment. Yeah. I think it's a number of things. I mean, you know, it starts with the kind of mission-critical applications. I think those are the ones that tend to move forward in this environment. The second aspect is the TCO that I talked about, you know, and ultimately the feature set of the product. I think that combination of, you know, being attached to a project which is gonna be important enough to continue forward, retain its funding, even in organizations that are potentially cutting budget, trimming staff, et cetera, I think that's critical. I think, you know, bringing to bear something that is, you know, a better solution and a better deal, I think that's critical as well. Great. Thank you both. Thank you. Thanks, Rob. We'll take our next question from Derrick Wood with TD Cowen, followed by Guggenheim. Great. Thanks, and congrats on a strong Q1. Just picking up on that, Jay, I thought you did a really good job outlining the advantages of cloud and what you guys are doing versus on-prem. I wanted to talk about, there's a lot of Kafka DIY out there, ranging from very large cluster deployments from tens of thousands of companies in the long tail. Obviously you guys have some really compelling TCO and ROI figures. Is the macro a tipping point to drive more conversion? When you look at kind of the top end of the pyramid and the bottom end, are you focused on one end or the other more in this environment to drive more open source conversions? Yeah. I think it is ultimately helpful. You know, the initial impact of some downturn is not helpful, right? You know, customers are reprioritizing, people are being laid off, things are changing. That's not a helpful environment to do business in, and the additional scrutiny that we've talked about, you know, is exactly the factor. Over time, you know, I do think that there's a mindset shift that's happening in technology, where, you know, to some extent, the more tech-forward organizations were kind of copying a Google model from, you know, some decade ago, where you would build out these internal infrastructure platforms in-house and staff them up, and that was gonna be a kind of lever for success. I think the modern way is just to get a managed service, and that's ultimately better and more cost effective. I think that that mindset shift is really important and is an important tailwind for us. When I talked about that, hey, what is the penetration that's possible, you know, for a company into the open source user base, I think that's ultimately the big driver, right? It's both about us having good enough cost structure, having that TCO, making that true. You know, it's not inherently true of every cloud product, right? That's something we've done a ton of work to make true. Then it's about people really kind of internalizing that and understanding it and acting on it, which doesn't happen immediately, but is happening now. Yeah, when you talk about where on the journey are we focused, we do look at that full journey, right? It, you know, for us, because customers progress, you start with one use case that spreads, you know, to broader in the organization and becomes a big platform. It doesn't make sense to start at only one place. You know, if you did that, maybe you might focus at the beginning of the journey, but customers would, you know, as they got to large scale, you wouldn't have the features and functionality to really support them. They would migrate off, right? That wouldn't be good. You know, only focusing on the very largest customers and not getting the, you know, next 100,000 Kafka users who are just starting now, that wouldn't make sense either, right? It makes most sense to start with them as they go. The reality is, you know, both in terms of the TCO and the customer experience, you have to be good all along the way. That's why it's actually so hard for these cloud products. It's why it's not a trivial thing to do. You have to be, you know, very easy to use and a better deal for that first app, you know, one developer kicking the tires. You have to be something that can be deployed at scale and used across a large organization, you know, effectively, and has the right controls and governance of data, et cetera, as you get to scale. You know, I think that's why, you know, it's a deep area of investment to really do this well. You know, that's the journey we've been on. I think the cool thing about, where we're at with our cloud product right now is we have substantial, you know, customer usage at each spot along that. Indeed, we're kind of going out to the open source users and converting them over to this now, whatever stage on that journey they happen to be on right now. Great. Great color. Steffan, just wanted last quarter, you talked about kinda less urgency from buyers at the end of the quarter, and you had deals slip. Just wondering, did those slipped deals kinda close as expected? Did it feel like the that kinda headwind end of quarter dynamic that you saw in Q4 faded a little bit in Q1? 'cause it didn't seem like you had any big surprises, but just wanted to get a sense for how end of quarter compared sequentially. Majority of the deals that had slipped from Q4 did close in Q1, which was great. We still are seeing the same dynamic that we've been calling out for the last several quarters, candidly, where customers are taking more time to evaluate purchases. It's elongating deal cycles. We've been able to execute through that, and set guidance appropriately. We did see similar dynamics at the end of the quarter, and we're anticipating that that dynamic is gonna be factored throughout the balance of the year. That's really the dynamic at play. Thanks, guys. Appreciate it. Thanks, Derrick. We'll take our next question from Howard Ma with Guggenheim, followed by Barclays. Great. Thank you. Jay, dovetailing on some of your comments about TCO and the value prop of both platform features and fully managed, which I think it helps address an ongoing debate in the investment community about the mission criticality of Confluent and how susceptible Confluent is to, you know, optimizing both overall IT and cloud spending. Can you give some more specific examples from a vertical specific use case about, you know, expansion, both expansion and new use cases that give you confidence in achieving your targets this year? Yeah, absolutely. I mean, you know, you would see this across virtually every industry. You know, the one that we called out in the earnings was this large expansion in financial services. Yeah, that's an industry that obviously a lot is happening in. So the willingness to make, you know, big bets on this in the cloud, right? These are organizations that are very sensitive about security, about compliance, et cetera, really, you know, do a thorough job of vetting. The willingness to make a big bet in this area is, you know, really one of a small number of third-party cloud infrastructure vendors. I think that speaks to how critical this area is. You, you could probably come up with a similar example in any other industry of interest, whether that's, you know, retail, insurance, automotive, public sector. You know, really exciting things happening in each of those. Okay. Okay, great. That's helpful. I have a follow-up for Steffan. Steffan, can you comment on your go-to-market priorities this year, your investment priorities in particular, I guess, with respect to hiring more reps, bolstering customer retention efforts, further building out the channel ecosystem? Has anything changed in the last few months that would require you to invest more in any of these fronts that would, I guess, derail or impede, the, you know, the plans to reach break even exiting year-end? We established a plan at the beginning of the year that focused on a number of investment priorities in the sales and go-to-market organization. A lot of that is based off of quota capacity that we wanna ensure that we have across the world, and we will continue to be hiring in areas that show the most promise and that have the most potential ROI for us. We will continue to make investments in our customer success organization, ensuring that the experience for the customer continues to be excellent, that will both bolster our gross retention rates. Nothing has changed relative to our major investment priorities for the year. In fact, been very pleased with the performance of how the groups are operating in a very choppy environment. If you look at the growth in RPO, if you look at the growth in CRPO in particular, we had an acceleration in CRPO this quarter. That's in part due to the great work that the sales organization and the go-to-market organization is doing. To answer your question, no real changes relative to our plans that we outlined at the beginning of the year. As I said in my prepared remarks, we're on track to achieve break even in Q4. Okay. That's great. The CRPO acceleration is certainly encouraging. Thanks for the questions, guys. Thank you. Thanks, Howard. Thanks, Howard. We'll take our next question from Raimo Lenschow with Barclays, followed by Mizuho. Thank you. Hey, guys, congrats. Good start to the year. I have two questions, first on cloud. There's obviously like a big discussion going on About consumption, optimization, et cetera, and we talked about it a little bit. Jay, like, in what respect are you guys part of that? Can people kind of buy you through the marketplace now and that's kind of a little bit of a headwind? Or is it more like people not doing... You know, like, there's a finite number of new projects starting in this environment and so, you know, that's kind of more what's kind of creating the headwind for you. Yeah. For Steffan, if you think about it, like you obviously outperformed Q1, well done. You kept the full year guidance, that kind of is either more uncertainty or, you know, there's more of a buffer in the year. Could you just talk a little bit about the puts and takes that took your kind of guidance for the full year? Thank you. Yeah. I'll start with the first question. You know, I think it's ultimately like, hey, to what extent are we subject to, you know, optimization, cloud optimization, which is a, you know, topic in every user of the public cloud, including us. You know, to what extent are we impacted by potentially fewer net new software projects that are occurring? Yeah. I would say the latter is probably the most significant factor, right? Our expansion is driven by new projects coming on, adding their data streams, using the technology, you know, taking it out to new use cases. The rate of that is certainly an important variable for us in growth, in addition to how active we are at converting those use cases, which is about the TCO in comparison to open source, et cetera, right? Those two variables are very important. You know, is it possible to optimize the usage of Confluent? Yeah, of course, right? It's possible to optimize the use of any SaaS product, right? This shows up quicker in products that have a consumption revenue model. You know, it shows up that very quarter. Obviously, companies are going through and cutting seats and looking at who really needs the access to that tool and, of course, all the layoffs and any other trimming of staff flow down to seat-based models in exactly the same way. You know, I think there's optimization happening everywhere. You just see it faster in the consumption models. Within those products, of course, it's wildly different how much optimization is possible, and that has everything to do with what the product actually does, right? How much do you actually need the thing that you bought? Is it, in fact, a mission-critical thing that you're gonna keep running, or is this something where you can just turn off if you don't need it? You know, that's an area where I think we have it, you know, very good. We're a mission-critical part of the production application stack. Those applications typically come fairly well optimized. You know, of course, you can go rewrite your applications to try to be more efficient, send less data, you know, whatever. That's a lot of work, and it usually has already been done in the kind of, you know, building and deployment process. We certainly see that, but we don't, we don't see as much of it. Typically, as we have kind of consumption coming online, it's kind of mostly pre-optimized. There may be further optimizations that will happen, but of course, that all folds up into that overall net retention rate. We haven't seen any big changes in that in the last few quarters. Customers, of course, are trying to optimize, but they're also adding new projects, which drives expansion. What you see is kind of the combination of those two factors, which I think, you know, in the end is quite strong. Good. Thank you. Turning to your question on guidance, our point of view on the full year remains unchanged from last quarter. The demand environment remains healthy, even though it's a tough macro out there. We're reaffirming our guide for the full year, growing revenue at 30% and plan to achieve breakeven on a non-GAAP operating margin basis in Q4. We did not flow through the amount of the overperformance we had in the top line this quarter to the full year guide, which is really a byproduct of the macro environment and factors I've called out before, which we're trying to prudently take into consideration while formulating guidance. You asked for some puts and takes. We expect cloud to continue its growth momentum, with the highest NRR and an increase in sequential revenue add every quarter for the remainder of the year. The CRPO growth that I pointed out before continues to be robust. NRR remained healthy, and both of those things support the growth, and in the overall business plan. Okay. Thank you. Well done. Thanks, Raimo. We'll take our next question from Gregg Moskowitz with Mizuho, followed by Deutsche Bank. Okay. Thank you for taking the questions. I guess first for Jay. At your investor briefing last October, I think it was Erica who mentioned that on average it was taking customers who made a significant commit about 6 months for their annualized consumption to match their commitment levels. Obviously the macro has gotten tougher since then. Just curious kinda where that where that stands today. Yeah. We haven't seen a huge change in the ramp-up of customers. That's more determined by how long it takes them to build their applications, get them online, get them fully consuming, roll them out, which is the average of, you know, companies who are moving very fast and companies who move slower. I'd say that has less impact from the macro. We have seen a little bit of change in the behavior of customers and how they use the commits. You know, Steffan called out a little bit of compression in the multiyear stuff. In general, I think customers are just being thoughtful about, you know, the amount that they're committing to. You know, the plus side of that is we've seen very strong consumption against those commit amounts, which is, you know, great. That's what we wanna see. We don't want customers buying a lot that remains unused or anything like that. That kind of above a 100% utilization is a good thing. All right, great. I know the commercial segment has been very resilient for Confluent. Did that continue this quarter, or are you starting to see some weakness? Yeah, it did, it did continue this quarter. You know, we've been watching it closely because, you know, I think that segment obviously has a lot of these private tech companies that I think are a bit fragile under, you know, very significant pressure. We kind of have expected to see some hit there and have not. I would, I would ascribe that primarily to the fact that there's just a lot of untapped opportunity. You know, of course, there is pressure. Of course, that is a countervailing force, but there's also just, you know, a lot of open source Kafka uses to go grow into. The fact that we hadn't paid as much attention to that segment until later in the life of the company and have now gone after it, means there's still a lot of opportunity there. Very helpful. Thank you. All right, as a reminder, to ask a question, please click on the Raise Hand button, and our team will promote you to the panelists. I think we're still waiting for Deutsche to join the room. Ryan, let's go to Eric Heath from KeyBank. Hey, Eric. Hey, I'm in here now. Thanks, Shane. Steffan, just on the cloud revenue side, I think you altered your guidance a little bit to 48%- 50% of Confluent Cloud coming of revenue coming from Confluent Cloud in fourth quarter. Just curious if that's more so a function of new use cases being brought online being a little bit slower than you expected, or is it growth of existing use cases moderating a little bit? It's a little bit of combination of both. As we think about just the mix of business, we did have a strong Q1 for our Confluent Platform, and we look at the overall mix for the year. We modestly shaped the guide for our cloud business. Originally, we said approximately 50% for the year. We basically gave a range, widened it a little bit to 48%-50%. I will say that given the run rate that we have with Confluent Cloud, we're almost at a $300 million run rate, growing at 89%. The consumption of Confluent Cloud continues to be robust. When we think about use case expansion opportunities, there is a natural network effect with the consumption business that we're seeing. In this environment, sometimes it does take, companies longer to deploy new workloads, et cetera. That was factored into the 48%-50% comment that I made earlier. Got it. Jay, if I could just ask you a question. I might have missed the beginning. Apologies. Just on generative AI, I mean, Kafka and Flink are challenging technologies, and finding people with those skill sets is kind of difficult. Just curious if there's an opportunity to leverage generative AI to basically democratize access to those technologies, and if that's something that could bring more users onto the platform. Absolutely. You know, I did address this briefly, the answer focused more on what's the role we provide in generative AI architectures. The flip side of that is, you know, what are the use cases for us? Of course, to the extent that software engineers can become more productive in building applications around this through tools like Copilot and things like that, obviously we become more efficient building our products, also our customers actually can be much faster at consuming our products, and that's a phenomenal thing. We'll have to see how it all plays out. You know, I think the full impact of this and then how it plays out as it happens in all companies is really hard to kind of, you know, estimate the second-order effects of what all that means. I think it's net-net a very positive thing for us. Great. Thanks, Jay. All right. Thanks, Eric. We'll take our next question from Rudy Kessinger with D.A. Davidson. Rudy? Great. Thanks for taking my questions, guys. Hey, Steffan. Gross margins last couple quarters, you know, certainly trending a bit above your midterm target, more so in the range of your long-term target. How should we expect those to trend near term? Why are you seeing the outperformance there? When we look at the guide, you know, you reiterated the revenue, but you took up the operating margin a bit. Is the gross margin outperformance the primary source of that upside in the operating margins? Because it sounds like you're keeping hiring plans pretty much the same. Well, gross margin has been a bright spot for us, especially given the dynamics at play, where we've had an increase in Confluent Cloud revenue really go exponential over the last, call it 2 years. 2 years ago, it accounted for 18% of revenue, today it accounts for 42% of revenue. It comes at a lower gross margin profile than Confluent Platform. We've made a lot of progress on the unit economics there. We've seen really strong growth. As we look towards what the future holds, we feel comfortable with the 70%-72% range, because we think the cloud business will continue its upward trajectory. Longer term, we think it'll be, you know, in the, call it in the mid-70s. The rate and pace of us being able to expand there, is gonna be dependent upon a lot of the engineering work that we're doing, the price discipline that we have, and the value that we're bringing to our customers. Then as it relates to how our overall guidance works for, not only Q2 but for the balance of the year, we are anticipating, being at the higher end of our near-term range of 70%-72% in gross margin. We're definitely letting that flow through the bottom line. We're also seeing the efficiency work that we've been really focused on, across all OpEx line items paying off. So our operational cadence around efficient growth is playing out. But that work is never done, and we're laser focused on delivering it. But we're very happy that we're able to deliver our top line revenue growth as in what we call high growth mode, and dramatically improve operating margin on our path to get to breakeven in Q4. That's helpful. Then was there anything in particular that drove the platform strength in the quarter? I know it's certainly by two things. I mean, one, most of the revenue upside came from platform versus your guide. Secondly, I know in Q4, cloud was 70%, over 70% of new bookings, and it was over 50% this quarter. Obviously the new bookings mix trended more terms platform. Anything in particular that you think drove that strength? We called out the strength in the public sector vertical that tends to be Confluent Platform business, and those also tend to be one-year deals. It was actually the best Q1 in public sector that the company's ever had. That really drove the strength in the platform over performance. Because of that strength, we did see a mix shift from an ACV standpoint. While cloud was greater than 50%, it did come down from a mix standpoint, given just the strength in Confluent Platform. I will say that Confluent Cloud, we've had now 6+ quarters in a row of greater than 50% of net new ACV being Confluent Cloud. That business still continues to grow at a very rapid pace. It was just that Confluent Platform deals tend to be lumpy, they can be seasonal also. That's what we saw play out this quarter. Got it. That's helpful. Thanks for taking my questions, congrats again, on the good numbers here. Thanks, Rudy. Thanks, Rudy. We'll take our last question from Shelby with FBN Securities. Yes. Thank you very much. What was your headcount number for Q1? Did you complete the 8% headcount reduction that you announced? Do you anticipate further headcount reductions as the year progresses? Yeah. Do you wanna take the headcount question, Steffan? Yeah. We substantially completed our restructuring. It's not 100% done, but it's substantially complete. We haven't disclosed the actual ending Q1 headcount before. I can say it's below what it was last, you know, at the end of Q4 for obvious reasons, due to the restructuring. We are continued to be focused on driving operational efficiency throughout the year. Jay, happy to turn it over to you to answer any other part of the question. Yeah. Yeah. Yeah. We're not planning for any further reductions at this point. I get that your cloud gross margin declined 2 points sequentially in Q1. The first time that's happened in my model, if I assume, like, your platform gross margin's like 88% or high eighties, you get around 65% for the cloud in Q1 from 67% in Q4. First of all, did that happen? Was there a gross margin decline in cloud for the first time sequentially? Why did that happen? What's your outlook going forward? Well, we don't guide on the specific componentry of platform versus cloud gross margins. What I will tell you is I know it's hard to model from an outside in, but the dynamic that you described actually didn't happen. We saw nice improvements in our margin structure for the components that go into our subscription margins. Okay. Thank you. Yep. All right. That concludes today's earnings call. Thank you all very much for joining us. We look forward to seeing many of you at our upcoming conferences and our investor day in June. Take care. Thanks, all.