Static site hosting/Surge alternatives/November 2026

Surge alternatives: where six free static hosts stop and what the next plan costs

Surge publishes a folder of built files with one surge command. Between 4 October and 3 November 2026 its pricing page changed, and the free plan now includes certificates on custom domains, --force https and the CORS file. Pro, still $30 a month, now covers only password protection and redirects. People still leave over three things: Surge never runs your build, it serves no functions, and a project tops out at 450 MB or 10,100 files.

Quick answer
  • Surge is alive: npm surge 0.56.0 shipped on 2 November 2026, the same day as the latest GitHub commit.
  • Static traffic with no meter: Surge and Cloudflare Pages both leave it unbilled; Pages adds 500 server-side builds a month.
  • Redirects without the $30 Pro plan: Cloudflare Pages, Netlify, Vercel, Render and Firebase all take redirect rules on their free plans.
  • Free-plan catches: Vercel Hobby excludes commercial use, GitHub Pages needs a public repository, and Netlify pauses every project once credits run out.

Surge plus 6 static hosts · free caps, first paid plan, migration files · last updated 12 November 2026

Free tier and first paid step

How far does each free plan go before you pay?

One row per host. Traffic and build limits are the free plan's; the last two columns are the cheapest paid plan that lifts them, with its billing cycle. None of the seven puts a static site to sleep: Render's 15-minute idle spin-down applies to free web services, not static sites.

Host Free traffic Free builds or deploys Size limits Catch on the free plan First paid step What that step adds
SurgeNot metered, no overageNo server-side build; 30 publishes per domain per 15 min, 200 per day, 500 per account per day450 MB, 10,100 files per projectA limit pauses publishing; the live site keeps serving. Unverified accounts get half the rate.Pro: $30/month per accountPassword protection (AUTH) and redirects or rewrites (ROUTER); publishing limits stay the same
Cloudflare PagesStatic requests free and unlimited500 builds/month, 1 at a time, 20 min each20,000 files, 25 MiB per fileFunctions traffic counts against Workers free limitsWorkers Paid: from $5/month per accountPaid Functions usage, no egress charge. More builds and 100,000 files per site come with Cloudflare Pro or higher; the Pages docs do not price it
Netlify300 credits/month; 1 GB of bandwidth costs 20 creditsEach production deploy costs 15 creditsNot listed on the pricing pageWhen credits run out, every project on the account pauses until the next cyclePersonal: $9/month1,000 credits; extra packs at $5 per 500
Vercel100 GB Fast Data Transfer, 1M CDN requests per month100 deployments/day, 45 min per build200 projects, 50 domains per projectHobby is for personal, non-commercial usePro: $20/month per developer seat$20 usage credit, 6,000 deployments/day, commercial use
GitHub PagesSoft limit of 100 GB/monthSoft limit of 10 builds/hour; deploys time out at 10 min1 GB per siteFree only from public repositories; not meant for commercial transactions or SaaSGitHub Team: $4 per user/monthPages sites built from private repositories
Render5 GB/month, then $0.15 per GB500 pipeline minutes/monthNot listed on the pricing page2 custom domains included, then $0.25 per domain/monthPro: $25/month plus compute25 GB bandwidth, 1,000 pipeline minutes, unlimited seats
Firebase Hosting10 GB/month transferNo hosted build; deploy from the CLI10 GB storage, 2 GB per fileOn Spark, going past the transfer quota disables the sites after a short grace periodBlaze: pay as you go, no monthly fee$0.15 per GB transfer and $0.026 per GB stored past the free 10 GB

Netlify bills bandwidth in credits: 300 free credits ÷ 20 credits per GB = 15 GB a month, and only if the account spends nothing on deploys, requests or compute. Two production deploys (2 × 15 = 30 credits) take that down to 13.5 GB. Prices are list prices in USD, monthly billing, before tax.

Sources, checked 12 November 2026: Surge pricing and limits · Cloudflare Pages limits · Pages Functions pricing · Netlify pricing · Vercel pricing · Vercel limits · GitHub Pages limits · GitHub pricing · Render pricing · Firebase Hosting quotas and pricing

Six hosts

Which host fits which reason for leaving Surge?

Cards follow the table order. The label on each one names the Surge limit it removes.

Cloudflare Pagesfrom $5/mo
Unbilled static traffic

Closest to Surge's no-meter model, plus Git builds and Functions. Watch the 20,000-file cap on the free plan. pages.cloudflare.com

Netlifyfrom $9/mo
Redirect file habits

_redirects and _headers files read like Surge's ROUTER and CORS. Credits make heavy traffic the first thing to run out. netlify.com

Vercelfrom $20/mo
Frameworks with SSR

The biggest free transfer allowance here (100 GB), but Hobby excludes commercial work, and a password prompt costs extra on Pro. vercel.com

GitHub Pagesfree, public repos
Docs next to the code

