Thank you for standing by. My name is Jaylen and I will be your conference operator today. At this time I would like to welcome everyone to the CloudFlare first quarter 2026 earnings call. All lines have been placed on mute to prevent any background noise. After the speaker's remarks there will be a question and answer session. If you'd like to ask a question during this time simply press star followed by the number one on your telephone keypad. If you would like to withdraw your question simply press star one again. But now let's turn the conference over to Phil Winslow. You may begin.

Thank you for joining us today to discuss Cloudflare's financial results for the first quarter of 2026. With me on the call, we have Matthew Prince, co-founder and CEO, Michelle Zatlin, co-founder and president, and Thomas Seifert, CFO. By now, everyone should have access to our earnings announcement. This announcement, as well as our supplemental financial information, may be found on our investor relations website. As a reminder, we'll be making forward-looking statements during today's discussion, including but not limited to, our customers, vendors, and partners, operations, and future financial performance, our anticipated product launches and the timing and market potential of those products, our anticipated future financial and operating performance, and our expectations regarding future macroeconomic conditions. These statements and other comments are not guarantees of future performance and are subject to risks and uncertainty, much of which is beyond our control. our actual results may differ significantly from those projected or suggested in any of our forward-looking statements these forward-looking statements apply as of today and you should not rely on them as representing our views in the future we take no obligation to update these statements after this call for a more complete discussion of the risks and uncertainties that could impact our future operating results and financial condition please see our filings with the SEC as well as in today's earnings press release unless otherwise noted all financial numbers we talk about today other than revenue will be on an adjusted non-GAAP basis you may find a reconciliation of gap to non-GAAP financial measures that are included in our earnings release on our investor relations website for historical periods a gap to non-GAAP reconciliation can be found in the supplemental financial information referenced a few months ago we would also like to inform you that we'll be hosting our annual investor day on tuesday june 9th now i'd like to

