Updated

Amazon Web Services vs Cloudflare

Of the 3,549 makers' products we know the hosting of, 460 chose Amazon Web Services (13%) and 385 Cloudflare (11%); 68 use both. Among the 860 launched in 2026, Amazon Web Services is in 9% and Cloudflare in 20%, against 12% and 8% of those launched in 2024 or earlier. They're different kinds of tool, hyperscaler cloud and edge platform, so the counts don't measure the same choice. Cloudflare is the more common pick among Astro products (21 vs 10). At our calculator's default usage, Amazon Web Services comes to $17 a month and Cloudflare $12, at list prices. On GitHub, 39 public pull requests moved projects from Amazon Web Services to Cloudflare, and 10 the other way: more move to Cloudflare, though fewer products use it in total.

Two sides of the hosting decision: hyperscaler cloud and edge platform. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.

Ask your AI about this, with this page as the source:ChatGPT ↗Claude ↗Perplexity ↗

Which fits you

Choose Amazon Web Services if
  • The widest catalog of building blocks — Lambda, containers, managed databases, queues — to assemble your own infrastructure.

Use it whenYou need a specific AWS service, enterprise customers ask for it, or you have credits to spend.

Trade-offYou wire up networking, permissions and deploys yourself; billing is per service and hard to predict.

Choose Cloudflare if
  • Your app is a static site or docs and should cost nothing to host

Use it whenYou want the cheapest global hosting and can live with the Workers runtime.

Trade-offThe Workers runtime isn't full Node.js; some libraries need adapting.

At a glance

Amazon Web ServicesCloudflare
Used by460 makers' products · 18 open-source projects385 makers' products · 232 open-source projects
Cost at default usagerequests 5 million requests, data transfer out 100 GB, serverless function compute 100 GB-hours$17/mo Pay as you go (Lambda + EC2 t4g.small)$12/mo Workers Paid
Moved to it on GitHubpull requests since Oct 202410+ from Cloudflare39+ from Amazon Web Services
Downloads4.2M/wk−40% vs npm21.3M/wk3.1× vs npm
PricingPay-as-you-go per service; new accounts get up to $200 in Free Tier credits over 6 months. · paid from Pay as you goGenerous free tier; usage-based paid plans. · paid from $5/mo (Workers Paid)
Free tierYesYes
Open sourceNoNo
Incidents, 90 daysfrom its status pageno public status feed48+ (5 major)

Which makers on your framework pick

Makers' products built with each framework that chose either one, for hosting.

New launches vs older products

A tool that came first has products from every year since, so its total runs ahead. Here is what products launched each year chose, as a share of those that made the hosting decision (by the year they launched on Product Hunt).

LaunchedAmazon Web ServicesCloudflareProducts
2022 or earlier19% 228% 10118
202316% 1413% 1289
202410% 597% 41582
202514% 8910% 65629
20269% 8020% 176860

Cost as you grow

At 100k requests Cloudflare costs less ($0 vs $16); and still does at 500M requests ($871 vs $1,600). They're different kinds of tool — hyperscaler cloud and edge platform — so the prices don't buy the same thing.

$0$50$200$500$1,0000.10.5151050100500
CloudflareAmazon Web Servicesx: requests per month (million requests), other usage scaled with it; held at 1 server (always-on app servers) · cheapest usable plan at each point, list prices · try your own numbers
The numbers, plan by plan
Requests per monthAmazon Web ServicesCloudflare
0.1$16 Pay as you go (Lambda + EC2 t4g.small)$0 Workers Free
0.5$16 Pay as you go (Lambda + EC2 t4g.small)$5.12 Workers Paid
1$16 Pay as you go (Lambda + EC2 t4g.small)$5.84 Workers Paid
5$17 Pay as you go (Lambda + EC2 t4g.small)$12 Workers Paid
10$32 Pay as you go (Lambda + EC2 t4g.small)$19 Workers Paid
50$160 Pay as you go (Lambda + EC2 t4g.small)$88 Workers Paid
100$320 Pay as you go (Lambda + EC2 t4g.small)$175 Workers Paid
500$1,600 Pay as you go (Lambda + EC2 t4g.small)$871 Workers Paid

From each vendor's pricing page: Amazon Web Services, Cloudflare.

Who moves from one to the other

Public pull requests on GitHub since Oct 2024 whose title says "Amazon Web Services to Cloudflare" or the reverse — real code changes, by developers in general rather than makers only.

Amazon Web Services → Cloudflare39+ PRs
When and what they move →

What makers say

Makers on using it for hosting, from Product Hunt and Starter Story interviews, each linked to the source. Products with a page of their own and fuller notes first.

