# AWS Amplify vs Cloudflare Pages

Canonical: https://inetgeek.com/compare/aws-amplify-vs-cloudflare-pages/

Every value below is read from AWS Amplify's and Cloudflare Pages's own documentation. See https://inetgeek.com/methodology/ for how.

## At a glance

| Criterion | AWS Amplify | Cloudflare Pages |
| --- | --- | --- |
| Free tier | Yes | Yes |
| Pricing model | Usage-based; pay for what you use, with no monthly minimum | Metered usage with a $5 monthly account minimum |
| Sites or apps included | 25 apps per Region by default (adjustable via a quota increase request); 50 branches per app | 100 projects per account (platform-wide, all plans) |
| Monthly visits cap | No monthly visit cap, but a per-app rate quota of 20,000 request tokens per second (adjustable). SSR requests are free up to 500,000 per month, then $0.30 per 1 million requests. | No cap on static asset requests on any plan; requests to Pages Functions count against the Workers Paid plan quota |
| Build minutes | 1,000 build minutes per month at no cost with AWS Free Tier; $0.01 per minute for a Standard Instance thereafter | 500 builds per month on the Free plan |
| Concurrent builds | 5 concurrent jobs per Region by default, adjustable via a quota increase request | 5 concurrent builds on Pro (1 on Free, 20 on Business), with 5,000 builds per month on Pro |
| Git deployment | Supported | Supported |
| Edge network | Supported | Supported |

## Where they differ

### Pricing model

- AWS Amplify: Usage-based; pay for what you use, with no monthly minimum ([source](https://aws.amazon.com/amplify/pricing/))
- Cloudflare Pages: Metered usage with a $5 monthly account minimum ([source](https://developers.cloudflare.com/workers/platform/pricing/))

### Sites or apps included

- AWS Amplify: 25 apps per Region by default (adjustable via a quota increase request); 50 branches per app ([source](https://docs.aws.amazon.com/amplify/latest/userguide/quotas-chapter.html))
- Cloudflare Pages: 100 projects per account (platform-wide, all plans) ([source](https://developers.cloudflare.com/pages/platform/limits/))

### Monthly visits cap

- AWS Amplify: No monthly visit cap, but a per-app rate quota of 20,000 request tokens per second (adjustable). SSR requests are free up to 500,000 per month, then $0.30 per 1 million requests. ([source](https://docs.aws.amazon.com/amplify/latest/userguide/quotas-chapter.html))
- Cloudflare Pages: No cap on static asset requests on any plan; requests to Pages Functions count against the Workers Paid plan quota ([source](https://developers.cloudflare.com/pages/functions/pricing/))

### Build minutes

- AWS Amplify: 1,000 build minutes per month at no cost with AWS Free Tier; $0.01 per minute for a Standard Instance thereafter ([source](https://aws.amazon.com/amplify/pricing/))
- Cloudflare Pages: 500 builds per month on the Free plan ([source](https://developers.cloudflare.com/pages/platform/limits/))

### Concurrent builds

- AWS Amplify: 5 concurrent jobs per Region by default, adjustable via a quota increase request ([source](https://docs.aws.amazon.com/amplify/latest/userguide/quotas-chapter.html))
- Cloudflare Pages: 5 concurrent builds on Pro (1 on Free, 20 on Business), with 5,000 builds per month on Pro ([source](https://developers.cloudflare.com/pages/platform/limits/))

## Which should you choose?

Pick AWS Amplify if Front-end apps deployed from Git onto AWS with usage-based pricing and no monthly minimum, including 1,000 build minutes and 15 GB of transfer under the free tier.

Pick Cloudflare Pages if Projects where the entire fixed cost should be a $5 monthly account minimum rather than a per-seat fee, and teams already running on the wider Workers platform. Billing is metered, so cost tracks traffic rather than headcount.

Consider something else: AWS Amplify — Egress beyond the free allowance is $0.15 per GB, which is the highest of the platforms compared here, and SSR compute is capped at 15 minutes.

Consider something else: Cloudflare Pages — Your repository is hosted somewhere other than GitHub or GitLab, or the free plan's 500 builds a month is not enough headroom.

## Documented by only one

- Entry paid plan: Cloudflare Pages: $5 / month account minimum
- Egress over allowance: AWS Amplify: $0.15 per GB served
- When you exceed a cap: AWS Amplify: Billed automatically: pay-as-you-go with no monthly minimums; storage charges keep recurring until the app is deleted
- Storage (entry plan): AWS Amplify: Pay-as-you-go: no cost up to 5 GB stored on CDN per month, then $0.023 per GB per month. Separately, build artifact size is capped at 5 GB per app.
- Included bandwidth: AWS Amplify: 15 GB of data transfer out per month at no cost (with AWS Free Tier)
- File or inode limit: Cloudflare Pages: 100,000 files per site on paid plans (20,000 on Free); maximum single asset size 25 MiB
- Max request duration: AWS Amplify: 15 minutes (maximum execution time of an SSR compute execution instance)
- CPU time limit: Cloudflare Pages: Up to 30 seconds of CPU time under the Standard usage model, which the Pages docs state Pages supports. CPU time is tracked separately from duration in the Pages Functions metrics dashboard; the same page notes that network-bound work inflates duration but not CPU time. Not plan-differentiated on the page.
- Streaming response limit: AWS Amplify: Next.js streaming is listed as an unsupported feature of the Amplify Hosting compute SSR provider — i.e. streamed responses are not available at all, rather than bounded by a duration or size. Platform-wide (Amplify Hosting has no plan tiers).
- Managed connection pooling: Cloudflare Pages: Supported
- Scheduled jobs: Cloudflare Pages: Not supported
- Persistent processes: AWS Amplify: Not supported
- Persistent storage: AWS Amplify: Not supported
- Regions: Cloudflare Pages: 348 cities across 100+ countries

## Questions this comparison answers

**Should I choose AWS Amplify or Cloudflare Pages?**

Pick AWS Amplify if Front-end apps deployed from Git onto AWS with usage-based pricing and no monthly minimum, including 1,000 build minutes and 15 GB of transfer under the free tier.
Pick Cloudflare Pages if Projects where the entire fixed cost should be a $5 monthly account minimum rather than a per-seat fee, and teams already running on the wider Workers platform. Billing is metered, so cost tracks traffic rather than headcount.