turn the call over to matthew thank you phil we had a very strong start to 2026 we achieved revenue of 639.8 million dollars up 34 percent year over year we now have 4 416 customers paying us more than a hundred thousand dollars per year a 25 increase year over year revenue contribution from these large customers grew 38% year-over-year, contributing to 72% of revenue during the quarter, up from 69% in the first quarter last year. Our dollar-based net retention was 118%, down 2% quarter-over-quarter, and up 7% year-over-year. A gross profit margin was 72.8%. We delivered an operating profit of $73.1 million, representing an operating margin of 11.4%. And we generated strong free cash flow of $84.1 million during the quarter, again, exceeding expectations. The strong momentum we've seen in our business continued to build through the first quarter. Some highlights. Sales productivity increased year over year for the ninth consecutive quarter. Growth in hiring sales force capacity also accelerated in the first quarter, increasing at the fastest pace since 2023. Deals over $1 million were up 73% year-over-year, the fastest growth rate since 2024. We added a record number of our largest customers in the quarter, those spending more than $5 million with us annually. In fact, we added as many $5 million-plus customers in Q1 as we did in all of last year. Bookings from new customers increased at the highest rate since 2023. New pipeline generation grew sequentially at the fastest pace in five years, and we exceeded our planned target by more than any other first quarter since 2021. Our quarterly gross retention reaches highest level in four years, reinforcing that customers understand Cloudflare is a must-have rather than a nice-to-have. We are a significant beneficiary of many of the most powerful trends across the economy. To give you some sense, we had 1 million new developers in just the last quarter. Our products were made for this moment, and we are helping our customers build the future on our platform. That's a good segue to talk about some of our customer wins in the quarter. A leading technology platform expanded their relationship with Cloudflare, signing a two-year, $10 million pool of funds contract with initial use cases for application services and our workers' developer platform. With our full portfolio now unlocked under a single rate card, we won workloads from both a hyperscaler as well as point solution competitors. Looking ahead, we are also in discussions on AI pay-per-crawl to control and help monetize AI bot traffic. A rapidly growing technology company in APAC expanded their relationship with Collabler, signing a two-year, $8.7 million contract for application services and our workers developer platform. Driven by the boom in AI-powered Vibecoating, this company has seen explosive growth, and Cloudflare has become core to their infrastructure, intelligently routing billions of daily requests across the globe. This customer chose Cloudflare over a competitive bid from a hyperscaler due to the strength of our unified platform and our seamless, low-latency security. A Fortune 100 technology company expanded their relationship with Cloudflare, signing a two-year, $8 million contract for our privacy proxy solution, the fifth privacy engagement of this customer, solidifying CloudLar as their go-to privacy partner. They approached us with an urgent need to handle massive scale with precise geolocation accuracy for user-initiated agentic traffic. We delivered a fully operational solution within one week, demonstrating the speed, trust, and engineering depth that continues to set us apart. A leading insurance company in EMEA expanded their relationship with Cloudflare, signing a five-year, $5.1 million contract for application services and our full SASE portfolio. Driven by years of acquisitions, this customer's IT environment had bloated to over 600 vendors, with some employees literally juggling up to four laptops to access essential applications. By standardizing on Cloudflare, they displaced six legacy vendors at signing, with 10 more displacements already underway, targeting over $1.3 million in annual savings. Their CTO put it simply, he wanted a high-performance, quote-unquote, Formula One-level architecture with Cloudflare as the engine. The Fortune 500 Aerospace and Defense Company expanded their relationship with Cloudflare, signing a three-year, $5 million contract for zero-trust products, including browser isolation, access, and gateway. After a major security breach forced this customer to move from on-premise hardware to the cloud they discovered that their first generation zero trust vendors browser isolation solution could not meet critical government compliance requirements putting 5.5 billion dollars in government revenue at risk clasler delivered a fully compliant solution in a matter of weeks where the incumbent could not a leading ai company expanded their relationship with clasler signing a one-year 4.1 million dollar contract for application services as one of the most visible targets for cyber attacks globally, this customer needed a security layer to protect their massive infrastructure build-out. Despite a strong build-over-buy mentality, they chose Cloudflare, trusting a battle-tested network that has proven its resilience against the largest attacks. This is a customer that moves fast and pushes boundaries, and they're already testing our AI gateway for their AI workloads. Another leading AI company expanded their relationship with Cloudflare signing a 10-month, $2 million contract for Argo Smart Routing, coming just one quarter after signing a worker's developer platform deal. This customer wants to be the fastest and most reliable AI provider in the market, and Cloudflare is deliberate. After deploying Argo, they immediately reduced their average global latency by 30%. In the AI space, that kind of speed is a real advantage that our hyperscaler competitors simply can't match. In nearly every customer conversation, it's clear. The emergence of generative and agentic AI is not just redefining the economics of the internet and software companies. They're redefining the business models of all companies, fundamentally reshaping how organizations are structured, operate, and create value. At Cloudflare, we don't just build and sell AI tools and platforms. We are our own most demanding customer. AI and agents are no longer pilot projects at Cloudflare. They are now core parts of our workforce. It's been an interesting journey. We've been selling picks and shovels in the AI gold rush for the last four years, but we ourselves were cautious users wanting to ensure there was real ROI before making significant investment. We avoided a lot of the performative AI some companies engaged in. Internally, the tipping point was last November. At that point across our teams, we began to see massive productivity gains. Team members that were two, 10, even 100 times more productive than they had been before. It was like going from a manual to an electric screwdriver. Cloudflare's usage of AI has increased by more than 600% in the last three months alone. For team members in R&D, 97% use AI coding tools powered by the same workers developer platform we ship to our customers. And 100% of their contributions to our production code bases are now reviewed by autonomous AI agents. I think across the industry, you're about to see a massive uptick in reliability as every Every code or configuration change can now have a tireless and uncorrelated set of eyes trained on every incident from the last 10 years, checking to avoid problems. At the same time, the impact on developer velocity is clear. We've never seen a quarter-to-quarter increase in new code generated, bugs squashed, and technical backlog burned down like we did last quarter. It's been wild. Beyond the product and engineering, employees across Cloudflare from HR to marketing run thousands of ai sessions each day to get their work done those agentic workflows rely on dozens of mcp servers to reach data in systems of record and use hundreds of centrally managed skill files as well as many more that have been created and shared within individual teams the harness that we've built which we call cloudflare os allows teams across the company to quickly get up and running we've asked our team to think what the fundamental job to be done is and then reimagine how we can make the work to achieve it more efficient, reliable, and joyous. At Cloudflare, the way work is done has fundamentally changed. That means being intentional in how we architect our company for the agentic AI era in order to supercharge the value we deliver to our customers and honor our mission to help build a better internet for everyone, everywhere. As a result, we announced significant actions this afternoon to further accelerate our evolution to an agentic AI-first operating model. That unfortunately means saying goodbye to teammates who have contributed to building Cloudflare for where we are today, resulting in a reduction of the size of our team by more than 1,100 people. This decision is not a reflection of the individual work or talent of those leaving us. They were critical in getting us to where we are today. Instead, we are reimagining every internal process, from engineering, to finance, to sales, to run on an agentic AI backbone on our workers' platform. This isn't a cost-cutting exercise or an assessment of individuals' performance. It's about defining how a world-class, high-growth company operates and creates value in the agentic AI era. Deciding to part ways with teammates is the hardest part of this decision, and it's a responsibility the entire senior leadership team at Cloudflare takes personally. We believe that acting with empathy isn't about avoiding hard decisions, but rather about how you treat people when those decisions are made. If we are asking our team to be world-class, we have a reciprocal obligation to be world-class in how we treat them. By taking decisive action now, we provide immediate clarity to those departing and protect the stability of the team that remains. We are also pairing the directness of these measures with severance packages that lead the industry, because we want to ensure that those who have invested their time and talents in Cloudflare's mission are taken care of as we move into the next phase. It's the right thing to do, it's the honest thing to do, and it reflects the values of the company we are continuing to build. On a personal note, this has been a hard day. A number of friends will no longer be colleagues, but I'm confident they will land at other great places and bring with them a set of skills they learned building Cloudflare to where we are today. The group leaving us will build many future great companies, and I'm confident that our reshaped organization will be even more nimble and innovative as we continue to build the future. Not an easy day, but the right decision. With that, I'll turn it over to Thomas to

