How Cloudflare Makes its Money: Revenue Breakdown (FY2024)

How Does Cloudflare Make its Money?

Cloudflare Inc. (NYSE: NET) generated $1.665 billion in total revenue in FY2024 — up +27% year-over-year — by operating a proprietary global network spanning 330+ data centers in 120+ countries that delivers web security, performance, reliability, and increasingly, compute services as a subscription. Cloudflare charges businesses a recurring monthly or annual fee to route their internet traffic through Cloudflare’s network, where it is protected from attacks (DDoS, bots, SQL injection), accelerated via caching and smart routing, and increasingly processed at the edge (serverless compute, AI inference, databases).

Cloudflare started in 2010 as a CDN and DDoS protection service used by hundreds of thousands of small websites on a freemium model. It has expanded into an extraordinarily broad platform: Zero Trust / SASE security (replacing corporate VPNs), network infrastructure (SD-WAN, Magic Transit), a developer compute platform (Workers, R2, D1, Pages), email security, and AI services. No other company in the industry occupies the same breadth — Cloudflare competes simultaneously with Akamai (CDN), Zscaler (zero trust), AWS (compute), and Palo Alto Networks (enterprise security), while building a developer ecosystem that resembles AWS in its early cloud transition.

FY2024 was a strong year operationally: revenue grew +27%, large customer count ($100K+ ARR) grew +27% to 3,782, and Cloudflare crossed key profitability milestones — generating positive free cash flow for the full year and narrowing its GAAP operating loss to near-breakeven (-$0.08B). The company guided for FY2025 revenue of approximately $2.09B (another ~26% growth year), demonstrating sustained demand for its security and network services.

Key Takeaways

• Cloudflare generated $1.665B in FY2024 revenue (+27% YoY) with a 76.8% gross margin — exceptional for a company that owns and operates its own physical global network hardware rather than renting hyperscaler infrastructure
• Network-as-a-service model: Cloudflare charges for traffic throughput, connections, and services delivered over its proprietary global network; this is fundamentally different from pure SaaS because Cloudflare has real network infrastructure costs — but its programmable, multi-purpose network creates structural margin advantages as utilization scales
• 3,782 large customers ($100K+ ARR), up +27% YoY — the key growth metric; large customers have proven sticky, multi-product, and have significantly higher NDR than the overall book; large customer ARR is the health indicator Cloudflare management tracks most closely
• Net Dollar Retention (NDR) of 110% — slightly compressing from 115% (FY2023) and 127% (FY2021 peak) as Cloudflare’s customer base matures and cohort expansion normalizes; still positive (customers collectively expand spend year-over-year), but the trend bears watching
• Zero Trust / SASE is the largest near-term growth driver — Cloudflare’s One platform (replacing corporate VPNs, firewalls, web proxies) is winning enterprise deals and now represents a significant portion of large customer expansions; the TAM for SASE is estimated at $80B+ by 2027
• Workers / Developer Platform is the long-duration bet — Cloudflare’s edge compute platform (Workers serverless, R2 storage, D1 database) is positioned as a challenger to AWS Lambda / Vercel; growing rapidly among developers but not yet material to revenue; if it scales, it redefines Cloudflare’s TAM from security to cloud compute
• AI inference at the edge is the newest growth vector — Cloudflare’s global network positioning (330+ PoPs near users) is architecturally ideal for low-latency AI inference; Workers AI and AI Gateway are attracting developer experimentation; this could be a significant revenue driver in 2025–2027

Cloudflare (NET) Business Model

Cloudflare operates as a network-as-a-service platform monetized through subscription and usage-based pricing. For how subscription and usage-based SaaS models work, see the Usage-Based Business Model and SaaS Business Model.

What Cloudflare sells and how it prices it:

Cloudflare’s pricing has three tiers:

1. Free tier — Cloudflare has always offered a free plan for personal websites and developers. This builds the developer community, generates network traffic (which trains Cloudflare’s machine learning models for threat detection), and creates bottom-up enterprise adoption (developers who use Cloudflare personally bring it to their employers). Free users are not a revenue source — they are a product investment and a marketing channel
2. Self-serve / SMB — Pro ($20/month), Business ($200/month), and usage-based add-ons for additional bandwidth, workers invocations, and R2 storage. These customers are acquired through the website with no sales touch; high gross margin, lower ARPU
3. Enterprise contracts — custom pricing, multi-product bundles, dedicated support, SLAs; enterprise deals often start with a single product (WAF, CDN, or Zero Trust Access) and expand as security teams consolidate vendors onto Cloudflare’s platform

