An AWS Amplify Alternative For A Static React App

Looking for an AWS Amplify alternative for a React or Vite front end? The free plan now ends after 6 months. Six hosts compared on price and catch, Nov 2026.
The OxyPages Team · · 9 min read
You connected a GitHub repo to AWS Amplify, picked a branch, let it detect Vite, and a few minutes later your React app had a URL. Then you went back into the AWS console to change one redirect and found yourself three menus deep in a service list with hundreds of entries.
That console is the price of a platform built for far more than your app needs. Amplify can run server-rendered Next.js, wire up auth and data through Amplify Gen 2, and sit behind a firewall. A folder from npm run build uses none of it.
The other reason people go looking for an AWS Amplify alternative is the free plan. For accounts created since 15 July 2025, it's credits that run out, and an account that closes on a timer.
This post covers what changed, what a month on Amplify really costs for a small React app, who should stay, and six other places the front end can live. Prices are monthly unless marked, from each vendor's own pages, as of November 2026. For the wider field, every static host compared side by side has the full table.
TL;DR: New AWS accounts since 15 July 2025 get up to $200 in credits on a Free plan, and AWS says "the account closes on its own 6 months after you open it or when your credits run out, whichever comes first." After that, Amplify is metered: $0.01 per build minute, $0.023 per GB stored each month, and $0.15 per GB served. A small React app costs a few dollars a month, with no ceiling in a bad month. Stay on Amplify for server-rendered Next.js, Amplify Gen 2 auth and data, or AWS compliance needs.
Why People Look For An AWS Amplify Alternative
Most people look for an AWS Amplify alternative because the free plan changed and the bill became something to watch. This is from AWS's own pages, November 2026.
The free plan is now a countdown. For accounts opened from 15 July 2025, new customers get up to $200 in Free Tier credits. AWS says the free plan "will be available for 6 months after account creation", and the AWS Free Tier page adds that the account "closes on its own" at six months or when credits run out. You can upgrade to a paid plan, and leftover credits then apply to your bills, but they must be used within 12 months.
The old "free for 12 months" allowances still quoted online only apply to older accounts.
Every unit is metered. Builds cost $0.01 a minute on the standard machine, storage costs $0.023 per GB a month "recurring until the app is deleted", and data served costs $0.15 per GB. There's no flat plan and no monthly cap.
Build images move under you. Amplify ended Node.js 14, 16 and 18 build support on 15 September 2025, which AWS's own troubleshooting docs connect to broken builds on older apps.
What A Month On Amplify Really Costs

A small React app on Amplify costs a few dollars a month once the credits are gone. Here's the maths on a realistic month.
Say you push 30 times and each build takes 3 minutes. That's 90 build minutes at $0.01, so $0.90. Your stored app is 1 GB, so $0.023. Then 30,000 visits each pulling 1.5 MB of JavaScript, CSS and images is 45 GB served, at $0.15 a GB, which is $6.75.
That's about $7.67 for the month, which is fair.
The catch is the shape, not the size. If a link goes viral or a bot hammers the site and pulls 2 TB, the same rate says $300 for transfer alone. If you add the web application firewall, that's another $15 a month per app plus AWS WAF charges. A flat-priced host trades that open end for a quota.
Who Should Stay On AWS Amplify?
Stay on Amplify if your app uses the parts that make it a platform rather than a file server.
- You run server-rendered Next.js. Amplify's compute handles SSR for Next.js 12 to 15. A static host can't render pages on the server at any price.
- You use Amplify Gen 2 for auth and data. The backend is defined in TypeScript next to the front end, and one pipeline deploys both.
- You need AWS-native security or compliance. WAF integration, IAM, and an existing AWS bill your company already approves are real reasons.
- Your team works in branches. Feature-branch environments, pull request previews and password-protected branches come built in.
- You'd rather drag a zip than learn Git. Amplify's manual deploy takes a zip up to 5 GB, an S3 bucket or a public URL, with no repo needed. It's not for SSR apps, but it works for a static build.
Leaving AWS entirely with a server to run? A static host isn't the answer; look at an app platform such as Render or Railway.
Six Places To Host The Front End Instead
The right pick depends on whether you need server rendering and how much you care about a fixed bill. All prices are monthly and as of November 2026.
| Host | Free tier | Paid from (monthly) | Runs SSR or server code | The catch |
|---|---|---|---|---|
| AWS Amplify | Up to $200 credits, 6 months (new accounts) | Metered: $0.01 per build minute, $0.15 per GB served | Yes, Next.js 12-15 | No ceiling on usage billing |
| OxyPages | 1 site, 25 MB, 5,000 page views, personal use, no custom domain | Lite $5 ($48 a year): 2 sites, 20,000 views, custom domains | No, static only | No functions, backends or databases |
| Cloudflare Pages / Workers | Unlimited static requests, 500 builds | Workers Paid $5 minimum per account | Yes, through Workers | Two overlapping products; 10 ms CPU cap on Free |
| Netlify | 300 credits, hard limit, commercial use allowed | Personal $9 (1,000 credits) | Yes, Next.js with zero config | Deploys and bandwidth both burn credits |
| Vercel | Hobby: 100 GB transfer, non-commercial | Pro $20 per deploying seat | Yes, Next.js native | Per-seat billing plus usage |
| Firebase Hosting | 10 GB storage, 360 MB transfer a day | Blaze: $0 minimum, then $0.15 per GB | SSR via App Hosting on Blaze | Spark sites disabled past the quota |
| Azure Static Web Apps | 100 GB bandwidth per subscription, hobby use | Standard $9 per app | Managed Functions APIs; Next.js hybrid in preview | Card needed for an Azure account |
OxyPages: The Static Front End Only
I run this one, so here's the plain version. OxyPages replaces the static front end of an Amplify app and nothing else. It hosts built React, Vue, Svelte, Vite and Astro output, has a single-page app mode, reads _redirects and _headers, and builds from GitHub on every plan, with 100 build minutes a month on Free.
It doesn't run server code, functions or databases. If your Amplify app renders on the server or depends on Gen 2 for its backend, keep that on AWS. The free plan is personal use only with no custom domain, so a commercial site starts on the $5 Lite plan, a flat price with page-view quotas rather than a per-GB bill.
Cloudflare Pages Or Workers
Cloudflare suits sites that might get sudden traffic, because static asset requests are free and unlimited. Server code runs on Workers, with 100,000 requests a day free and a 10 ms CPU limit per request. Workers Paid starts at $5 a month per account.
The catch is the Pages-or-Workers choice; Cloudflare now points new projects to Workers.
Netlify
Netlify suits Amplify users who want SSR without AWS. It runs Next.js "with zero configuration", including SSR, ISR and middleware, and its free plan allows commercial projects. You get 300 credits a month as a hard limit; Personal is $9 a month, Pro $20 a month with unlimited members.
A production deploy costs 15 credits and bandwidth 20 credits per GB, and when credits run out, every project on the team pauses.
Vercel
Vercel suits teams heading deeper into Next.js, since Vercel makes it. The free Hobby plan includes 100 GB of fast data transfer a month but is limited to personal or non-commercial use. Pro is $20 a month with one deploying seat and $20 of usage credit, then $20 for each extra deploying seat.
Firebase Hosting: The Google Cloud Option
Firebase Hosting is the closest match if you're moving to Google Cloud. The free Spark plan gives 10 GB of storage and 360 MB of transfer a day with custom domains, and no card. Past that, Spark sites are disabled until the next month, and the Blaze plan bills $0.15 per GB with no hard cap. Server-rendered apps go to Firebase App Hosting, which needs Blaze.
Azure Static Web Apps: The Microsoft Option
Azure Static Web Apps is the closest match if your company runs on Microsoft. The free plan includes 100 GB of bandwidth a month per subscription and two custom domains per app, but Microsoft says it's "intended for hobby/personal usage". Standard is $9 per app per month in most US and EU regions, and an Azure account needs a credit or debit card.
Moving The Front End Without Touching The Backend