walk through the numbers. Thomas, take it away. Thank you, Matthew, and thank you to everyone for joining us. Before I begin my customary remarks on our results for the first quarter, I would like to provide additional details on the actions we announced this afternoon to accelerate Cloudflare's evolution to an agentic AI-first operating model. Cloudflare's history proves our business model innovation is as important as our technical innovation. These two forces don't sit side-by-side at Cloudflare. Rather, they compound on each other in ways that provide us with meaningful competitive advantages and create significant value for both our customers and cloudflare ai is driving a fundamental re-platforming of the internet as well as a paradigm shift in how software is created and consumed and it's shaping up to be the biggest tailwind for both our network and our workers develop a platform that we've ever seen in cloudflare's history from this position of strength we are again applying the same winning formula of compounding technology innovation with business model innovation. By fully embracing an authentic AI-first organizational structure and operating model, as Cloudflare's revenue scales, our efficiency and productivity will scale even faster. Unfortunately, this decision means parting ways with colleagues who have helped build the strong foundation Cloudflare stands on today, resulting in a reduction of the size of our team by approximately 20 percent these reductions are across all functions and geographies and reflect how broadly ai is accelerating our operational velocity importantly however we continue to expect growth in the net capacity of our quota carrying self force to accelerate in 2026 with today's actions compounding productivity to fuel our growth these actions will result in severance and other restructuring charges of 140 to 150 million dollars for full year 2026. Approximately 40 million dollars of which is non-cash with a majority concentrated in the second quarter. Our expectations for free cash flow for 2026 however remain unchanged with approximately 25 to 30 percent of full year cash generation in the second and third quarters. By decoupling our ability to scale from the traditional dependencies of the past, Cloudflake will be structurally faster, more innovative, more productive, and more efficient. Now turning to our results. The first quarter was a strong start to 2026, with momentum building across multiple areas of our business. We continue to see rapid growth from AI and authentic workloads across our network, strength in our largest customer cohorts, continuing returns from our go-to-market transformation, and rapid adoption of our workers' developer platform. Total revenue for the first quarter increased 34% year-over-year to $639.8 million. From a geographic perspective, the U.S. represented 49% of revenue and increased 34% year-over-year. EMEA represented 28% of revenue and increased 31% year-over-year. APAC represented 15% of revenue and increased 34% year-over-year. Turning to our customer metrics, we ended the quarter with roughly 4,400 large customers, representing an increase of 25% year-over-year. Revenue contribution from our largest customers was 72% of revenue during the quarter, up from 69% in the first quarter last year. We again saw significant strength in our largest customer cohorts, including those that spent over $5 million with Cloudflare annually, which grew 50% year-over-year and added a record number of additions, both quarter-over-quarter and year-over-year. Our dollar-based net retention was 118% during the first quarter, down 2% sequentially, and up 7% year-over-year. As we've noted previously, there can be some variability in this metric quarter-to-quarter, with growth this quarter driven by a meaningful acceleration in business from new customers, which grew at the highest rate since 2023. Moving to cross-margin. First quarter cost margin was 72.8%, representing a decrease of 210 basis points sequentially and a decrease of 130 basis points year-over-year. Paid versus free traffic on our network continue to grow both year-over-year and quarter-to-quarter, again driving additional allocation of network costs from sales and marketing into cost of revenue. Our work has developed a platform product, which currently carry a lower cost margin than our corporate average, delivered another quarter of significant growth. In fact, developers on our platform increased to more than 5.5 million at the end of the first quarter, an increase of 1 million developers in a single quarter as compared to an increase of 1.5 million in all of 2025. While our developer products are not yet as optimized on gross margin, they also have a lower cost of book. work, and we will continue to focus on driving further efficiency improvements as our developer product scales. While cost margin may continue to trend down in the near term from these dynamics, the scalability and efficiency of our network remain intact, and we expect our unit economic margin will continue to increase. Network CapEx represented 9% of revenue in the first quarter. As a reminder, there can be some variability in this metric quarter to quarter, and we expect network capex to be 14 to 15 percent of revenue for full year 2026 turning to operating expenses first quarter operating expenses as a percentage of revenue decreased three percent year over year to 62 percent our total head count ended the quarter at approximately five thousand five hundred the majority of new hires during the first quarter were in sales with a particular focus on continuing to add quota-carrying account executives. Sales and marketing expenses were $227.5 million for the quarter. Sales and marketing as a percentage of revenue decreased to 36 from 38 percent in the same quarter last year. Research and development expenses were $101.5 million in the quarter. R&D as a percentage of revenue remained consistent at 16 percent compared to the same quarter last year. General and administrative expenses were $63.6 million for the quarter. GNA as a percentage of revenue decreased to 10% from 11% in the same quarter last year. Operating income was $73.1 million, an increase of 31% year-over-year compared to $56 million in the same period last year. First quarter operating margin was 11.4%, percent, a decrease of 30 basis points year over year, turning to net income in the balance Our net income in the quarter was $94 million, or diluted net income per share of $0.25. Free cash flow was $84.1 million in the quarter, was 13 percent of revenue, compared to $52.9 million, or 11 percent of revenue, in the same period last year. We ended the first quarter with $4.2 billion in cash, cash equivalents, and available for sales securities. Remaining performance applications, or RPO, came in at $2,543,000,000, representing an increase of 2% sequentially and 36% year-over-year. Current RPO was 64% of total RPO and includes 34% year-over-year. moving to guidance for the second quarter and full year 2026 for the second quarter we expect revenue in the range of 664 to 665 million dollars representing an increase of 30 percent year over year we expect operating income in the range of 90 to 91 million dollars we expect an effective tax rate of 21.5 percent we expect diluted net income per share of 27 assuming approximately 377 million shares outstanding. For the full year, 2026, we expect revenue in the range of $2,805,000 to $2,813,000, representing an increase of 30% the over year at the midpoint. We expect operating income for the full year in the range of $418 to $421 million. dollars we expect an effective tax rate of 20.5 percent we expect diluted net income per share over the period to be in the range of one dollar and 19 cents to one dollar and 20 cents we expect approximately 375 million shares outstanding in closing the first quarter set a strong tone for the year our strategic position heading into this paradigm shift of the agentic internet has never been stronger and the opportunity ahead of us is larger and more defined than at any point in our history we remain committed to capturing it with disciplined execution durable growth and long-term focus before opening the floor for questions i want to again acknowledge our colleagues who will be departing cloud slayer as we move into our next chapter they will always be part of the Cloudflare story and we are sincerely grateful for their service to our customers and their commitment to our mission. With that operator, please