The network flywheel — Cloudflare’s structural advantage:

Cloudflare operates 330+ data centers globally, peered directly with thousands of ISPs and networks. When a business routes traffic through Cloudflare, that traffic is protected and accelerated without leaving Cloudflare’s network until the final “last mile” to the origin server. This architecture provides three compounding advantages:

1. Performance — traffic is served from a PoP (Point of Presence) near the user, reducing latency; caching stores content at the edge so origin servers are hit less frequently
2. Security at scale — because Cloudflare sees traffic from millions of websites and billions of users, its machine learning threat detection improves with every new attack observed on any customer; protecting one customer makes all customers safer; this “network effect on security intelligence” is a genuine moat that pure-play endpoint security vendors don’t possess
3. Marginal cost economics — building a new data center costs real capex, but once built, adding the next customer costs near-zero incremental network capacity; as the network grows more utilized, fixed infrastructure costs are spread over more revenue, driving gross margin expansion over time

Why 76%+ gross margin despite owning hardware:

Pure SaaS companies typically hit 75–80% gross margins by avoiding infrastructure costs — they rent compute from AWS/Azure/GCP. Cloudflare owns its hardware but still achieves 76%+ gross margins because: (a) traffic costs are relatively low vs. revenue per customer; (b) Cloudflare’s global network was largely built in prior years and depreciation flows through cost of goods gradually; (c) as utilization improves (more customers on the same network), incremental revenue carries near-zero incremental cost. Long-term, as the network matures and utilization rises, Cloudflare’s gross margin has the potential to improve toward 80%+.

How Zero Trust / SASE works and why enterprises pay for it:

Traditional corporate security was built on a “castle-and-moat” model: put all company resources inside a corporate network (behind a firewall), and verify users’ identities when they enter the network (via VPN). This model has collapsed in a world where employees work remotely, applications live in the cloud (not the corporate data center), and attackers can bypass perimeter defenses via phishing.

Zero Trust replaces this with: verify every user, every device, every application access request, regardless of network location. Cloudflare One delivers this via:

• Access — identity-aware proxy that replaces VPN; users authenticate through SSO (Okta, Azure AD) before accessing any internal application, from any network
• Gateway — DNS and HTTP filtering that blocks malicious content before it reaches user devices; replaces traditional secure web gateways
• WARP — device agent that routes all traffic through Cloudflare’s network for inspection and policy enforcement
• CASB — Cloud Access Security Broker; monitors and enforces policies on SaaS applications (Google Workspace, Microsoft 365)
• Email Security — advanced phishing and malware detection for email (acquired Area 1 Security in 2022 for $162M)

Enterprise security teams pay Cloudflare because: consolidating onto a single vendor platform reduces cost vs. buying point solutions from 5–10 vendors; Cloudflare’s network performance advantage means Zero Trust doesn’t degrade user experience (a common complaint with legacy VPNs); and Cloudflare’s integrated platform creates less complexity than managing multiple security vendors.

Cloudflare Competitors

CDN and application security:

• Akamai — the original CDN leader; larger revenue ($3.8B) but slower-growing; competes directly on CDN, WAF, DDoS protection, and bot management; Akamai is acquiring Guardicore (microsegmentation) and building zero trust capabilities but is seen as slower to innovate than Cloudflare; Cloudflare has been taking CDN market share from Akamai for years
• Fastly — edge CDN and compute platform; once positioned as a developer-friendly Akamai alternative; has struggled with revenue growth and customer concentration (TikTok was a massive customer); competes with Cloudflare on CDN and edge compute (Compute@Edge vs. Workers)

Zero Trust / SASE:

