A Simpler Alternative To Azure Static Web Apps

Need an alternative to Azure Static Web Apps for a React or Vite build? Free is hobby-only and Standard is $9 per app a month. Six hosts compared, Nov 2026.
The OxyPages Team · · 8 min read
You created a Static Web App in the Azure portal, signed in to GitHub, picked React as the preset and dist as the output folder. Azure dropped a workflow file called something like azure-static-web-apps-purple-pond.yml into your repo, GitHub Actions ran it, and your Vite app was live a few minutes later.
Then the questions started. What's a resource group? Why does the account need a card? And the one that matters most: the site is about to start earning money, and the free plan's label says personal.
That's the usual moment people go looking for an alternative to Azure Static Web Apps. The service works well. The friction is the portal around it, a free plan Microsoft marks for hobby use, and a paid plan billed per app, so every extra site adds to the bill.
This post covers what the free plan really allows, what Standard costs once you have a few sites, who should stay, and six hosts that can serve the same build. Every vendor figure was checked on the vendor's own pages in November 2026, and prices are monthly unless marked. For the whole field, every static host compared side by side has the bigger table.
TL;DR: The Azure Static Web Apps free plan is large: 100 GB of bandwidth a month per subscription, up to 10 apps, 2 custom domains per app and 250 MB per app. Microsoft says it "is intended for hobby/personal usage and does not come with SLA", and a free site stops serving if it goes over quota. Standard is $9 per app per month in most US and EU regions ($10.80 in Malaysia, Indonesia and Southeast Asia 3), so five production sites cost $45 a month. Stay if you use its managed Functions APIs, built-in sign-in and roles, linked backends or Microsoft's SLA. For a plain React or Vite build, Cloudflare, Netlify, GitHub Pages, Vercel, DigitalOcean and flat-priced static hosts all fit.
Why People Move Off Static Web Apps
People move off Static Web Apps for three reasons: the free plan's hobby label, per-app pricing, and the Azure account around it. All of this is from Microsoft's own pages as of November 2026.
Free is for personal projects. The plans page labels Free "For personal projects", and the pricing page says Free "is intended for hobby/personal usage and does not come with SLA". Standard is described as "For general purpose production app". If your site sells something, that wording points you to Standard.
Free sites stop when the quota runs out. The 100 GB of monthly bandwidth is shared across the whole subscription, not counted per app. Overage is "Unavailable" on Free, and Microsoft says the site stops serving if quotas are exceeded. Ten small sites on one subscription share that one pool.
Standard is billed per app. At $9 per app per month, each new site is another $9. Bandwidth past the 100 GB included per subscription costs $0.20 per GB.
The account needs a card and a phone number. An Azure account requires "a credit card or a debit card (non-prepaid)", even if you only ever use Free.
Smaller things add up. The Dedicated plan was retired on 31 October 2025, so anyone on it had to redeploy. Build artifacts sit in GitHub Actions storage and count against your GitHub quotas. And server-rendered Next.js is still in preview, with a 250 MB limit.
What Five Sites Cost On Standard
Say you run five client sites, all built React or Vite apps, each with a custom domain, all commercial. On Standard in a US region that's 5 × $9, or $45 a month and $540 a year. In Malaysia or Indonesia it's 5 × $10.80, so $54 a month.
That's before bandwidth, and five modest sites rarely pass 100 GB combined. The bill is predictable, which is a real point in its favour. It just grows by one app fee for every site you add, and per-site pricing is exactly what the hosts below avoid.
Who Should Stay On Static Web Apps?
Stay on Static Web Apps if your site uses the parts that aren't static. Here's when moving would cost you features you can't easily replace.
- Your app calls a managed Functions API at
/api. Static Web Apps proxies those calls with no CORS setup. A static host has no server code to call. - You use the built-in sign-in. Microsoft Entra ID and GitHub logins, plus custom roles, come configured. Replacing them means adding an auth service.
- You link a backend on Standard. A Functions app, App Service, Container App or API Management can sit behind the same domain.
- You need private endpoints or an SLA. Standard has both, and compliance teams ask for them.
- Your site is personal and fits Free. 100 GB a month, 10 apps, custom domains and pull request staging environments is one of the larger free tiers around. If that's you, stay.
If none of those apply, you're using a full Azure resource to serve a folder of files.
Choosing An Alternative To Azure Static Web Apps
Pick on two things: whether the free tier allows commercial use, and whether the paid plan charges per site. All prices are monthly and as of November 2026.
| Host | Free tier | Paid from (monthly) | Commercial use on free | The catch |
|---|---|---|---|---|
| Azure Static Web Apps | 100 GB per subscription, 10 apps, 2 domains per app | Standard $9 per app | No, hobby or personal | Card needed; free sites stop at quota |
| OxyPages | 1 site, 25 MB, 5,000 page views, no custom domain | Lite $5 ($48 a year): 2 sites; Starter $10: 5 sites | No, personal only | No functions, sign-in or databases |
| Cloudflare Pages / Workers | Unlimited static requests, 500 builds | Workers Paid $5 minimum per account | No clause in the terms; marketed for hobby projects | Two overlapping products |
| Netlify | 300 credits, hard limit | Personal $9 (1,000 credits) | Yes | Deploys and bandwidth burn credits; sites pause at zero |
| GitHub Pages | Public repos, 1 GB site, 100 GB soft bandwidth | Team $4 per user for private repos | No online business or ecommerce | No rewrite rules for SPA routing |
| Vercel | Hobby: 100 GB transfer | Pro $20 per deploying seat | No, personal or non-commercial | Per-seat billing plus usage |
| DigitalOcean App Platform | 3 static apps, 1 GiB transfer each | Extra static apps $3 each | No restriction found | Overage billed at $0.02 per GiB |
OxyPages: Flat Plans Instead Of Per-App Fees
I run this one, so I'll keep it plain. Our free plan is personal use too, and smaller than Azure's: one site, 25 MB, 5,000 page views and no custom domain. The difference is the paid step. Lite is $5 a month for two sites with commercial use and custom domains, and Starter is $10 a month for five, against $45 for five on Standard.
It hosts built React, Vue, Svelte, Vite and Astro output with a single-page app mode, _redirects and _headers, version history and GitHub builds. You can also drop a folder in the browser or deploy from the command line, with no workflow file. It runs no server code, so if your app calls a Functions API or uses the built-in sign-in, OxyPages is the wrong move.
Cloudflare Pages Or Workers
Cloudflare suits sites with unpredictable traffic: static asset requests are free and unlimited, with 500 Pages builds a month and up to 100 custom domains per project. Workers Paid is $5 a month per account. The catch is the product split, since Cloudflare's Pages docs now send new projects to Workers.
Netlify
Netlify suits freelancers, because its free plan explicitly allows commercial projects and custom domains. You get 300 credits a month as a hard limit. Personal is $9 a month and Pro is $20 a month with unlimited members.
The catch is the credit meter: 15 credits per production deploy and 20 per GB of bandwidth, and every project pauses at zero.
GitHub Pages
GitHub Pages suits open-source docs and personal projects, and it's the Microsoft-owned option with no Azure account. It's free for public repos, with a 1 GB site limit and a soft 100 GB of bandwidth a month. GitHub's terms rule out running an online business or ecommerce site on it, and it has no rewrite rules, so React Router apps need a workaround. the GitHub Pages alternatives post covers that trade in detail.
Vercel
Vercel suits personal projects and anything moving towards Next.js. Hobby includes 100 GB of fast data transfer a month and is limited to personal or non-commercial use. Pro is $20 a month per deploying seat, with $20 of usage credit included.
DigitalOcean App Platform
DigitalOcean suits small commercial sites on a tight budget. The free tier covers three static-site apps with custom domains and no non-commercial clause, and extra static apps are $3 a month each. Each free app gets just 1 GiB of transfer a month, with overage billed at $0.02 per GiB, and sign-up needs a payment method for verification.
Moving A Vite Site Off Static Web Apps

