Excellent. Thank you everyone for joining us this afternoon. My name is Keith Weiss. I run the U.S. Software Equity Research franchise here at Morgan Stanley, and really pleased to have with us from Cloudflare, CFO Thomas Seifert. Thomas, thank you for joining us again. Always a pleasure. We were on the same stage a year ago. Yep. We were talking about how 2025 was gonna be a year of inflection for Cloudflare. It was a pretty spectacular year, right? There was activities that took place that we weren't really on the bingo card, if you will, of investors. You signed your largest ever contract, a $130 million contract, seven years in duration. The highest ACV deal you've ever signed at $42.5 million. RPO grown 48% during the year. 30% revenue growth accelerated in each of the last three quarters. The net revenue retention rate improved from 111% in Q1 to 120% in Q4. Number of paying customers up 40% year-over-year, and the list goes on, right? That's, I mean- Thank you. ... by every measure, a spectacular year. Maybe just to start out the conversation, what clicked into place? I mean, it's not like you weren't performing well before, but it definitely feels like you were correct, right? There was an inflection that took place. What were the elements that came, like, really to fruition that enabled those types of results? I would say last year was the result of mainly two things. The first one was the compounding effects of a sales transformation that has been going on for more than two years now, and all the things falling in place. Moving up the enterprise stack, making good progress with large customers. The larger the customer cohort for us, that means above the $1 million or $5 million of ACV, the more acceleration we saw, productivity on the sales force, pool of funds deal. The sales transformation really compounding and on all the vectors that have been touched. I think that that was one of the big contributors. I think the second part is that, you know, it becomes clearer and clearer that we are not selling just a product, but we put a platform in place that helps our customers solve significant and challenging problems. The innovation around that offering, that platform is really what differentiates us from many in the market. I think this could not have been clearer last year. All the events around AI and the products and tools we are putting in place in order to support that transformation. That all came together nicely, knock on wood. I think those are the main two reasons why last year was such a special year. Got it. As we head into 2026, are you gonna give us another prognostication of an inflection point into 2026? Maybe a fairer question for you. If it's sales transformation and like really stretching the benefits of the platform in 2025, any additional elements that we should be looking on and turning on in the story in 2026? I think we'll make, we'll continue to make progress around those fronts. Then on top of that, I think we all currently see that AI is re-platforming the internet, in a way, how code is written, how people interact, and I think this will be one of their significant tailwinds for Cloudflare in this year and moving forward, to be really honest. Yeah. Yeah. I wanna start and dig in on sort of the product side of the equation. Yeah W hich is always a little bit dicey with the CFO, but we'll give it a shot. I'll be pretty good with the product. Trust me. We came out with a framework on team software at Morgan Stanley. We called it our Best Athlete framework, right? The elements of that Best Athlete framework was in a time of rapid change within the overall environment of rapid innovation, we're looking to companies that have speed, meaning fast innovation. They have strength, meaning good kind of market positioning. They have good execution capability. That's a skill. Flexibility, right? The ability to change the business models to match that scenario. I think one of the most impressive things that we've seen over the past year is that product innovation really meeting the period, right? Mm-hmm. You can see that across multiple parts of the platform. You guys often talk to like Act 1, Act 2, Act 3, and Act 4. Yeah. What's so interesting, though, is that it's not like Act 1 and Act 2 goes away when Act 3 and Act 4 comes online. Yeah. You build upon it. What is it, like, that enables you guys to be that nimble and to be that sort of fast ahead of the right trend? If we take Act 3, the Workers and the Developer Platform, quickly Workers became the Developer Platform of choice underneath a lot of these code generation tools, underneath a lot of those platforms. What enables you guys to get into that positioning to be in the right place at the right time when these innovations are taking place? You know what? I always go back and say when investors start to work on us and say, "If you really want to understand what we are and what we do, you have to go back and understand the architecture of the network." This is really the highest competitive amount we have. You know, the network today, after 15 years, is now in 330 cities, in many cities like San Francisco, in multiple locations, in 125 countries, and interconnected today with about north of 13,000 networks. That is the infrastructure today off-the-shelf hardware. Every product and every service we run, whether it's application services in Act 1, SASE and Zero Trust in Act 2, whether it is Workers now in Act 3, whether it will be, you know, what we say, pay to scroll products or whatever, how we monetize content in Act 4, is running on that one network. Every product and every service we offer on every server in every location. This is a flywheel that is feeding itself. You know, you talked about Workers. Workers was originally not a product that was supposed to be sold. It was a tool that helped us to innovate our products fast enough, how we write code, and how we can deploy code with the push of the button to region Earth all around the globe. This flywheel, I think, is, based on this infrastructure, is allowing us to stay ahead of this innovation game. You know, now we're in a world of agentic AI flows, we're looking back now, it seems the infrastructure of the network was built exactly for that use case. What do you need in order to build an agent? You need a CPU, you need a GPU, you need API. The CPU orchestrates, the GPU computes, the API fetches the data. In Cloudflare, this happens all in one place on one server. In a world where now between 20%-30% of all websites and all traffic is moving through the network. The insight you have into what market needs and where markets are going is driving that flywheel to an extraordinary extent. Got it. You have a lot of visibility by having- Yeah ... sort of that perspective. A network that was built for flexibility. Yeah. Right? That, that one unified network that everything builds up, and it's all software that gets built up. There's no bolt-ons, as Matt's told us over the decades. On the other side, you've been able to develop a extreme level of developer affinity. On the most recent conference call, you talked about over four and a half million human developers. One of the things that really struck me, I was looking at a Stack Overflow survey, and they asked developers, like, where do they want to develop their applications? The first three on the list is exactly who you'd think it would be. It's Amazon, Microsoft, and Google, because they're huge and the behemoths. Number four is Cloudflare, right? It's become the place, not what your boss is telling you to develop on, but the place where developers want to go to develop. How do you, like, how do you gain that developer affinity? How do you make yourself such an attractive platform for those developers? I think a couple of things come together. You know, the tools you build, the ease of use of the platform, the languages that you put into the hands of the developers to work with it, the cost of the product, the performance of the product. They all have been coming together. You know, the interesting part now is we talked about 4.5 million human developers on the platform. If you look at the agents on top of that, it's staggering. If you look at downloads of Workers KV over the last 2 months, you know, it's growing almost vertical. A big part of that is literally agentic AI agents downloading, programming themselves, deleting when they are done. This comes together now in a really unique way. Yeah. It's a really interesting point. I was talking with Sanjit Singh, who covers a lot of infrastructure names for us, and we're talking after the Databricks presentation. One of the themes we're starting to hear more and more is the tooling doesn't necessarily have to be built out just for, or can't just be built out for humans. Now you have to build a set of tooling, a set of infrastructure that's very amenable to the agents. Does that change the way that you approach the Workers opportunity? Does that change sort of how, or sort of what you need to build out in there to make yourself the sort of platform of choice, not just for the human developers, but for the agents? Very much. I mean, you know, we started really early, over a year ago now, a year and a half ago, to put a speedboat in place. This is what we called it around the developer activity. Their person in charge, Ally, was actually the woman who developed Worker as a product in order to get our arms around what go-to-market do we need for enterprises? What features do we need? How do we get to the large deals? How do we keep the human developer count growing? What do we have to do from a offering, from a feature, and a performance perspective to address what you said? How, you know, how do we make ourselves discoverable for agents that are doing development work, writing code on our network? Yes. Got it. You guys recently acquired Replicate and Astro to strengthen that Developer Platform. Can you talk to us about what these acquisitions brought into the equation and how it fits into that broader vision of Workers that we're talking about? I mean, you know, how do we cater to their developer ecosystem in terms of the offerings we have, the products we have? How do we get more dynamics in our go-to-market place? How do we build this marketplace for developer tools and products, you know, that you're drawn to work with us in our platform. I think, both acquisitions squarely fit into that motion, and you'll see us do more activity in this direction moving forward. Got it. Yeah. Can we just touch briefly on sort of the defensibility? There's AI labs that are focused a lot on the code development and the agentic code development, but they're broadening their scope, right? Is there a dividing line that you feel comfortable there's a defensibility of sort of the Workers Platform versus where this expanding scope of what we're seeing the AI labs and their focus on that whole development life cycle is going to hit? I think it's a combination of many things, that I think, you know, it starts with us being that control plane where agents have to move through. You know, whether it's a human interaction or an agent of interaction needs to be secured, it needs to be transported. It moves to our network today with, you know, 13,000 interconnects and 20%-30% of the web traffic behind us. There's that. I think the architecture of the networks and how Workers architected on top of that, in terms of no containers, but isolates. You know, we talked about how agent workflows are architected. You need a CPU to orchestrate. You need a GPU to compute. You need an API to get data. In our world, you know, you have to wait for the traffic for the API to deliver data or not. In our architecture of isolates, this wait period can be important, can be really expensive when you work on container platforms. In our case, the spin up, and more importantly, the spin downtime when you're waiting for the data to come back is really fast, goes to zero. With that, the offering of how we are able to price, you know, not for time, not for capacity, but for a task completed makes us really unique. I think the combination of the ecosystem, the tools, the architecture of the network, and then the architecture of Workers itself running on that network is a pretty substantial competitive moat that is hard to overcome. Got it. Mm-hmm. It comes back to that strength, that being in front of 20% of the internet, but really the infrastructure being in front. Yeah ... of that 20% of the internet with a secure platform, should be a durable advantage. That kind of sort of segues into Act 4. Mm-hmm of what you guys have been talking about in terms of the agentic web. Can you just maybe as an overview describe to us what's the opportunity for Cloudflare in there? Like, we all understand a lot of agents are being built on Workers. That's part of Act 3. They're more and more, agentic activity taking place. What is the, like, the new monetizable opportunity for Cloudflare in this Act 4? Well, you know, in the near term, it's actually that opportunity and getting ready to monetize a world of agentic AI workflows and content is actually driving business into the older acts first. You know, today about, I would say 80% of the 50 top AI native companies is behind our network and they need to secure, they need to mitigate traffic and requests. That's driving business. We see tailwind from verticals that we weren't traditionally strong in, especially media content creators, publishers that now want their content to behind a network where they can control how it's monetized. In the first step, it's, you know, the opportunity of Act 4 is literally driving business in Act 1 and Act 2 in the first place. We've seen this as part of the acceleration in the last year, and we'll see more in 26. Act 4 moves us into the world, how is content monetized? How do we sit between frontier models and content and give both sides the opportunity to monetize? There will be agentic AI workflows that do business on each other's behalf or on your behalf with microtransactions. How do we build the trails in order to facilitate that? That's why you hear us talking and partnering with pretty much every large payment provider, whether it's the credit card companies, whether it's PayPal or Coinbase. We talked about putting our own stablecoin in place in order to facilitate that. How that is gonna play out in detail, I think there are a lot of questions still that need to be answered. We are making really good progress building an ecosystem and building the rails that need to enable that. Got it. Excellent. You guys talked about AI traffic, already ramping up- Yeah ... on the platform. I think you made a comment about in January of 2026, weekly AI agent requests more than doubled- Yeah on your network. A lot of investors, Claude b ot was a good case in point, had made the connection of, like, this is a lot of API calls, right? Yeah. Which is kind of Act 1 in application services. This is a lot of network traffic to be secured. Where are we in terms of sort of yes, there's a doubling, but from a very small base, where are we on that evolution of when this agentic traffic gets to a volume that it's material for your business, that it becomes a more material driver of Act 1 and Act 2? I think we're in the early innings. You know, today, I would say slightly north of 50% of the traffic in our network is API-driven, but most of it is human-initiated. As you said, in the first six weeks of this year, we saw agent-driven traffic really go through the roof, double literally over a very short period of time. You know, from how we handle a request, it really doesn't matter whether it's a human request or a machine-driven request. Most of our requests are priced in terms of, Phil always makes a good comparison in T-shirt sizes. You're the customer, you buy an M T-shirt that gives you 40 million requests, and as you approach the cap, you buy the next size T-shirt. There is a lag and a step up before you see revenue materialize. It's a lagging, I think, indicator. We're coming from a small base, but the slope of the increase is staggering. I think if you asked me six months ago if that is even close to possible, I would have said no, but staggering. Got it. If we think about the unit economics, if you will, of the AI and autonomous agent traffic, it sounds like you guys are neutral, right? It doesn't matter to you whether it's a human-initiated or an agent-initiated. You still feel comfortable with the economics of that core application services business from that rising traffic spike. Yes, we are. I mean, this is the beauty of and the efficiency and the flexibility of that network, that it's able to digest incredible amounts of fluctuations and upsides. I mean, go back to COVID, where traffic literally increased 60% quarter-over-quarter, and we didn't even see a flinch in our network, neither from a performance nor from a capacity. Now, even more important, nor from a gross margin perspective. It's able to digest incredible amounts of swings of traffic. We are highly comfortable that you know, that is what the network is built for and that we can digest that. You know, you've got visibility in what the trends are. We guided CapEx for this year in the widest range we ever guided it, 12%-15%, and the highest on the upside, 15%, not so much because we need more capacity. It's much more a reflection of some of the supply chain pressures we see from a pricing perspective, especially on the memory side. But again, it gives you an idea how flexible the network is. You know, one of the things that always has driven this efficiency in the business model based on the architecture is that we're in this unique position to invest behind demand. You're never in a position where you say, "I have to invest $100 million in GPU capacity hoping that traffic will come." If for whatever reason, you know, traffic would explode in a site in, across the locations in San Francisco, we'd probably be able to double the capacity across all San Francisco locations, generate revenue in these sites before we even pay for the hardware that we put in place. That means that, you know, you're always in this comfortable position that you can follow demand and you're never really investing ahead of it. That is also why over the last year and a half, we spent so much time on really understanding what inference workloads are, how they vary. You know, inference task is not like inference task. How we optimize our hardware stack for that? We can abstract the need for the customer to decide, "I need this capacity, I need this GPU," but to say, "We'll compute it for you. We'll find the cheapest, the most performant way to approach this." Again, it comes back to the architecture of the network. This is why we are so CapEx-efficient, and that's why the absorbability of the network to deal with gigantic fluctuations in traffic is so significant. Got it. I wanna switch gears a little bit and talk about network services, and in particular, Zero Trust and Cloudflare One. This has been, I think a building momentum within the Cloudflare story. Yeah. This is, I think, the part that most aligns with sort of the improving sales productivity, but it's also one of the more competitive environments. There's a lot of areas that Cloudflare is almost a sort of a class of one, right? When we're talking about these application services or Workers. We've talked to several SASE vendors, right, at this conference. How does Cloudflare look to differentiate in that environment where there's, like, more of a competitive environment, there's more of a sort of direct vision from the end user, the CISO, of what they're looking for in these solutions? Yeah. I mean, we are really happy with our SASE development for a couple of reasons. First of all, from a feature performance perspective. You know, we launch products early, and then they feature out over time, and we call this, you know, moving up into the right in whatever Gartner, Forrester quadrant, and we are right there now. What we needed most now over this year in terms of continuing momentum is building out our go-to-market path, partner and channel. That was needed because, you know, from a go-to-market perspective, there was not really a lot of value to be delivered on for the partners on application services, the products are really easy to install. It's really even for, you know, Morgan Stanley would be behind our network within hours, not within days. For Zero Trust, we needed to build out a partner channel strategy, which Mark Anderson successfully did. Our partner-driven revenue share in the fourth quarter was the highest ever. It was 29%, which is really a good proxy for our progress on Zero Trust, because this is what we mainly use the channel for. You know, if you look at our competitors, their channel shares in terms of revenue are significantly higher. We have lots of opportunity to continue to grow. Our win rates are really strong. You know, when we are in consideration, the likelihood that we win is really high. We are happy with the momentum. Of course, SASE for us is not just a product or a suite of products, it's part of a platform. As part of this platform, it is a significant value distribution. We have not been tired to read down the wins we had on even very large and customers in traditional verticals, even over the last earnings calls. Good progress. Last point, it's probably our strongest margin product because it takes advantage of the infrastructure that has been built with what you would call Act 1. You know, the size of the pipes that transport the data is sized on Act 1 for data moving out to the eyeballs. You know, you fill it with traffic coming back with SASE products. It's a high margin product, so we have ample of room to compete. Excellent. It seems to me that in having Mark Anderson engage a partner channel, as well as the evolution of the products, just gives you more credibility as a security vendor, right? It is fundamentally a little bit of a different buyer from Act 1 and definitely from Act 3. What are the customer conversations today like? Are you still convincing them that Cloudflare is a real security vendor, or are we past that point and it's really about how broad can we go with the Cloudflare One platform? I think we have moved far beyond that already. I mean, you know, the largest customer cohorts are the fastest growing customer cohorts. If you, if you, if you just go back to the earnings calls, most of the customers that we read down there are coming from traditional verticals, critical infrastructure verticals. The progress we are making on in with federal customers, not only in the U.S., but also outside with friendly. I think we are beyond that. I think their, the biggest change in their, in the go-to-market transformation, where Mark Anderson really made a difference, is much more in terms of ingraining this enterprise DNA into the sales force and into the Cloudflare culture. We've been quite open, transparent that we were always a product and innovation-driven go-to-market engine, and it needed this DNA change. Last but not least, what I said before, you know, combining that with a highly effective channel strategy. Those two parts were missing. I think he did an incredible job, you know, instilling this into the company. I think we are in the customer conversations, we are beyond what you said. You know, we don't have to convince people anymore that we're a serious player, right? Mark's been on board for about two years. Yeah. Engaged sort of a channel strategy, but to your point, created much more of a enterprise sales motion. You put that together with the breadth of the solution portfolio, and I'm assuming it's those two things coming together that enable something like a $42.5 million ACV deal. Maybe we could just touch on what does that look like? Like what is the customer acquiring from Cloudflare when they're putting that much budget annually behind your company and behind your platform? Well, you know, first of all, I interpret that as a vote of confidence, right? You know, you commit a lot of dollars to a supplier across a very broad range of products. A pool of funds deal, in this case, really means that you can buy every product that is on the offering list. You negotiate a rate card for every product that we have, and then you decide how you use. Well, we talk of course to each other, but you know, how you consume. What it does for us, it makes this product adoption and expansion rather frictionless, right? Literally once you are on our network with a product, every other product and service is very much a mouse click away. You know, this is all it needs. Yeah. Having this rate card already negotiated, the commitment in place, it makes a rather frictionless process in terms of expanding and expanding across our product portfolio. Got it. Pool funds contracts have pretty quickly ramped up. I think you talked about it as about 20% of your ACV. From an investor standpoint, how should we think about the impacts of this new contracting methodology in terms of variability in business model and, and potential more volatility in kind of the revenue run rate? Well, first of all, we should be all excited because, you know, it's large deals and a committed revenue over a period of time. It generated noise, especially in the beginning, especially when an existing customer migrated from a traditional contract into a pool of funds contract. To make this more visible, you know, say you're a customer, you're committed to $10 million a year. Now you sign a pool of funds contract for $40 million over, or $45 million over two years. Of course, you will get better unit pricing because you have a significantly larger commitment. In the first two quarters, you know, while you consume as much as you did before, maybe even slightly more because the unit prices are lower, you have to step. You have a headwind to DNR for a quarter or two, makes forecasting a little bit more tricky. You catch up and you move out of this, you have this Nike swoosh from a revenue perspective, and this is what we have seen last year. Of course, this is only a headwind that you see when you migrate an existing customer into a pool of funds contract. For a new customer, you know, that is just DNR expansion moving forward. It makes my life a little bit, or my team's life a little bit more difficult from an accounting, billing, especially forecasting perspective. Since it's committed dollars over the length of the contract, you know, this is all good news. Of course, both sides have to get used to how you handle that, and I think we are through this now. The forecasting has become much more stable. If you look at across all the pool of funds deals that are in play, we are slightly ahead of linearity. you know, there is good management also from a customer consumption perspective. That's become a rather beneficial instrument to especially grow our large customer cohorts even faster. you know, one of the reasons why DNR improved so significantly over last year. Got it. Got it. I want to turn to gross margins. As a CFO, I have to ask you some margin questions as well. Yeah. You guys are still within that 75%-77% long-term target model. Yeah. We have seen some impacts- Yeah ... on gross margins, and it seems like a lot of this is mix shift from free to paid customers. Yeah. Can you dig into why is that an impact and sort of like, what's the duration of that impact? Is there anything else that we should be aware of from the gross margin perspective, within that, within that time frame? Yeah. Maybe just for background. You know, we have hundreds of thousands of paying customers, we also have millions of free customers. That is an incredible value, to the business model because, you know, if you even go back to Act 1 and read the reasons why we have free customers, gives us threat intelligence diversity. It allows us to consolidate huge amounts of data that makes us an attractive partner if we go to an ISP and say, "Colocate us, and here are the benefits." We have many free customers. The cost to serve these customers, we put into sales and marketing. We always have. That is how we handle it. If such a free customer now decides he or she wants to become a paying customer, the cost to serve the customer move from sales and marketing into cost of revenue, so have an impact on margin. For the overall P&L, doesn't really matter, but you have a shift in margin. What we've seen over the last two quarters is a significant shift of free customers wanting to give us money. It's actually really, really positive. If you look at our paying customer count, it has exploded. Some of them are really micro customers. They might be just, you know, $1 above the threshold, but it means that all the costs move from sales to marketing- Right ... into cross margins on that. That is accounting-wise, it pressures cross margin. Overall, the unit economics, they hold. In addition to that, I don't wanna, you know, be flimsy about this, our developer business, as we talked about it before, is really taking off. The growth rates are significant. Developer product, for Workers, is still below corporate average. We've made significant improvements over the last year in terms of utilization, but it's under the average cost margin, so there's slight pressure. However, the overall unit economics for this product are really, really good because it's significantly cheaper to sell that product. You know, if you look across all four X, they have very different cost margin profiles, but very consistent unit economic margin. One of the lessons we learn now, and, as we go into our investor day later this year, we'll talk more about both sides of that equation. Right. If we just signal and continue to signal cross-margin performance, that will lead to a misallocation of capital. We don't want that, so we have to adjust. I'm gonna try to squeeze in one question from the audience. I'll just shout it out. Let me get the mic on. On the AI front, sounds like everyone's focused on what the AI is gonna write for you now. Yeah. What I care about is the code the AI is gonna write- Yeah. ...pointed Cloudflare would talk about, like, the next five years more code written than any. Yeah. How do you capture that code, which is the next workload that is coming to you? A couple of ways. You know, I think if you go back to our blog post from last week, you know, we wrote a big piece of software in a week with one developer, and they're whatever, less than $1,000 of tokens. I think that gives you an idea. I think it monetizes in a couple of ways. First of all, it just increases traffic through the network in a very gigantic way. The traffic continues to be secured, needs to be moved, needs to be controlled, so we become this control plane for that traffic that is going to explode. These agents will do business switches with each other. We will find ways as part of Act 4 to monetize that, so clearly. Then, you know, the biggest advantage, I think, of the developer growth that I've seen so far is it gives us insight into how inference tasks are going to develop moving forward. The variety of things that are happening is so impressive, but it gives us this unique opportunity, forget dollars for a moment, to optimize our hardware stack better than anybody else in the direction of how we run workloads on our network. That's the reason why our CapEx is so low. I think there are more than one benefit to what you described. I think the flywheel around this is gonna be a significant tailwind to our business. It's one of the reasons why we think agent, agentic AI is such a multiplier to our infrastructure. Outstanding. Yeah. It's a great note to end on. Thomas, thank you so much for joining me. Thank you, Keith. The team. Always. Thank you.