• Zscaler — the largest pure-play zero trust company (~$2.2B revenue); competes directly with Cloudflare One on SASE/zero trust architecture; Zscaler is proxy-based (all traffic routes through Zscaler’s cloud); Cloudflare’s network-native approach argues for better performance; these two are the primary enterprise SASE competitors
• Palo Alto Networks — the largest cybersecurity company (~$8B revenue); offers SASE via Prisma Access and is building a comprehensive platform strategy (platformization, similar to Cloudflare’s approach but from a firewall/endpoint heritage); competes with Cloudflare on enterprise SASE deals
• CrowdStrike — competes primarily in endpoint security/XDR but is expanding into identity security and SASE; CrowdStrike + Cloudflare can be complementary (endpoint detection vs. network security) but are beginning to overlap

Developer platform / edge compute:

• Amazon Web Services — AWS Lambda (serverless compute), CloudFront (CDN), S3 (object storage) compete with Cloudflare Workers, Pages, and R2; AWS’s advantage is ecosystem depth and enterprise relationships; Cloudflare’s advantage is performance (edge deployment vs. AWS regional data centers) and cost (R2 has zero egress fees vs. AWS S3’s expensive egress pricing)
• Microsoft Azure — Azure CDN, Front Door, and security services compete with Cloudflare’s application and network services; Microsoft’s enterprise relationships are formidable but Cloudflare wins on developer experience and edge performance

For security sector context, see CrowdStrike vs Palo Alto Networks and Palantir vs Snowflake for enterprise software growth benchmarking.

Revenue Breakdown

Cloudflare reports as a single segment — all products (CDN, Zero Trust, Developer Platform, Network Services) are bundled into one revenue line. This reflects the company’s strategic intent: customers buy Cloudflare’s network, not individual products. Disaggregation between product lines is not publicly available, but based on customer conversation disclosures, analyst estimates, and Cloudflare’s own cohort commentary:

Note: Product-level revenue is not disclosed by Cloudflare. Estimates above are based on public commentary and analyst models.

Financial data sourced from Cloudflare FY2024 Annual Report (10-K).

Revenue by Customer Size

The large customer metric is the most important number in Cloudflare’s business. Large customers ($100K+ ARR) represent ~3.6% of Cloudflare’s total customer count but approximately 68% of revenue. They expand aggressively (adding new products from the Cloudflare platform), have lower churn than SMB customers, and require dedicated enterprise sales resources that Cloudflare has been scaling. Large customer count growing +27% means the enterprise business is accelerating — a positive mix shift toward higher-ARPU, more durable revenue.

NDR compressing from 122% → 115% → 110%: Net Dollar Retention measures how much existing customers expand their spend year-over-year. At 110%, Cloudflare’s customer base collectively grows 10% even with zero new customers — still excellent. But the trend from 127% (FY2021 peak) to 110% reflects: (a) natural maturation as the customer base grows larger and earlier cohorts become harder to expand; (b) macro headwinds (2022–2023 enterprise software budget scrutiny); (c) Cloudflare’s customer mix shifting toward larger enterprises (who expand more deliberately than SMBs). Stabilizing NDR at 110–112% would be a healthy signal; further compression below 108% would indicate customer expansion challenges.

Revenue Trend (3-Year)

Revenue growth is decelerating (48.8% → 32% → 27%) as the law of large numbers applies — growing a $1.7B business at 27% is more challenging than growing a $1B business at 48%. However, 27% growth at Cloudflare’s scale is exceptional for a security/network company. Gross margin is stable and slightly improving (74.7% → 76.8%), and operating margin has improved dramatically (from -21% to near-breakeven at -4.8%) as revenue scales against a more controlled cost base. FCF positivity is a key milestone — it means Cloudflare is self-funding growth, not burning cash from operations.

Cloudflare (NET) Income Statement

Financial data sourced from Cloudflare SEC filings.

Key observation: Cloudflare’s net loss of -$16M in FY2024 nearly rounds to breakeven. Interest income of $130M on Cloudflare’s cash/investment balances is now large enough to nearly offset the operating loss — meaning Cloudflare is operationally close to GAAP profitability. At FY2025’s guided revenue (~$2.09B) and continued operating leverage, Cloudflare is likely to reach GAAP operating income breakeven.

Sales & Marketing at 42% of revenue: This is high, reflecting Cloudflare’s aggressive enterprise sales buildout. As enterprise deals grow (bigger ACVs, longer contracts), the S&M % of revenue should gradually improve — but Cloudflare must keep investing here to capture zero trust and SASE enterprise budgets before competitors consolidate those relationships.

Key Financial Metrics