Moving a static React front end off Amplify takes about 30 minutes, and your AWS backend can stay where it is. Here's the order I'd follow.
- Build locally. Run
npm run buildand open thedistfolder (orbuild, for Create React App) with a local preview. If it works there, it works on any static host. - Check where the backend config lives. An Amplify Gen 2 front end reads its backend addresses from
amplify_outputs.json, which gets bundled into the build. The browser keeps calling the same AWS endpoints wherever the files are served from. - Copy your rewrite rules. Amplify's single-page app rule lives under Rewrites and redirects in the console and sends unknown paths to
/index.htmlwith a 200. On hosts that read a_redirectsfile it's one line:/* /index.html 200. Skip it and refreshing any inner page returns a 404. Why a refresh returns a 404 on a React app explains the cause. MDN's explanation of a single-page app covers why the server has to do this. - Update sign-in redirect URLs. If your app uses a hosted sign-in page or a social login, add the new domain to the allowed callback and sign-out URLs before you switch. This is the step people forget.
- Test, then move the domain. Deploy, click every route, refresh each one, and sign in. Then point your domain at the new host. pointing a domain you already own at a new host covers the DNS records.
- Delete the Amplify app last. Storage is billed "recurring until the app is deleted", so remove the app once traffic has moved, not before.
What To Do Next
Open your Amplify app and look at what it actually does. If there's no server rendering and no Gen 2 backend, you're paying a metered bill to serve a folder, and any host in the table can serve it.
If the app renders on the server or owns your backend, stay, or compare Netlify and Vercel for SSR.
If it's static and you'd rather pay a flat price than read a usage bill, run the six steps above. When you're ready to move a commercial front end with a custom domain, compare the OxyPages plans and test your build on a free account first.
FAQ
Is AWS Amplify Still Free?
Only for a limited time on new accounts. Since 15 July 2025, new AWS customers get up to $200 in credits on a Free plan, and AWS says the account closes six months after opening or when the credits run out, whichever comes first. Older accounts keep the previous 12-month allowances.
How Much Does AWS Amplify Hosting Cost?
Amplify is pay-as-you-go with no monthly minimum, as of November 2026. Builds are $0.01 a minute, storage $0.023 per GB a month, data served $0.15 per GB, and server-side rendering $0.30 per million requests plus $0.20 per GB-hour. A small React app with 45 GB of traffic a month comes to under $10.
What Is The AWS Amplify Alternative On Google Cloud Or Azure?
On Google Cloud it's Firebase Hosting for static sites and Firebase App Hosting for server-rendered apps. On Azure it's Azure Static Web Apps, which pairs static hosting with managed Azure Functions. Both have free tiers, and both bill by usage or per app once you outgrow them.
Can I Keep My Amplify Backend And Host The Front End Elsewhere?
Often, yes, because the front end calls AWS by URL. Add the new domain to your sign-in callback URLs first. If your backend deploys through the same Amplify pipeline as your front end, keep that pipeline for the backend, and treat any AWS Amplify alternative as a home for the static files only.