Introduction
Content delivery networks have evolved far beyond their original purpose of caching static files closer to users. Today's CDNs are full application delivery platforms that handle security, compute, routing, and optimization — often serving as the primary interface between users and your infrastructure.
This evolution raises a fundamental architectural question: is a CDN a feature of your cloud provider, or is your cloud a feature of your CDN?
Cloudflare, AWS CloudFront, Azure CDN (and its successor Azure Front Door), and Google Cloud CDN represent four distinct answers to this question. Each reflects a different philosophy about where intelligence should live in the stack, how security should be integrated, and what you should pay for.
This comparison goes beyond feature checklists. We will examine the architectural decisions that make each platform fundamentally different — and why those differences compound as you build on top of them.
Pricing changes. AWS introduced CloudFront flat-rate plans on 18 November 2025 alongside pay-as-you-go pricing; see the AWS launch announcement and current plan documentation. The workloads below show quantities to enter into current vendor calculators, not price quotes.
Architecture and Network Design
These CDNs differ in network architecture, integrations and pricing. The effect on performance depends on the workload and where users and origins are located.
Cloudflare: Integrated CDN and Security Platform
Cloudflare operates an anycast network and offers caching, security and Workers on its platform. See Cloudflare's current network documentation for its published coverage figures. The architecture also supports optional tiered caching, so a cache miss can involve another cache location before reaching the origin.
Cloudflare can apply caching, DDoS mitigation, WAF inspection, TLS termination and Workers logic to proxied requests. The path and enabled features depend on configuration; the pricing information here does not establish a latency or reliability advantage over the other providers.
For dynamic content, Argo Smart Routing is an optional routing feature. Measure its effect with your own traffic and origins.
Cloudflare offers CDN, WAF and DDoS protection, and compute through a closely integrated platform.
AWS CloudFront: Two-Tier Cache Hierarchy
CloudFront uses edge locations and regional edge caches. See AWS's current network information for published coverage. Edge locations handle initial request processing and cache hits; some misses can route through regional edge caches before reaching the origin. This hierarchy can reduce origin load.
CloudFront's architecture is deeply integrated with the AWS ecosystem. Eligible AWS origins can have favorable transfer terms; check AWS's current CloudFront pricing for the applicable services and conditions. Origin groups provide failover between primary and secondary origins, and Origin Access Control (OAC) can restrict S3 access to CloudFront.
The architecture assumes your origin lives in AWS. While CloudFront supports custom (non-AWS) origins, the deepest integrations and cost benefits are reserved for AWS-native workloads.
Azure CDN / Azure Front Door: Convergence in Progress
Azure CDN included legacy Microsoft, Verizon/Edgio and Akamai offerings. Their availability and migration paths differ. In particular, Microsoft stopped new domain onboarding and profile creation for Azure CDN Standard from Microsoft (classic) in August 2025 and lists its retirement for September 2027. See the current Azure Front Door and CDN comparison before planning a deployment or migration.
Azure Front Door is Microsoft's strategic direction. Front Door Standard and Premium combine global HTTP load balancing, CDN caching and security features, with capabilities varying by tier. It operates on Microsoft's global network; see current service documentation for coverage and feature availability.
Front Door Premium offers Private Link origin support, enabling private backend connectivity for supported origins. For enterprises already running on Azure, Front Door integrates with services such as App Service and Azure Storage.
Older documentation and tutorials may refer to retired or retiring Azure CDN tiers. For new deployments, evaluate Front Door Standard or Premium and check Microsoft's current service guidance.
Google Cloud CDN: Coupled to the Load Balancer
Google Cloud CDN is architecturally inseparable from Google's global external HTTP(S) Load Balancer. You do not configure Cloud CDN independently — you enable it as a property of your load balancer backend. This tight coupling means you get CDN caching, health checking, and traffic distribution from a single configuration surface, but it also means you cannot use Cloud CDN without using Google's load balancer.
Google Cloud CDN uses Google's global network. Google publishes cache locations rather than a single PoP total on its Cloud CDN product page, so this comparison does not use an unsourced headline count. Network size alone does not establish application performance.
For streaming and media workloads, Google offers Media CDN as a separate product, built specifically for high-throughput video delivery with features like prefetching and token authentication.
Google lists Service Extensions plugins for custom edge logic with Cloud CDN. Compare their capabilities and execution model with Cloudflare Workers and CloudFront Functions before choosing an edge runtime.
Content Delivery Capabilities
Beyond architecture, the practical capabilities of each CDN determine what you can build and how much operational work is required.
| Capability | Cloudflare | CloudFront | Azure Front Door | Google Cloud CDN |
|---|---|---|---|---|
| Points of presence | See current network documentation | See current network documentation | See current network documentation | See current network documentation |
| Cache hierarchy | Edge cache; optional Tiered Cache | Edge + regional caches | Edge caching | Edge caching |
| Cache purge speed | See current purge documentation | See current invalidation documentation | See current purge documentation | See current invalidation documentation |
| Cache key customization | Comprehensive (headers, cookies, query strings, device type) | Cache policies (headers, cookies, query strings) | Route-based rules | Cache key policy |
| WebSocket support | Yes; check plan terms | Yes | Yes | Via global external Application Load Balancer; traffic is not cacheable |
| HTTP/3 QUIC | Yes (default) | Yes | Yes | Yes |
| Image optimization | Polish, Mirage and Images transformations; check current plan terms | Can be built with AWS services | Check current product features | Edge image optimization (preview) |
| Edge compute | Workers (V8 isolates) | Lambda@Edge + CloudFront Functions | Rules Engine | Service Extensions plugins; compare runtime capabilities |
| Video streaming | Stream (separate product) | Via S3 + MediaConvert | Front Door can deliver video streams; encoding and other media workflows need separate services | Media CDN (separate product) |
| Origin shielding | Tiered Cache available | Regional edge caches | Check current features | Check current features |
| Brotli compression | Automatic | Configurable | Configurable | Configurable |
Google documents WebSocket traffic through a global external Application Load Balancer; those connections are not cacheable by Cloud CDN. The same product comparison lists Service Extensions plugins for custom edge logic.
Cache purge speed matters when applications require fresh content quickly. Published figures use different methods and conditions; test invalidation behavior for the assets and locations that matter to you.
Image optimization options differ. Cloudflare offers Polish and Mirage on eligible plans; check current Images pricing and allowances. On AWS, image transformation can be built with AWS services or a third-party service. Google documents Cloud CDN edge image optimization in preview. Compare feature status and delivery costs for your use case.
Microsoft documents video delivery with Azure Front Door. Azure Media Services, previously used for media workflows, retired on June 30, 2024.
Security Features
Security features are bundled differently across providers and plans. Compare the specific protections, configuration and charges your application needs.
DDoS Protection
Check current vendor pricing and plan terms for applicable rates, allowances and commitments.
| Provider | Offering | Cost factors | Current terms |
|---|---|---|---|
| Cloudflare | Plan-dependent DDoS protection | Plan fee and service terms | Cloudflare plans |
| AWS | Shield Standard and CloudFront plans | Included protections vary by service and plan | AWS Shield pricing and CloudFront plans |
| AWS | Shield Advanced | Subscription, commitment and eligible usage charges | AWS Shield pricing |
| Azure | DDoS IP and Network Protection | Protected resources and plan charges | Azure DDoS pricing |
| Cloud Armor Enterprise | Subscription or usage charges and protected resources | Cloud Armor pricing |
Azure DDoS pricing note. Use the current Azure pricing calculator for your region and protected resources before budgeting.
These offerings differ in scope as well as price. Cloudflare includes DDoS protection in its standard plans, and AWS bundles DDoS protection into CloudFront flat-rate plans. Enterprise tiers may add response services and commitments. Check current terms before comparing protection levels.
Web Application Firewall (WAF)
Check current vendor pricing pages and plan terms for rule allowances and usage charges.
| Provider | Offering | Cost factors and current pricing |
|---|---|---|
| Cloudflare | Managed WAF rulesets | Plan-dependent features; see Cloudflare plans |
| AWS CloudFront flat plans | Bundled WAF rule allowance | Allowance depends on plan; see CloudFront plans |
| AWS WAF (standalone) | Custom and managed rules | Web ACL, rule and request charges can apply; see AWS WAF pricing |
| Azure WAF | Managed rules on Front Door | Plan-dependent features; see Front Door pricing |
| Google Cloud Armor Standard | Security policies and rules | Policy, rule and request charges can apply; see Cloud Armor pricing |
Cloudflare includes some WAF features in plan pricing, and AWS includes a WAF rule allowance in CloudFront flat-rate plans. Standalone AWS WAF and Google Cloud Armor Standard have usage-based components; Azure Front Door Premium bundles WAF. Compare rule requirements, coverage and current fees for your workload.
Bot Management
Cloudflare offers Super Bot Fight Mode and Bot Management on eligible plans. Its detection quality relative to competing products cannot be inferred from network size or pricing alone.
For standalone/pay-as-you-go AWS WAF, Bot Control can have separate monthly and request-based charges. CloudFront flat plans have plan-dependent bot protections; compare included capabilities with standalone Bot Control. Check Azure Front Door pricing for CAPTCHA charges and Google Cloud Armor pricing for bot-management and reCAPTCHA charges.
Pricing Models
Pricing reveals more about a CDN's strategy than any technical specification.
CloudFront flat-rate plans, introduced in November 2025
AWS introduced flat monthly CloudFront plans on 18 November 2025 alongside pay-as-you-go pricing. The February 2026 version of this article omitted those plans. Compare the current Free, Pro, Business and Premium tiers on the AWS pricing page and read the plan documentation for allowances, eligibility and sustained-usage terms.
Check both request and transfer allowances: a workload with many small objects can reach a request allowance before its transfer allowance. Also compare the separate pay-as-you-go free tier and any invalidation allowance on the current AWS page; a flat plan is not necessarily the lowest-cost option for a small workload.
Bandwidth Cost Comparison
Flat plans and metered rates have different allowances and billing units. Use current pages for Cloudflare plans, CloudFront, Azure Front Door and Google Cloud CDN. Check regional rates, request charges, cache fill, origin transfer, load balancing and security services. Google quotes some quantities in GiB and TiB, while the workloads below use decimal TB.
Modelled at two realistic traffic levels
Egress and requests both affect CDN cost. Both scenarios assume a 250 KB average delivered object (250,000 bytes) and decimal TB (1 TB = 1,000,000,000,000 bytes). That gives 4 million requests per TB. For Google's GiB-based pricing inputs, 1 GiB = 1,073,741,824 bytes; use the exact conversion or the vendor calculator rather than treating 1 TB as 1 TiB.
Scenario A — 10 TB/month, ~40 million requests. A busy content site or a mid-sized SaaS app.
| Provider | Workload to price | Current pricing |
|---|---|---|
| Cloudflare | 10 TB egress; confirm plan eligibility and applicable services | Plans and terms |
| CloudFront | 10 TB egress and 40 million requests; compare flat-plan allowances with pay-as-you-go | Pricing and plans |
| Google Cloud CDN | 10 TB × 1,000,000,000,000 bytes/TB ÷ 1,073,741,824 bytes/GiB ≈ 9,313 GiB egress; 40 million cache lookups if each request is looked up; at 5% cache fill, about 466 GiB fetched from origin | CDN pricing; add load balancer charges |
| Azure Front Door Standard/Premium | 10 TB egress and 40 million requests; include the applicable base fee and tier features | Front Door pricing |
Scenario B — 100 TB/month, ~400 million requests. A large media or e-commerce property.
| Provider | Workload to price | Current pricing |
|---|---|---|
| Cloudflare | 100 TB egress; confirm plan eligibility and applicable services | Plans and terms |
| Google Cloud CDN | 100 TB × 1,000,000,000,000 bytes/TB ÷ 1,073,741,824 bytes/GiB ≈ 93,132 GiB egress; 400 million cache lookups if each request is looked up; at 5% cache fill, about 4,657 GiB fetched from origin | CDN pricing; add load balancer charges |
| Azure Front Door Standard/Premium | 100 TB egress and 400 million requests; include the applicable base fee and tier features | Front Door pricing |
| CloudFront | 100 TB egress and 400 million requests; compare Premium configuration with pay-as-you-go | Pricing and plans |
At either traffic level, compare request allowances alongside egress. The 5% cache-fill figures are illustrative volumes, not a promise of cache performance or a complete bill. Google also has Cloud Load Balancing charges. Enter the quantities into each vendor's current calculator before comparing totals.
Cloudflare's plan model can simplify CDN bandwidth budgeting for eligible workloads. AWS also offers flat CloudFront plans alongside pay-as-you-go pricing. Compare both vendors' current terms for your traffic mix.
How Is Free Bandwidth Sustainable?
Cloudflare's plan model includes several paid services and features:
- Security services: Plan-dependent WAF, bot management and DDoS features; see current Cloudflare plans
- Compute: Workers, Workers KV, Durable Objects, D1, R2
- Zero Trust: Cloudflare Access, Gateway, WARP
- Enterprise features: Custom SSL, dedicated IPs, premium support, SLAs
Bandwidth remains a cost of operating the network. Cloudflare uses an anycast network and offers optional tiered caching; the economics of its plans and the quality of its security models cannot be established from the CDN price table alone.
Total Cost Considerations
Raw bandwidth cost does not tell the full story. For Scenario A (10 TB, roughly 40 million requests), price the following components using current plan terms.
| Component | Cloudflare | CloudFront | Azure Front Door | Google Cloud CDN + Armor |
|---|---|---|---|---|
| CDN + 10 TB + 40M requests | Check plan terms | Compare flat and metered pricing | Include base, egress and request charges | Include egress, cache and load balancer charges |
| DDoS protection | Check plan coverage | Check CloudFront and Shield coverage | Check platform and optional protection | Check Cloud Armor tier |
| WAF | Check plan features | Check bundled allowance or standalone WAF | Check Standard/Premium features | Include policy, rule and request charges where applicable |
| SSL/TLS | Check certificate terms | Check certificate terms | Check certificate terms | Check certificate and load balancer terms |
| Bot management | Check plan features | Check plan or Bot Control charges | Check CAPTCHA charges | Check Cloud Armor and reCAPTCHA terms |
| Image optimization | Check Images pricing | Can be built with AWS services | Check current product features | Edge image optimization is in preview; check current pricing |
Totals vary with plan eligibility, metered usage, origin charges and optional security services. Recalculate with your own traffic and current vendor pricing.
When Hyperscaler CDN Pricing Makes Sense
The full infrastructure picture can change the cost comparison:
- Your usage fits a flat-rate allowance: Compare CloudFront's current flat plans and pay-as-you-go free tier against both request and transfer volumes.
- AWS-native origins: Check CloudFront pricing for applicable AWS-origin transfer terms and compare those with transfer to another CDN.
- Azure-native origins: Azure Front Door can have favorable origin transfer terms; check current pricing.
- Google-native origins: Check Cloud CDN pricing for origin transfer, cache fill and load balancer charges.
- Existing enterprise agreements: Many enterprises have negotiated committed-use discounts with hyperscalers that significantly reduce published rates.
If your entire stack is on one hyperscaler and you have a negotiated enterprise agreement, the CDN from that provider may be cost-effective even before you factor in operational simplicity of a single vendor.
Calculate Your Costs
Use the calculator below to estimate costs for your specific workload:
Try the interactive Cdn calculatorRun it free on inventivehq.com →Developer Experience
Configuration Complexity
Cloudflare's dashboard is designed for a CDN-first workflow: you add a site, change nameservers, and the CDN is active with sensible defaults. Advanced configuration (Page Rules, Cache Rules, Transform Rules) uses a visual rule builder.
CloudFront configuration involves creating distributions with origin groups, cache behaviors, cache policies, origin request policies, and response headers policies. The mental model requires understanding how these layers interact. Infrastructure-as-code via CloudFormation or Terraform is almost essential for non-trivial setups.
Azure Front Door uses a routing architecture with front-end endpoints, routing rules, and backend pools. The configuration surface is smaller than CloudFront but still assumes familiarity with Azure networking concepts.
Google Cloud CDN is configured through the load balancer, so setup involves Google's networking model (forwarding rules, target proxies, URL maps and backend services). The operational effort depends on your existing infrastructure.
Edge Compute
The edge compute options differ in runtime, execution location and limits:
| Capability | Cloudflare Workers | CloudFront Functions | Lambda@Edge |
|---|---|---|---|
| Runtime | V8 isolates | JavaScript (restricted) | Node.js, Python |
| Cold start | Varies by workload | Varies by workload | Can occur |
| Execution location | Cloudflare edge network | CloudFront edge locations | CloudFront edge locations for viewer events; execution location depends on trigger |
| Execution limit | Check current CPU and wall-clock limits | Check current function limits | Depends on trigger; check current quotas |
| Memory | Check current limits | Check current limits | Check current limits |
| Network access | Full fetch API | No | Full |
| Languages | JS/TS, WASM (Rust, C, Go) | JavaScript | Node.js, Python |
Workers can run applications at the edge; their CPU and wall-clock limits are different measures. CloudFront Functions handle lightweight request/response manipulation (header modification, URL rewrites). Lambda@Edge runs on CloudFront triggers, including viewer events at edge locations, and can have cold starts. Google Cloud CDN and Azure Front Door do not provide a directly comparable general-purpose edge-function runtime.
Observability
Cloudflare provides real-time analytics in the dashboard with GraphQL API access for custom queries. Logpush streams logs to storage or analytics services. Workers Analytics Engine enables custom event tracking at the edge.
CloudFront integrates with CloudWatch for metrics and S3 access logs for detailed request-level data. Real-time logs are available via Kinesis Data Streams. The observability is comprehensive but requires assembling multiple AWS services.
Azure Front Door provides built-in analytics with Azure Monitor integration. Google Cloud CDN metrics flow through Cloud Monitoring with request-level logging available in Cloud Logging.
Decision Framework
Choose Cloudflare When:
- Security is a primary concern and you want integrated DDoS, WAF and bot protection; check plan features and usage charges
- Bandwidth costs are significant or unpredictable — a flat plan fee with no per-GB CDN charge makes budgeting simpler; compare the applicable CloudFront Premium allowance
- You need Workers' runtime or platform integrations — check its limits and latency against your workload
- You use origins across providers — Cloudflare can proxy supported external origins; test the behavior and costs for yours
- You want operational simplicity — single dashboard for CDN + security + compute + DNS
Choose CloudFront When:
- A flat plan fits your traffic — CloudFront Pro, Business, and configurable Premium allowances can change the arithmetic that older comparisons are built on
- Your origin is on AWS — check CloudFront's current origin transfer terms for the services you use
- You need Lambda@Edge for server-side rendering, personalization, or A/B testing at the edge
- Deep AWS integration is required — IAM, ACM, WAF, Shield, and CloudWatch are tightly connected
- You have an existing AWS enterprise agreement with negotiated rates
Choose Azure Front Door When:
- Your infrastructure is on Azure — native integration with App Service, AKS, and Azure Storage
- You need Private Link origins for secure backend connectivity without public endpoints
- Enterprise Microsoft ecosystem — Azure AD integration, compliance certifications, Microsoft support contracts
- Hybrid cloud with on-premises — Azure Front Door works with Azure ExpressRoute and hybrid networking
Choose Google Cloud CDN When:
- Your origin is on GCP — tight integration with the global HTTP(S) load balancer
- Media and streaming workloads — Media CDN is purpose-built for high-throughput video delivery
- You are already using Google's load balancer — Cloud CDN is a checkbox, not a separate service to configure
- You need limited custom edge logic — evaluate Service Extensions plugins and their current capabilities
The Bigger Picture
The CDN market offers different combinations of edge caching, security, compute and integration with regional cloud services. Each provider's feature set and execution locations depend on the product and plan.
The better fit depends on user locations, origins, caching behavior, security requirements and the rest of your stack. Measure performance and total cost with a representative workload.
If your stack is on one hyperscaler, its CDN may simplify integration and origin billing. If you use multiple origins or need specific security and edge compute features, compare the providers against those requirements and measure the result.
Understanding these architectural differences is more valuable than memorizing feature comparisons. The features change quarterly. The architectural philosophies change over decades.
AWS launched CloudFront flat-rate plans in November 2025; the earlier version of this article missed them. Before committing a budget, check each vendor's current pricing page and enter your own traffic and request counts into its calculator. Request allowances, configurable Premium allowances and separate load balancer charges can all change the result of a per-TB comparison.
