# AWS Amplify vs Netlify

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

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

## At a glance

| Criterion | AWS Amplify | Netlify |
| --- | --- | --- |
| Free tier | Yes | Yes |
| Pricing model | Usage-based; pay for what you use, with no monthly minimum | Monthly plan credits are included with your plan each billing cycle and reset at the start of each cycle. |
| Egress over allowance | $0.15 per GB served | 20 credits per GB ($0.13 per GB) |
| When you exceed a cap | Billed automatically: pay-as-you-go with no monthly minimums; storage charges keep recurring until the app is deleted | Suspended: when credits run out every project is paused and visitors see a Site not available page, unless auto recharge is enabled to buy more credits automatically |
| Sites or apps included | 25 apps per Region by default (adjustable via a quota increase request); 50 branches per app | 500 projects on the Personal plan (same limit on Free and Pro) |
| 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 fixed visit cap; traffic is metered against the Personal plan's 1,000 credits/month at 2 credits per 10,000 web requests and 20 credits per GB of bandwidth |
| Concurrent builds | 5 concurrent jobs per Region by default, adjustable via a quota increase request | Personal: 1 concurrent build included, purchasable up to a maximum of 3, at $40/month per additional build |
| Max request duration | 15 minutes (maximum execution time of an SSR compute execution instance) | 60 seconds (synchronous); 30 seconds (scheduled); 15 minutes (background) |
| Streaming response limit | 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). | Streaming (non-edge) Functions: 60-second execution limit and 20 MB response size limit. Stated without plan differentiation (applies on the cheapest paid plan). |
| Git deployment | Supported | Supported |
| Persistent processes | Not supported | Not 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/))
- Netlify: Monthly plan credits are included with your plan each billing cycle and reset at the start of each cycle. ([source](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/))

### Egress over allowance

- AWS Amplify: $0.15 per GB served ([source](https://aws.amazon.com/amplify/pricing/))
- Netlify: 20 credits per GB ($0.13 per GB) ([source](https://www.netlify.com/pricing/))

### 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 ([source](https://aws.amazon.com/amplify/pricing/))
- Netlify: Suspended: when credits run out every project is paused and visitors see a Site not available page, unless auto recharge is enabled to buy more credits automatically ([source](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/how-credits-work/))

### 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))
- Netlify: 500 projects on the Personal plan (same limit on Free and Pro) ([source](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/))

### 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))
- Netlify: No fixed visit cap; traffic is metered against the Personal plan's 1,000 credits/month at 2 credits per 10,000 web requests and 20 credits per GB of bandwidth ([source](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/how-credits-work/))

### 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))
- Netlify: Personal: 1 concurrent build included, purchasable up to a maximum of 3, at $40/month per additional build ([source](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/))

### Max request duration

- AWS Amplify: 15 minutes (maximum execution time of an SSR compute execution instance) ([source](https://docs.aws.amazon.com/amplify/latest/userguide/ssr-deployment-specification.html))
- Netlify: 60 seconds (synchronous); 30 seconds (scheduled); 15 minutes (background) ([source](https://docs.netlify.com/build/functions/configuration/))

### 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). ([source](https://docs.aws.amazon.com/amplify/latest/userguide/ssr-amplify-support.html))
- Netlify: Streaming (non-edge) Functions: 60-second execution limit and 20 MB response size limit. Stated without plan differentiation (applies on the cheapest paid plan). ([source](https://docs.netlify.com/build/functions/api/))

## 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 Netlify if Teams that want Git-driven deploys onto a global CDN with a managed Postgres database built into the same platform. The free tier is 300 credits a month with a hard limit, so spend cannot surprise you.

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: Netlify — You need to run containers or long-lived processes — Netlify does not document either.

## Documented by only one

- Entry paid plan: Netlify: $9/month for 1,000 credits/month
- 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.
- Memory (entry plan): Netlify: 1024 MB (1 GB) default memory per function; raising it to 4096 MB (4 GB) requires a Credit-based Pro or Enterprise plan, so Personal is capped at the 1024 MB default
- Included bandwidth: AWS Amplify: 15 GB of data transfer out per month at no cost (with AWS Free Tier)
- File or inode limit: Netlify: No limit on files per deploy, but a hard limit of 54,000 files per directory (platform-wide)
- 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
- CPU time limit: Netlify: 50 ms of CPU execution time per request for Edge Functions, explicitly excluding time spent waiting on resources or responses. Listed under operation limits with no plan differentiation (applies on the cheapest paid plan).
- Edge function timeout: Netlify: Response header timeout of 40 s for Edge Functions (the documented time limit on the edge runtime, alongside the separate 50 ms CPU cap). Listed under operation limits with no plan differentiation.
- Scheduled jobs: Netlify: Supported
- Persistent storage: AWS Amplify: Not supported
- Managed databases: Netlify: Supported

## Questions this comparison answers

**Egress over allowance: AWS Amplify or Netlify?**

AWS Amplify: $0.15 per GB served
Netlify: 20 credits per GB ($0.13 per GB)

**When you exceed a cap: AWS Amplify or Netlify?**

AWS Amplify: Billed automatically: pay-as-you-go with no monthly minimums; storage charges keep recurring until the app is deleted
Netlify: Suspended: when credits run out every project is paused and visitors see a Site not available page, unless auto recharge is enabled to buy more credits automatically

**Should I choose AWS Amplify or Netlify?**

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 Netlify if Teams that want Git-driven deploys onto a global CDN with a managed Postgres database built into the same platform. The free tier is 300 credits a month with a hard limit, so spend cannot surprise you.