poll for questions. Thank you. The floor is now open for questions. If you have dialed in and would like to ask a question, please press star 1 on your telephone keypad to raise your hand and join the queue. If you would like to withdraw your question, simply press star 1 again. If you're called upon to ask a question and are listening via loudspeaker on your device, please pick up your handset and ensure that your phone is not on mute when asking your question and we do request for today's session that you please limit yourself to one question and one follow-up one moment please for your first question your first question comes from the line of matthew hedberg of rbc capital markets your line is open great uh thanks for taking my questions

guys um you know matthew first you know on on your strong cuban results you know i find it interesting that that some of your act one competitors don't seem to be benefiting um from monetizing congenital traffic the same way you are. I guess, you know, first of all, why are you seeing such strong tailwinds there? And then as a follow-up regarding the announced restructuring, really in light of these strong keyword results, it seems to really be coming from a position of strength. I guess the question is, why now? You know, how is it going to make cost fair stronger? And Thomas, have you embedded any conservatism in the guide for this action?

Yeah, Matt, so thanks. And to, maybe I'll start with a second, because again, I think it's, you know, I think sort of the honorable thing to do. This wasn't an easy decision, but it's the right decision. We've just seen that there are roles at Cloudflare that just aren't the roles that we need for the future. I think just because you're fit doesn't mean you can't get fitter. And so I think that what we've seen over, especially the course of the last six months, is just the productivity that we've been able to gain from the people who are directly talking to customers, the people who are directly creating code, that that has been just such an incredible efficiency gain. And a lot of the support, people that provide support behind them, those roles aren't going to be the roles that drive companies going forward. I think we've always lived a little bit in the future. And I think that you're going to see companies around every industry starting to realize the gains that they can get from these tools. And in the process, I think that that's going to change companies pretty dramatically. We're, I think, early beneficiaries of that. I think that we will continue to – we believe in people. I think that we will continue to hire people and we'll continue to invest in them because the people that are embracing these tools are just so much more productive than we'd ever seen before. And I would guess that in 2027, we'll have more employees than we did, you know, at any point in 2026. But the roles are changing dramatically, and you've got to do something dramatic in order to make that shift, and that's why this was the right time. You know, in other words, we're the fittest we've ever been, but we're going to get even fitter to win the next chapter. To your first question about traffic, I think the key here is something that we've always understood, but I'm not sure the market has understood as well, which is not all traffic is created equal. A lot of the times, if you were sort of a traditional CDN customer or company, what you were trying to chase was things that drove lots of bandwidth, so video streaming of live events and things like that. And, again, that was an okay business. I think it had a lot of pressure. It was largely a commodity. But, you know, that was kind of the game of being a CDN. We never saw ourselves that way. We thought what we wanted to get in front of was the most essential traffic that was out there, not bandwidth and video streaming, but APIs and applications and seeing that. And I think that in this new world of agentic commerce and agentic transactions, our approach is showing kind of the wisdom and durability of that. So today, you know, literally we're seeing hundreds of billions of agentic requests per month, and that number is growing exponentially. They are interacting with us, and we are setting what the rails and the guardrails are for that, and that's driving our act one business. And then on the other side, you know, in our workers' platform, you know, we have built a platform that allows you to build agents that are just significantly more efficient than anyone has before. And so across all of the parts of our business, because even in the zero trust and sassy space, it turns out that having more fine-grained controls about data is exactly what you need if you have kind of these, you know, somewhat new agents running around doing things. you want to make sure that they they only have access to the things they should it's it's i wish i could say that you know we saw all this years ago and built cloudflare for it um but but i think that the the reality is that we we happen to have built exactly the right set of tools for this moment and i think that's what's that's what's separating us from some of um some of the people

that we sometimes get compared to thanks natty yeah let let me take your your second part regarding guidance and how this action is reflected first of all i i would say we've been rather thoughtful and you heard in my um prepared remarks that while this action pretty much affects all teams at cloudflare the the only exception really is our ae and uh code occurring capacity um that is sitting in front of the customers we hardly touch that um and um i think we've been careful trying to reflect whatever residual risk remains in the guidance that we provided for the remainder of the year. So I think we, as usual, we try to be thoughtful and then prudent in how we think about what is in front of us. Thank you. Your next question comes

from the line of Adam Borg of Stiefel. Your line is open. Awesome. And thanks so much for taking

in the question. Maybe, Matthew, for you, you know, one of the things that we keep on hearing about is just how AI costs internally are really expensive, especially around, you know, R&D coding agents use internally. And so how do you think about balancing, you know, R&D-adjected coding adoption with the cost? You know, what AI efficiencies are you looking to see across the organization? And of course, you know, how much of this risk is to offset some of what I just