• Gross Margin: 76.8% — Exceptional given Cloudflare operates physical network hardware across 330+ global data centers. Most hardware-dependent infrastructure companies run 50–65% gross margins; Cloudflare’s 76.8% reflects strong pricing power for its security/performance services and the marginal-cost economics of its network (incremental customers cost near-zero to serve on existing infrastructure). The long-term trajectory should improve toward 80% as network utilization increases

• Operating Margin: -4.8% — Near breakeven and improving rapidly (+16 percentage points from FY2022’s -21%). The path to consistent GAAP operating profitability is clear at current growth rates: as revenue grows +25–30% annually on a moderately growing cost base, operating leverage drives the margin to positive territory within 1–2 years. Management has indicated a target of ~20% non-GAAP operating margin at scale

• Operating Leverage — Cloudflare’s business model has substantial operating leverage: the network infrastructure is largely built; R&D costs develop products that serve millions of customers without proportional headcount scaling; G&A is relatively fixed. Sales & Marketing is the primary variable cost that scales with revenue. As enterprise deals grow in ACV (reducing the number of deals needed per dollar of revenue), S&M efficiency should improve. Every 1 point of S&M efficiency improvement translates to ~1 point of operating margin expansion

• Free Cash Flow — Cloudflare achieved positive FCF in FY2024 (~6–8% FCF margin, approximately $100–130M). This is an important milestone: FCF-positive means Cloudflare’s cash generation from operations covers capital expenditure, and the company is not diluting shareholders to fund operating losses. Capex (network expansion, server purchases) runs approximately $150–200M annually — below the growth capex levels of hyperscale cloud providers because Cloudflare’s architecture is efficient in hardware utilization

• Stock-Based Compensation: ~$430M — approximately 26% of revenue; extremely elevated relative to revenue, reflecting the talent competition for security, network, and systems engineering expertise; SBC as a % of revenue has been declining (it was 38%+ of revenue in FY2022) but remains a significant gap between GAAP results and non-GAAP adjusted metrics; non-GAAP operating margin (excluding SBC) is approximately 18–20%, which is the metric management and many investors focus on

• Net Dollar Retention: 110% — Measures how existing customers collectively expand spending; at 110%, the existing customer base grows 10% even with no new customer additions; this “compounding base” dynamic means Cloudflare’s revenue growth is partially structural (existing customers expanding) rather than entirely dependent on new customer acquisition; healthy but compressing

Is Cloudflare Profitable?

On a GAAP basis: barely not — Cloudflare reported a net loss of $16 million in FY2024, essentially breakeven. On a non-GAAP basis (excluding $430M+ of stock-based compensation): Cloudflare is meaningfully profitable, generating approximately 18–20% non-GAAP operating margins. On a cash basis: FCF-positive in FY2024 — a milestone reached for the first time, meaning cash generation from operations covered capital expenditure.

The GAAP profitability journey is nearly complete. At ~$2.1B in FY2025 revenue (Cloudflare’s own guidance), even modest operating leverage will drive the operating loss to zero or positive. The richer debate is about the quality and sustainability of Cloudflare’s profitability model: is the 76%+ gross margin durable as compute costs and network expansion continue? Can S&M efficiency improve as enterprise deals grow? And does Workers/developer platform expansion eventually dilute margins (compute-heavy workloads cost more to serve than security subscriptions)?

Cloudflare Workers: The Long-Duration Edge Compute Bet

Cloudflare Workers launched in 2017 as a serverless execution environment running JavaScript at the edge — in Cloudflare’s 330+ global PoPs, near the user, rather than in a centralized AWS region. Workers has since expanded into a full developer platform:

• Workers — serverless functions running at the edge; V8 isolates (not traditional containers) that start in microseconds; priced by requests and CPU time; competing with AWS Lambda and Vercel Functions
• R2 — S3-compatible object storage with zero egress fees — the most developer-friendly pricing differentiation against AWS S3, which charges $0.09/GB for egress; R2 egress is free, making it dramatically cheaper for data-heavy applications
• D1 — SQLite-compatible distributed database running at the edge; enables full-stack applications (frontend + API + database) entirely within Cloudflare’s platform
• Pages — static site hosting and JAMstack deployment; competing with Vercel and Netlify
• Workers AI — inference-at-the-edge using Cloudflare’s GPU hardware in its global PoPs; run ML models (LLaMA, Whisper, Stable Diffusion) with ultra-low latency from any location; competing with replicate, Modal, and cloud provider inference APIs
• AI Gateway — rate limiting, caching, observability, and routing layer for AI API calls (OpenAI, Anthropic, Hugging Face, etc.); developer tool for managing AI API usage; no comparable product exists at Cloudflare’s network layer