On Amazon Web Services
We are so excited to integrate with AWS Lambda. Look for our upcoming co-authored blog about how Fleak and AWS Lambda bring goodness to data teams and help them win their time back!
Fleak, the makerSep 2026 ↗
AWS provides the global infrastructure we need to deliver low-latency voice translation to users worldwide. Their reliable services ensure our calls connect seamlessly across regions.
The Banana App, the makerSep 2026 ↗
…m - for customer support, knowledge base, and live chat support Webflow - for our website AWS - for our cloud hosting needs Figma - for all our design collaboration Microsoft Clarity…
SmartCue, the makerJan 2023 ↗
169 more on the Amazon Web Services page →
On Cloudflare
Cloudflare handles everything for iVox — DNS, website hosting on Pages, R2 file storage for downloads, and Workers for the license backend. All of it, basically free at indie scale.
iVox, the makerJun 2026 ↗
Cloudflare Workers and Pages let us deploy instantly at the network edge, delivering lightning-fast performance and reliability without the usual complexities of traditional hosting.
Comigo, the makerSep 2026 ↗
Everything runs on Workers, D1 and R2. The big one for me is that R2 doesn't charge for egress. This app serves a lot of audio files and I would not survive normal bandwidth pricing.
WaseiGo, the makerSep 2026 ↗
235 more on the Cloudflare page →

Loved and watch-outs

Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.

Amazon Web Services
Most loved
  • It offers a huge catalog of services in one place, from databases to queues to AI. PHPH 2PH 3PH 4
  • It scales up and down with bursty traffic without re-architecting. PHPH 2PH 3
  • Its reliability record is something teams are willing to bet a product on. PHPH 2PH 3PH 4
Watch-outs
  • Major outages, from long us-east incidents to struck data centers, have taken customer services down. HNHN 2HN 3HN 4
  • Its services can be tricky to configure. PH
On Product Hunt: 5.0★, 294 reviews · mentioned most: reliable cloud services, scalable infrastructure, extensive service offerings
Cloudflare
Most loved
  • Workers, D1, R2, Durable Objects and more combine as bindings on one platform instead of separate vendors. PHPH 2PH 3PH 4
  • The free tier bundles DNS, CDN, TLS and abuse protection in one dashboard. PHPH 2
  • Wrangler deploys to the global edge in seconds, with preview links per pull request. PHPH 2PH 3
Watch-outs
  • Bot checks and default AI-crawler blocking get in the way of legitimate users and automation. HNHN 2HN 3HN 4
  • The dashboard is slow and buggy, with login and passkey problems. HNHN 2
  • It has cut off customers abruptly, and billing support was slow and unhelpful when production went down. HNHN 2HN 3
On Product Hunt: 5.0★, 267 reviews · mentioned most: fast performance, reliable security, global CDN

Who uses each

Used by both — often one replacing the other, or each for a different part of the product

What makers pair each with

With Amazon Web Services
With Cloudflare
VercelFrontend cloudNext.js apps — zero-config deploys and preview URLs.vs Amazon Web Services →vs Cloudflare →
NetlifyFrontend cloudStatic sites and JAMstack apps on any framework.vs Cloudflare →
RailwayPaaSServers, workers and databases deployed together, with almost no configuration.vs Amazon Web Services →vs Cloudflare →
RenderPaaSA Heroku-style platform for web services, cron jobs and Postgres.vs Amazon Web Services →
Fly.ioContainer platformDocker apps that should run close to users in many regions.vs Amazon Web Services →
Hetzner CloudYour own serverA lot of CPU and RAM per euro, in European, US and Singapore regions.vs Amazon Web Services →
CoolifyYour own serverA Heroku- or Vercel-style dashboard on your own server, with many one-click services.

Questions

Amazon Web Services or Cloudflare: which do makers choose?

Of the 3,549 makers' products we know the hosting of, 460 chose Amazon Web Services (13%) and 385 Cloudflare (11%); 68 use both. Among the 860 launched in 2026, Amazon Web Services is in 9% and Cloudflare in 20%, against 12% and 8% of those launched in 2024 or earlier. They're different kinds of tool, hyperscaler cloud and edge platform, so the counts don't measure the same choice. Cloudflare is the more common pick among Astro products (21 vs 10). At our calculator's default usage, Amazon Web Services comes to $17 a month and Cloudflare $12, at list prices. On GitHub, 39 public pull requests moved projects from Amazon Web Services to Cloudflare, and 10 the other way: more move to Cloudflare, though fewer products use it in total. Choose Amazon Web Services if the widest catalog of building blocks — Lambda, containers, managed databases, queues — to assemble your own infrastructure; choose Cloudflare if your app is a static site or docs and should cost nothing to host.

Can you use Amazon Web Services and Cloudflare together?

68 makers' products we track use both, often one replacing the other or each for a different part of the product: Datazip, FetchSandbox, Gro, Hello Inbox, Modelence App Builder and others.

When should I pick Cloudflare over Amazon Web Services?

Pick Cloudflare if: Your app is a static site or docs and should cost nothing to host.

Which is cheaper, Amazon Web Services or Cloudflare?

At requests 5 million requests, data transfer out 100 GB, serverless function compute 100 GB-hours: Amazon Web Services $17/mo (Pay as you go (Lambda + EC2 t4g.small)), Cloudflare $12/mo (Workers Paid), at list prices.

How do Amazon Web Services and Cloudflare compare in cost as you grow?

At 100k requests Cloudflare costs less ($0 vs $16); and still does at 500M requests ($871 vs $1,600). Cheapest usable plan at each scale, at list prices.

Are people switching from Amazon Web Services to Cloudflare?

Public GitHub pull requests since 2024-10-02: 39+ from Amazon Web Services to Cloudflare, 10+ from Cloudflare to Amazon Web Services.