mentioned. Thanks. Yeah, so first of all, you know, we have seen as usage has gone up, you know, 600% in the last quarter. We have seen costs go up, but I don't think it's gone up nearly as much as some others. And that's driven by a number of things. I think the least important is, you know, it turns out that most of the big AI labs are cloudless customers. And so we have very good relationships with them we work with them we have we have ways of making sure that we can get um you know the best pricing and the best the best models uh from them um i think more importantly though is a lot of times we're able to run those models instead of on on their infrastructure on our own infrastructure and so uh we have a fleet of gpus and we have uh all of the tools with cloud floor workers and workers ai to be able to build and use those tools themselves and so So most of the use of various AI coding tools isn't even leaving our network, it's running on our infrastructure. Because we're very good at routing to wherever there's capacity, we're able to get a lot out of that. And so I think that's one of the reasons why we see a significantly higher utilization across our GPU resources than any of the hyperscalers and then even of the AI labs are able to able to drive. And then when we built what we call Klausler OS, we've paired that with our AI Gateway product. And that AI Gateway product allows you to route different requests based on what's the right model for the right task. And so that means that if we have a task which we can evaluate as being relatively simple, then we can route that to a model that might be running on our own infrastructure and be able to, you know, be delivered at essentially no marginal cost to us. Whereas, if we have something that is more important, we might, you know, send that off to one of the frontier models and pay more for that. I think that that model, again, I feel like we're living a little bit in the future. I think that's what you're going to see a number of companies doing, and as we demo Cloudflare for OS to other companies, you know, what we're seeing over and over again by CIO after CIO after CIO is, wow, we want that, too. And so we already have kind of the stripped-down version of that with Cloudflare as AI gateway, but I think you might see us increasingly take some of the tools that we've built internally and actually make those available to other companies. And that's actually very normal for Cloudflare. Almost every product we've had that's been successful starts as something that we needed ourselves, and then it turns out that what we've built for ourselves is valuable to others as well.

That's really helpful, and maybe as my follow-up, you know, Fournet last night talked a lot about this opportunity that they're seeing in Sovereign SASE, and when I think about Cloudflare and just, you know, your global network and your reach and data residency requirements globally, how do you think about the data localization opportunity, sovereign opportunity, not just in Act 2, but across the acts? Thanks so much.

Yeah, I mean, I think that we're uniquely positioned for a world where there are increasing regulatory or even just practical requirements around keeping data in particular jurisdictions. We're present in more than 120 countries worldwide, more than 350 cities, and we're designing all of Cloudflare systems in order to really think of data as being able to just stay wherever your permissions are. So if you're a customer that really cares about, I need to make sure that all my data stays in Germany, because I'm a German healthcare provider, then we can actually set that up now where your data can actually stay resonant in Berlin, Frankfurt, Munich, the various data centers that we have inside of Germany, and we can do that with a level of granularity that no hyperscaler can match. And so I think that will increasingly become an advantage of Cloudflare's network because of what we're doing. And then if you layer on top of that the Zero Trust and SASE tooling, that's going to allow us to make sure that agents can only get access to the things that they have permission to get access to. And I think that's actually going to be a bigger tailwind to that space. And again, we won't be the only winners there, but I think across the board, you're going to see a lot of these principles that sort of the most forward-leaning companies had adopted previously, that those will become much more standard with what people are doing with things like OpenClaw. I mean, it's amazing how the fact that we have a self-service version of our zero-trust products, as people are experimenting with things like OpenClaw, they need to have that fine-grained data control and we're basically the only game in town to deliver it your next question comes

from line of second calia of barclays your line is open okay great hey guys thanks for taking my questions here and a nice start to be here um thomas maybe maybe for you um you know i i know the growth in in different acts of course has different impacts on on gross margin and of course you know we spoke about sort of the proactive optimization here in the business as well as as As we get through those changes here, I think you said by the end of Q3, how do you think about sort of the net impact to OpEx, and how should we sort of think about gross margins as those other acts continue to grow?

Yeah. You know, it's a topic we've been talking about for a while, that the margin structure is different, the cross-margin structure is different across the various acts, with the developer products being the cross-margin weakest. But we also said that despite the fact, all products are pretty much equal when we look beyond cross margin and look at performance from a unit economic value. And I think this will be a transition that we will get you ready for on Investor Day, that our operating margin becomes a better measure for competitiveness of products than cross margin. Just keep in mind that one of the biggest moves in cost margin the last quarter was free traffic moving to paid traffic and cost moving into cost of revenue. While that is decreasing the cost margin, it's literally a wash from an overall P&L perspective. And I think you'll see more movements like that. It will be up to us to give you the right insight. But what is clear to us across all products with opportunity in front of us, that the unique economic margin and value is going to increase over time. We, you know, with a guidance that is in place already today, we are getting north of 46 percent from a rule of 40 perspective. And we think we have visibility to reaching, you know, north of 50 percent next year. So, that all shows you how much potential is, and we just need, you know, to give better insight in how the various parts are coming together and provide force in that direction.

Yeah, the one thing I would add to what—sorry, I was just going to say, the one thing I'd add to what Thomas said is just to put a finer point on what I think is the most important part there which is you know for for since our since our founding croplers always had a free version of our service and that that provided a lot of different benefits one of the largest was it gave us data to provide build the security models and and and do everything we did um and we haven't actually worked that hard to convert free customers into into paying customers with that and and so the the traffic that was associated with those free customers went into into as a marketing costs. What's been fascinating, though, is that that giant pool of free customers turns out a lot of them are developers. And so as we've now built incredibly compelling developer tools, most of our developer tools aren't free. They require at least some payment. And so you're seeing a lot of that free traffic turning into paid traffic. And so it actually might be that the cost of customer acquisition that we have for those really high growth products like our our developer platform, are really fueled by what we've built over the beginning of CloudFlare and some of those Act 1 products. And so while that shows up somewhat funnily in gross margin, it actually is a sign that more and more people are adopting the paid products, including the developer platform products, which is, you know, the part of our business, which I think, you know, I am certainly among the most excited about.