Moving a static Vite site off Static Web Apps takes about 20 minutes plus DNS time. Here's the order I'd follow, whichever host you choose.
- Build locally. Run
npm run buildand check thedistfolder with a local preview. - Translate
staticwebapp.config.json. The part that matters for a single-page app is the fallback rule:
{
"navigationFallback": {
"rewrite": "/index.html"
}
}
On hosts that read a _redirects file, that becomes /* /index.html 200, saved in Vite's public folder so it ends up in dist. Without it, refreshing an inner page returns a 404. Why a refresh returns a 404 and how to fix it explains the cause, and MDN's definition of a single-page app covers why the server has to cooperate.
- Move headers and redirects. Anything under
globalHeadersgoes in a_headersfile, and route redirects go in_redirects, on hosts that support them. - Check for Azure-only features. Search your code for
/api/and/.auth/. Either one means the app uses Functions or the built-in sign-in, and a static host can't serve those routes. - Deploy, test, then move the domain. Click every route and refresh each one, then lower your DNS TTL and point the domain at the new host.
- Clean up Azure. Delete the workflow file from
.github/workflowsso pushes stop deploying, then delete the Static Web App resource. A Standard app keeps billing until you do.
What To Do Next
Search your repo for /api/ and /.auth/. If neither appears and your staticwebapp.config.json only holds a fallback rule, your site is a static build, and any host in the table can serve it.
If they do appear, stay on Static Web Apps. Its Functions and sign-in are the reason it exists.
If you're static and paying per app, add up what your sites cost today and compare it with a flat plan. When you're ready to move commercial sites with custom domains, compare the OxyPages plans and test one build on a free account first.
FAQ
Can I Use The Azure Static Web Apps Free Plan Commercially?
Microsoft says the free plan "is intended for hobby/personal usage and does not come with SLA", and labels Standard as the plan for production apps. If your site earns money, Standard is the plan Microsoft points you to. It costs $9 per app per month in most US and EU regions as of November 2026.
How Much Does The Azure Static Web Apps Standard Plan Cost?
Standard is $9.00 per app per month in most US and EU regions, $10.80 in Malaysia, Indonesia and Southeast Asia 3, and $12.60 in Chile, as of November 2026. Each subscription includes 100 GB of bandwidth, then $0.20 per GB. There's no per-seat charge.
What Happens When A Free Static Web App Runs Out Of Bandwidth?
The site stops serving. The free plan's 100 GB a month is shared across the whole subscription, and overage isn't available on Free, so every free app in that subscription shares one pool. Upgrading to Standard lifts the stop and bills overage instead.
Is GitHub Pages A Good Replacement?
For personal and open-source sites, yes: it's free for public repos and needs no Azure account. It isn't allowed as free hosting for an online business, and it has no rewrite rules for single-page app routing. Weigh those two limits before treating it as your alternative to Azure Static Web Apps.