Comparison

Updated October 25, 2026

· ~3 min read

CloudFront vs Cloudflare in 2026: Flat-Rate Plans, WAF, Edge Compute and Where Each Fits

CloudFront
Cloudflare
CDN
AWS WAF
Pricing

For years the comparison was easy to summarize: Cloudflare was a flat monthly price with security bundled, CloudFront was metered and WAF cost extra. In November 2025 AWS launched CloudFront flat-rate plans. Free, Pro ($15), Business ($200) and Premium ($1,000) a month bundle the CDN, AWS WAF, DDoS protection, bot management, Route 53 DNS, log ingestion and S3 storage credits, with no overage charges.

That makes this a closer call than it used to be. Price is now similar at the low end. What separates the two is where your origin lives, what else you want from the edge, and who on the team will run it.

Plans side by side

CloudFront flat-rate

Cloudflare

Free

$0: 1M requests, 100 GB transfer, 5 GB S3 credit

$0: CDN and DDoS protection, no bandwidth meter

Entry paid

Pro $15/month: 10M requests, 50 TB

Pro $20/month billed annually, $25 monthly

Business

$200/month: 125M requests, 50 TB

$200/month billed annually, $250 monthly

Top self-serve

Premium $1,000/month: 500M requests, 50 TB, configurable to 6B requests and 600 TB for $10,000

Enterprise, custom pricing

Billed per

Distribution, one apex domain per plan

Zone (domain)

Overage

None. Sustained excess over 2–3 months may see delivery adjusted unless you upgrade

None on bandwidth for the CDN

Attack traffic

Blocked DDoS and WAF-blocked requests do not count toward the allowance

Unmetered DDoS mitigation on all plans

What the CloudFront plans include, and what they exclude

Every plan includes AWS WAF with managed rules and IP rate limiting, geo-blocking, a TLS certificate, Route 53 hosting for an attached zone (with ALIAS queries to CloudFront free) and CloudFront Functions. Pro adds access logs with CloudWatch Logs ingestion included and the edge KeyValueStore. Business adds VPC origins and origin mutual TLS. Premium adds Origin Shield and viewer mTLS. A distribution on a plan must have a WAF web ACL attached, and some features are not supported: real-time logs, continuous deployment (staging distributions), multi-tenant distributions, WAF rule groups, partner managed rules, Targeted Bots, and account takeover and account creation fraud prevention. Lambda@Edge works on every tier but is billed pay-as-you-go. Legacy configuration (origin access identity, ForwardedValues, legacy cache settings) has to be migrated first. If you depend on one of those, stay on pay-as-you-go for that distribution.

The egress line most comparisons skip

Data transfer from S3, ALB or API Gateway to CloudFront is free. Data transfer from AWS to Cloudflare is ordinary internet egress, $0.09/GB for the first 10 TB a month in US East after the account-wide 100 GB free allowance. AWS is not in Cloudflare's Bandwidth Alliance. So the cost of Cloudflare in front of AWS depends on cache hit ratio. A static site at 98% hits pays almost nothing. An API or personalized pages that miss the cache pay AWS egress on every response, which can cost more than the CloudFront plan you were avoiding.

Capabilities

CloudFront

Cloudflare

Edge compute

CloudFront Functions (lightweight JS on every request) and Lambda@Edge (Node.js, Python at regional edge caches)

Workers: full JS/TS/Wasm runtime with KV, D1, R2, Durable Objects and Queues

WAF

AWS WAF: managed rules, rate limits, bot control; same rules work on ALB and API Gateway

Cloudflare WAF: managed rules from Pro, more rules and features by tier

Private origins

VPC origins (Business and up): app in private subnets, reachable only through CloudFront

Cloudflare Tunnel: outbound-only connector from your network

DNS

Route 53, included for one attached zone per plan

Cloudflare DNS, required for full proxy setup on most plans

Zero Trust and access

Not part of CloudFront; use Verified Access or an identity proxy

Cloudflare One (Access, Gateway) on the same network

Infrastructure as code

CloudFormation, CDK, Terraform alongside the rest of your AWS stack

Terraform provider, Wrangler; a separate account and permission model

Bills and access

On the AWS bill, under the same IAM and Organizations controls

A second vendor, a second identity system, a second invoice

Which one

Question 1 of 3

Where does the origin run?

Our verdict

**Your origin is on AWS:** CloudFront is the default. Origin fetches from S3, ALB and API Gateway are free, VPC origins keep the app off the internet, and the flat-rate plans now make the bill predictable. **You want one edge in front of many clouds or hosts, or Zero Trust and a full edge platform in one place:** Cloudflare. Budget for AWS data transfer out, because Cloudflare in front of an AWS origin pays AWS egress on every cache miss. **Neither wins on its own.** Plenty of teams run Cloudflare for DNS and Zero Trust and CloudFront for delivery.

Related solutions

AWS Architecture Review

A focused, senior-level review of your current AWS architecture, with a prioritized list of what to fix and why.

1 week
$4k–$8k
View

AWS Cost Optimization & FinOps Sprint

Reduce your AWS bill by 20–60% while improving performance and reliability.

1–3 weeks
$6k–$18k
View

Serverless Migration

Move from expensive always-on compute to serverless architecture: reduce costs, eliminate patching, and scale automatically.

3–8 weeks
$12k–$30k
View

Get your edge, WAF and DNS set up and priced

We work with startups and growing companies on AWS architecture decisions. Tell us about your situation and we will recommend the right approach.

As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.