It's a great reminder and certainly a geography shift to your point. Matthew, maybe for you for my follow-up, I'd love to hit on Act 4 a little bit and Cloudflare's ability to sort of manage that relationship between, you know, AI tools, you know, scraping type of tools and content owners. Maybe the question is, what are some of the milestones that you need to see in order to see that business inflect? You know, is it big lighthouse accounts? Do you need industry consortiums? It's just such an uncharted territory. I'm curious how you think about it.

Yeah. I think the way that we think about Act 4 is that the business model of the internet, which has historically been advertising and subscriptions, is about to change dramatically over the next five years. And exactly what it changes to, I think, is still an open question. And I think it might not be one thing. I think it might be several things. Because of how much of the Internet sits behind Cloudflare, we have a seat at the table of defining that. And so I think there are a number of different things that I'm watching. So one of them is I think that some part of this is going to be some kind of microtransactions for any requests that agents are making. It might be fractions and fractions of pennies. But, you know, if you think about the, I don't know, it's about 500 billion requests that pass through Cloudflare, you know, in any given second, that some percentage of those, we think that there's going to be some ability to have some micropayment that is made for that. Because I'm asking for the infrastructure, and if you look at the growth in a genetic traffic, if you look at the growth in sort of non-human traffic on the Internet, somewhere in 2027, we think it's going to surpass human traffic, and it's not going to slow down. And so we've got to figure out something else to build it. So I think one of the milestones we'll look for is how do we figure out what that sort of micropayment infrastructure looks like? And the challenge is, like, nobody can handle the volumes right now. And so we're looking around to partner with people. we're looking around for everything. But right now, the sort of transaction volumes that people are excited about, like a million transactions per second, we need something that's significantly larger than that. So I think that's one thing. I think on the other side, you know, first of all, it's really important to be clear that the answer isn't that everyone wants to be blocked from AI, or everyone wants them to be paid. For example, Cloudflare has a whole bunch of developer We want those developer documents to be in every single LLM that's out there, and so we make it as easy as possible for LLMs to crawl our developer documents. On the other hand, if you're an ad-supported business, then your content being crawled is actually a threat. So I think we're trying to provide tools on both sides of that. The side that you focused on was the folks that want to block it, the ad-supported folks that are out there. And I would say that the first milestone that we've seen is that we went from being relatively low in terms of our penetration in the media space to today dominating that space. And so I think that's the first sign. And what I hear from media company execs is they are signing better deals with AI companies because we've given them the tools to be able to control who has their content. That's the early lighthouse signal. I think the question is, how can we then take that down to the long tail? So sure, the Condé Nast or the dot dash Merediths of the world can negotiate their own deals, but how do we make that available for everyone that's on the Internet? And I think that's going to be really some lighthouse sort of deals with some of the foundational model companies. And, you know, I don't know exactly when that will come, but I do, I do, I will say that when we listed what our top six priorities were for 2026, One of the six was making sure that we make real progress and see the first revenue that we can then pass back to that long tail of the Internet in order to help make sure that we continue to create a healthy ecosystem for content creators. And I'm pretty confident we'll make that goal.

Your next question comes from the line of James Fish of Piper Sandler. Your line is open.

Hey, guys. Thomas, you just mentioned Rule 50 there. potentially. But given what you're seeing with the demand behind inferencing, I guess what's the team's willingness to go after more of this opportunity and really drive more megawatts behind the network to host more of those inferencing use cases like what you're seeing out of some of your

edge peers? I can get started, but Matthew for sure has an opinion on this. I think you see us leaning in in this opportunity already with all the force that we have this is the reason why you saw developer count go up by a million um in in the first quarter alone we are continuing to to optimize margin for these products but we are not at all restricting growth just the opposite i would say so um this is not a there's no restriction on leaning in into this opportunity

I think that, Jim, at risk of kind of being critical, I think that people don't understand the difference in our business model versus the hyperscalers. The hyperscalers' business is to buy a server and then to lease that server back, ideally for five times or more of what they paid for it. And so if they don't have servers to lease, then they can't grow their revenue. And so their CapEx has to invest ahead of whatever that demand is that's out there. We focus on very different things. So the thing to watch for us is when you see us publish a blog post about how we figured out how to get more utilization across our fleet of GPUs or how to get more models loaded quickly across GPUs, that's real IP that we're inventing internally. And the metaphor to think about is, what's one of the time when I was in college? I remember this new thing called the web was starting, and so we needed to have a web server. And so we literally, from Gateway, I remember ordering a box that came with cow prints on the outside of it. But we bought a gateway server, and we plugged it in because there was no idea of virtualization. And then VMware came along, and after that you had Docker and containers, and that was sort of the journey that everyone went on. We're still at the stage with GPUs of buying the physical server and needing to use that for most of the industry. And so across most of the hyperscalers, you're seeing utilization rates of their GPUs that are in the single digits, whereas we're slowly getting our GPU utilization to approach what our CPU utilization is, which is up in the 70 to 80 percent range. And so as we do that, we can actually continue to, with the fleet we have, service the requests that come in and invest behind demand as opposed to investing ahead of demand. And so because our business model is different, that's allowing us to continue to keep up with the inference demand and also do a lot of experiments and trials and things to capture developer mind share that is very different than if, again, what your business is, is essentially leasing a physical server that you bought and trying to get at least five turns