Why Workers matters strategically: If Cloudflare’s developer platform becomes the default edge compute choice for new applications, Cloudflare’s relationship with those customers becomes extremely deep and sticky — not just a CDN/security vendor, but the compute and data infrastructure. This is the AWS dynamic: once workloads run on Workers, they’re difficult to migrate because the architecture is designed around Cloudflare’s edge compute model. Workers represents Cloudflare’s ambition to expand its TAM from security/networking (~$80–100B) to cloud compute (~$700B+).

What to Watch

1. Large customer ($100K+ ARR) growth rate — The single most important operating metric. At 3,782 large customers growing +27% YoY, each incremental large customer adds significant multi-year revenue potential. Track whether this growth rate holds at 25%+ in FY2025 (implying ~4,700 large customers by year-end). Deceleration below 20% would signal enterprise pipeline challenges; acceleration above 30% would be highly positive

2. Net Dollar Retention stabilization — NDR has compressed from 127% → 122% → 115% → 110% over four years. The question is whether it stabilizes around 110% (healthy enterprise expansion base) or continues toward 105% (indicating expansion headwinds). Watch particularly whether Zero Trust platform expansions (adding multiple products per enterprise customer) can arrest the compression trend

3. Zero Trust / SASE enterprise deal wins — Cloudflare competes head-to-head with Zscaler and Palo Alto Networks for 7-8 figure enterprise SASE contracts. Reference customer wins at Fortune 500 scale (with disclosed ACV), replacements of incumbent Zscaler or VPN deployments, and management commentary on deal size inflation are the key signals. A large customer win (e.g., 50,000+ seat deployment) validates Cloudflare’s enterprise readiness for the largest organizations

4. Workers / R2 developer platform revenue scale — Management has indicated that the developer platform (Workers, R2, D1, Pages) is growing faster than the company overall in percentage terms. At some point, Cloudflare will likely disclose revenue or ARR for this segment specifically — that disclosure (and whether it represents a material fraction of total revenue) will clarify whether the long-duration compute bet is on track

5. GAAP operating income breakeven — At FY2025 guided revenue of ~$2.09B and modest operating cost discipline, Cloudflare should approach or achieve GAAP operating income breakeven. This milestone matters for institutional investor universe expansion (many index funds and value-oriented institutions avoid unprofitable technology companies); crossing into consistent GAAP profitability could be a re-rating catalyst

6. AI Gateway and Workers AI traction — As AI API usage scales in enterprise and developer workflows, Cloudflare’s AI Gateway (observability, caching, routing for AI API calls) and Workers AI (edge inference) are positioned in high-demand workflows. Track developer sign-ups, usage metrics disclosed at investor days, and whether any large AI-native company (not yet disclosed) becomes a top-10 Cloudflare customer as an AI infrastructure customer

Cloudflare (NET) Financial Summary

Cloudflare (NYSE: NET) generated $1.665 billion in total revenue in FY2024, up +27%, with a 76.8% gross margin — exceptional for a company owning 330+ global data centers. The company achieved positive free cash flow for the first time and reduced its GAAP net loss to -$16M (essentially breakeven). Large customers ($100K+ ARR) grew +27% to 3,782, representing ~68% of total revenue and validating the enterprise platform expansion strategy. The business model — a programmable global network monetized through security, performance, and compute services — creates structural operating leverage: incremental customers cost near-zero to serve on the existing infrastructure, and multi-product platform adoption (Zero Trust + CDN + Workers) makes customers extremely sticky. The key strategic bets for the next five years: winning the SASE/Zero Trust enterprise consolidation from Zscaler and Palo Alto Networks, and establishing Workers as the default edge compute platform for the developer ecosystem.

For security industry context, see the Cybersecurity Sector analysis and CrowdStrike vs Palo Alto Networks. For enterprise cloud growth benchmarking, see Palantir vs Snowflake.