Deploys on push or from an Actions workflow. No redirect or headers file, and no SPA fallback beyond 404.html. pages.github.com

Render$25/mo + compute
Site plus backend

Static sites are free to deploy next to paid services and databases. Bandwidth past 5 GB is billed per GB. render.com

Firebase Hostingpay as you go
Already on Firebase

A CLI deploy close to surge, with redirects, rewrites and headers in firebase.json. Spark disables sites past 10 GB of transfer. firebase.google.com

Migration checklist

What do you rebuild when you move off Surge?

The built files copy over unchanged. The work is in the small files and flags Surge reads from the project root, listed here with where each host keeps the same setting.

On Surge Cloudflare Pages Netlify Vercel GitHub Pages Render Firebase Hosting
Custom domain + certificate CNAME file; DNS to geo.surge.world, ns1–4.surge.world or an A recordAdded per project, SSL included; 100 domains per project on FreeFree custom domains with SSL50 domains per project on HobbyCNAME plus "Enforce HTTPS" (Let's Encrypt)Managed TLS; 2 domains on Hobby, then $0.25/month eachCertificate provisioned automatically
Deploy command surge ./dist example.comnpx wrangler pages deploy ./distnetlify deploy --prodvercel --prodPush to the publishing branch or run an Actions workflowBuilds from the connected Git repositoryfirebase deploy --only hosting
200.html SPA fallback with a 200 statusAutomatic when the build has no top-level 404.htmlRewrite rule to /index.html with status 200Rewrite in vercel.jsonNone 404.html onlyRewrite rule in the dashboardrewrites in firebase.json
ROUTER redirects, Pro only_redirects: 2,000 static + 100 dynamic rules_redirects or netlify.tomlredirects in vercel.jsonNoneDashboard rules; not on the domain rootredirects in firebase.json
CORS file free since autumn 2026_headers_headersheaders in vercel.jsonNoneCustom headers in the dashboardheaders in firebase.json
AUTH password protection, Pro onlyCloudflare Access, a separate productPro plan onlyPro add-on, $20/month per projectPrivate sites need Enterprise CloudNone documented for static sitesNone built in

Surge also accepts --force https on the free plan. Rebuild the AUTH and ROUTER rules before you switch DNS, because no other host reads those two files as they are.

Sources, checked 12 November 2026: Surge custom domains · Surge 200.html · Surge redirects · Pages redirects · Netlify redirects · Vercel password protection · GitHub Pages visibility · Render redirects · Firebase Hosting config

Sources and dates

How we checked

On 12 November 2026 we read each host's pricing page and limits documentation, requesting Netlify's page with a US country cookie so it returned dollar prices. The date of Surge's pricing change comes from Wayback Machine captures of surge.sh/pricing taken on 4 October and 3 November 2026. Maintenance status comes from the npm registry entry for the surge package and the sintaxi/surge repository on GitHub, read the same day. Rows marked "not listed" are limits the vendor does not publish on the pages above.

Questions

Surge: maintenance, pricing and staying put

Is Surge still maintained in 2026?

Yes. The surge package on npm reached version 0.56.0 on 2 November 2026, its 55th release of the year; before 0.24.7 in February 2026 the previous version dated from August 2024, and the sintaxi/surge repository on GitHub had its latest commit the same day; it is not archived and lists 193 open issues. The repository's Releases tab still stops at v0.19.0 from March 2017, which is why older write-ups called the project frozen, but the version tags continue past it.

What changed on the Surge pricing page in autumn 2026?

Archived copies of surge.sh/pricing up to 4 October 2026 show a free plan with basic SSL and a $30/month Professional plan that held custom SSL, forced HTTPS, CORS, redirects and password protection. The capture from 3 November 2026 shows the current layout: certificates on custom domains, --force https and the CORS file are free, and Pro at $30/month adds only password protection (AUTH) and redirects or rewrites (ROUTER).

Does Surge charge for bandwidth?

No. Its pricing page says nothing is metered and there is no overage charge. The limits are on publishing instead: 30 publishes per domain every 15 minutes, 200 per domain per day, 500 per account per day, and 450 MB or 10,100 files per project. Hitting one pauses publishing for a while; the site keeps serving.

Which alternative keeps static traffic unmetered like Surge?

Cloudflare Pages. Its docs say requests to static assets are free and unlimited on free and paid plans, and the free plan allows 500 builds a month and 20,000 files per site. Netlify, Vercel, Render and Firebase all count bandwidth on the free plan; GitHub Pages has a soft 100 GB monthly limit.

When does staying on Surge make more sense than moving?

When the site is a folder of built files, you deploy from a terminal or CI token, and you do not need redirects or a password prompt. That setup now costs nothing on Surge, with no bandwidth bill. Moving pays off when you want the host to run your build, serve functions, or handle redirects without the $30 monthly Pro plan.