out of that lease. Yep, makes sense, Matthew and Thomas. Maybe just following up on the security side look you guys have been aggressive about displacing uh the legacy hardware guys across security firewall vpn and so forth are you seeing any compression in enterprise sales cycles for large-scale zero trust deployments or a macro or macro approval still kind of elongated and really the crux of it is is the supply chain issues the component issues causing more customers on the enterprise side to start to evaluate more of the cloud uh opportunities out there for protecting their environments. Thanks, guys.

I mean, the hardware companies seem to have nine lives, and I don't know how many more they have to use. But I think that as you see that there are vulnerabilities in hardware, which, you know, some of the Palo Alto had issues with, as you see, again, supply chain shortages, especially around memory right now. I do think all of those things are pushing more and more people to evaluate that they need at least some part of the cloud as part of um part of their their infrastructure but but again i i've been i have been impressed by how long the hardware players have continued to operate and hold out so i'm not willing to call that you know this is the time that that is going to be you know a complete change but i do think that there's um i i do think that that the cloud continues to show its resilience and that that and that that that all these things are tailwinds behind behind our business and other you know cloud native businesses

that are out there your next question comes from line of gabriella borgias of goldman sachs your

line is open hey good afternoon thank you matthew and thomas i wanted to get your observations on how the fleet mix may be changing between gpus and cpus and specifically matthew you're just talking about how gpu utilization is approaching cpu utilization are you also finding that there some AI inference that you can now route to CPUs. And, Thomas, I imagine that has an implication on the unit economics of how you're serving up the AI inference market.

Yeah. I mean, so we want to make sure that for customers, we're just abstracting what the most optimum silicon is behind the scenes. And so for some models, CPUs work great. But for others, we want to make sure that GPUs, you know, are available. As we deploy, you know, a server, those servers today have, you know, they sort of come with all of the various parts, and so it's not you deploy a GPU server or you deploy a CPU When we deploy a server now, it's got a CPU, it's got a GPU, it's got a certain amount of memory, it's got a certain amount of storage, it's got a certain amount of capacity in the And those are all resources that we're constantly trying to both balance and then create opportunities around. And so I think what's different about us is we're not renting, you know, an H100, but we'll have H100s across our network. And then we're trying to match the workload that makes the most sense with the silicon that's behind that and with what a customer is paying for. So if you're paying us more, then we're going to, you know, give you a faster and better experience than if you're paying us less. And so I think that that has always, like, at some level, software has always been just a giant scheduler. And so what we're effectively doing is dispatching those jobs across this and then being able to drive it. It's a question earlier about is our cost going up because our developers are using more AI tools? The answer is yes at the margins, but much less than we see from our peers because we can use that giant scheduler to essentially route those tasks to anywhere we have excess capacity across our network, and we can prioritize those based on what is, you know, more important or less important.

Matt, there is the data point intra-quarter on entropic announcing managed agents. I would just love to pick your brain on where you think that type of infrastructure intersecting with the LLM creates opportunity and or risk for the collaborative business model.

I mean, I think that we're, so without talking about specific customers, I'll say that what What we're seeing from the major AI labs is, first of all, that we're partnered with all of them and get access to all of their labs, and that they see our infrastructure as critical to being able to deliver this, and so they are actually looking for partners to be able to have that infrastructure run on, and so, like, the examples of, you know, in the case of we launched something called dynamic workers which allows you to very very quickly stand up something which is which is significantly more efficient than a container containers are too slow and too heavy uh that to actually be able to respond to these incredibly fast agentic workloads and so um what ai studios are are doing is they're looking at this and they're seeing the opportunity and so to give you a sense of with i'm naming them one of the you know large ai studios um in just the last 15 days went from essentially zero dynamic workers to over a million dynamic workers running across across this uh the platform and and we're seeing almost everyone excited about the the underlying tools and technologies that we built so i see what what anthropic is doing um as being you know very positive to the infrastructure that we that we see we see that as an opportunity uh to deliver incredible value across that and we see ourselves as very differentiated in the space and able to provide significantly better performance and at a significantly lower cost than than anyone else who's playing in the in space today your next question comes from

the line of fatima bulani of city your line is open good afternoon thank you so much for taking

my questions. Matthew, along those lines with respect to the agentic edge and agentic AI systems moving into production, I wanted to hearken back to a lot of the announcements that you made at Agents Week. It's very clear that there is a fundamental rewiring that you're working on to natively power agents to basically do their best work, to put it simplistically. and a lot of this does seem like it is a frontier monetization opportunity for you but I'm wondering if you can speak to what sort of halo the rise of production agentic systems could have on the more flagship established parts of your business i.e. the revenue and monetization halo to act one act two and certainly act three products and then I have a follow-up for Thomas, if I may.

Yeah. I mean, I think for the Act 3 products, the developer platform products, I think it's the most obvious, which is that we're just seeing more code being created. It needs an efficient place to run. It needs to have, you know, a set of primitives that can act as fast and as ephemerally as agents need to act. So if you imagine that you're a company that's building something that's going to plan a vacation for someone, what you really need is the ability to essentially spin up an extremely lightweight sandbox that writes code that assembles kind of all of the different parts of what that vacation may entail, puts it together, pulls it back, and then blows the sandbox up very, very quickly. to do that with any other platform is extremely expensive and slow. And we've made it, with some of the things that we've announced during Agents Week and otherwise, we've made that just drop dead simple. And so that's driving a ton of use. And again, I think that the way to see that is the fact that we added a million developers to our platform just the last quarter, you know, almost as many as we did in all of last year, is extraordinary. And if you look at growth across the workers' platform, more than three-quarters of that is from new customers. And the growth rates are pretty extraordinary across that. That's also, again, just putting pressure on gross margin because those are less optimized for gross margin products. But be confident that it can continue to drive GPU utilization and all those things that we'll be able to get more out of that. I think to the other part of your question, just as more, every time an agent does something, like if you think about it, if you type something into, you know, ChatGPT or any of those things, like to search the number of sites that get searched, the amount of traffic that gets generated. If I'm looking for a digital camera as a human, I might visit five websites if I really care about it. My agent's going to visit 5,000. And so that's going to just drive significantly more usage, which is the biggest driver of kind of our Act One revenue. And again, I think unlike some of the pure play CDNs that are out there, you know, the agents aren't going to go watch reruns of the Super Bowl. They're going to drive things that actually drive real traffic to real e-commerce sites. And that's where Cloudflare and the huge block of the internet that sits in behind us is really valuable. And then for Act 2, again, as we talked about already, I think being able to very narrowly define what data an agent has access to and what data they don't, we're just seeing more and more of that usage, especially in the self-service category, which there really isn't another sort of sassy, zero-trust, self-serve competitor out there with any sort of scale. And so that's with things like OpenClaw grabbing a lot of usage there, and what we found time and time again is as hobbyists or individuals adopt technology, they inevitably start to bring that technology more and more to work, and that's what we're seeing as we win more of the enterprise accounts across NAC2.

Thank you. Thomas, just on the pool of funds, you're sort of in year three in earnest of having this motion with your customers mature. I was wondering if you have any comments or observations on a pending renewal cycle from maybe your earliest vintage of pool of fund adopters, and maybe what trends you are seeing from a renewal and expansion of usage vectors as you re-engage with some of these customers that are, you know, coming back to the well, so to speak.

Yeah. Well, you know, as we are now in our, I would say, sixth quarter of pool of funds, it becomes a much more standard tool in our go-to-market motion. Folks are familiar in how to deploy the tool, when to deploy it, when it makes sense. So I think we get efficiency in the process. From a renewal perspective, you heard this in Matthew's prepared remarks. We had our highest ever renewal rate in the last quarter and that includes all their pool of funds deals that were up for renewal so i would say um the hypothesis that this would be a tool that not only allows us to work expansion really well but also becomes a very sticky tool from a customer

engagement perspective has turned out to be true and your last question comes from line of shaul

Eyal of TD Cowan. Your line is open. Thank you. Good afternoon. Thank you for squeezing me in. Thomas, you mentioned quota carrying sales capacity continues to accelerate. Could you provide some more color on your expectations to continue to grow capacity relative to productivity?

And I have another follow-up for Matthew. Yeah. So, when I said we are not touching quota carrying a sales capacity what goes along with that is where we see significant productivity is in the support ratios for these for these aes so the ratio is going to change significantly which means we are freeing up dollars and in within the same spent envelope now of dollars you can deploy more quote-occurring AE capacity towards our market opportunity. And this, of course, then will allow us to continue to drive productivity from a go-to-market perspective.

Got it. Matthew or Thomas, partners increased to 30% of revenue this quarter. what's driving this continued increase and how much more channel mix would you expect going forward?

Yeah, I'll start and Thomas might have more to add. I think that, you know, this really started with Mark Anderson laying out certain two years ago that we were going to have a motion that really included partners and made sure that they were able to deliver on them. I think that it has been an incredibly successful way for us to sell, especially our Act II products, which require a lot more of a consultative sale and a lot more of work making sure that the integration is done extremely, extremely well. That I think will continue going forward. I think that the big question is going to be what partners are really able to leverage this new world of agentic AI in order to, you know, just get additional value and scale and velocity. And I think that's what we're evaluating across the partnership world. I think there's going to be a lot of change in that space, but I think that partners will continue to be an extremely important part of our strategy. And just like, again, I think a lot of our businesses is changing. A lot of our partners' businesses are changing, and we're seeing that the ones that are delivering the most value to customers and are the best at getting success at selling are our tools, are the ones that are embracing new ways of selling and servicing and making sure that the customers are successful with our tools. Thank you. That concludes our Q&A session.

I will now turn the conference back over to Matthew Prince for closing remarks.

So, again, just wanted to emphasize, this has been a hard day. We've never done something like this in Cloudflare's history, and we take it extremely seriously, and we know how much it has affected people who have been friends and colleagues. I am confident that those people who are leaving us today are going to go on to take what they learned at Cloudflare and help build many more great companies. In fact, it's amazing to see how many people are already writing in saying anyone who got traded to Cloudflare, we will be happy to interview. We're going to make sure that we take care of those people, but we also want to make sure that we are hiring for the right roles. This isn't about us downsizing. This isn't about us saving costs. This is about making sure we have the right people in the right roles to build the future. Our mission is to help build a better internet. That's an important mission. it's never been more important as the internet goes through all of the transitions with AI and agents, and Cloudflare is going to lead the way. I'm proud of everything that we're doing. I'm sorry that we had to take the action that we did today, but I believe it's going to make Cloudflare better for the future. Thank you. We'll see you back here next quarter. This concludes today's conference call.

You may now disconnect.