
Netlify alternatives: where your forms and functions go
Aron Wagner
CEO & Co-Founder
Picking a Netlify alternative comes down to what your site uses from Netlify. Any host serves static files, so the HTML is the easy part. Your redirect rules, Netlify Forms and Functions are what don't move on their own. On a server you own, all of them run as nginx rules and one small Node service, for a bill that traffic doesn't change.
Why are people leaving Netlify?
Credits. Since September 4, 2025, new Netlify accounts pay in credits, and one pool covers almost everything: a production deploy costs 15 credits, a GB of bandwidth costs 20, and 10,000 web requests cost 2. Form submissions are free, and build minutes are no longer billed on their own. Accounts opened before that date can keep their legacy plans.
The free plan gets 300 credits a month. That's 20 production deploys before anyone visits the site. Personal is $9 for 1,000 credits and Pro is $20 for 3,000, with extra packs of 500 for $5 on Personal or 1,500 for $10 on Pro.
The bigger problem is running out. When the credits are gone, every project on the account pauses: visitors get a "Site not available" page, forms stop taking submissions, and deploys stop. It happens on the free plan, which can't buy more credits, and on paid plans with auto recharge off, which is the default. One busy project takes the quiet ones down with it.
Here's one month of a small business site that deploys once a day and serves 100 GB:
What does your Netlify site actually use?
Before you compare hosts, list what Netlify does for your site. Four things decide where it can go:
- Redirect and header rules: a
_redirectsor_headersfile in the publish folder, or[[redirects]]and[[headers]]blocks innetlify.toml. - Forms: any
<form>with anetlifyordata-netlify="true"attribute. Netlify collects those submissions for you. - Functions: a functions folder, including scheduled functions and background functions that run for up to 15 minutes.
- Deploy previews: a URL for every pull request, on every plan.
Search the repo for those file names and that attribute, and you have your list. A site with none of them is a folder of files, and every host below serves it.
Where does each Netlify feature land?
| Host | Redirect and header rules | Forms | Functions | Previews |
|---|---|---|---|---|
| American Cloud (your own server) | nginx rules, from your files | An endpoint in your Node service | Routes in that same service | Coolify, or a second server |
| Cloudflare Pages | Reads _redirects and _headers, with limits | A function you write | Pages Functions, billed as Workers | A URL per pull request |
| Vercel | vercel.json | No forms product | Vercel Functions | A preview per branch and pull request |
| Firebase Hosting | firebase.json | A function you write | Cloud Functions, on the Blaze plan | Preview channels |
| Render (static site) | Set in the dashboard | None | None on a static site; add a web service | A preview per pull request |
Cloudflare Pages is the only one that reads Netlify's own files, and not all of them: it skips query-parameter matches, 404 rewrites and domain-level redirects, takes up to 2,000 static and 100 dynamic redirects and 100 header rules, and none of it applies to responses from its functions. Vercel, Firebase and Render want the same rules in their own config, so each line gets rewritten once.
None of the four has a Netlify Forms. Each form becomes a small function you write that stores the submission somewhere. Cloudflare's Static Forms plugin hands the submission to your code, and a Render static site runs no server code at all.
On your own server, the same four things are config and one process. nginx serves the build folder and applies your redirect and header rules. One Node service holds the function routes and a form endpoint, so submissions land in your own store. Scheduled functions become systemd timers. It's often simpler than what it replaces. The process is always warm, so there are no cold starts, and nobody bills you per call.
Want a preview URL for every pull request and git-push deploys back? Run Coolify or Dokploy on the server. Both are open-source platforms you host yourself. Coolify is free to self-host, and its docs suggest at least 2 CPUs and 2 GB of memory. On American Cloud, a 2 vCPU, 2 GB, 50 GB server is $33.13 a month.
You can own the server on a budget VPS too. Hetzner's smallest dedicated-CPU server in the US, with 2 vCPU and 8 GB, is $50.99 a month with 1 TB of outbound traffic and $1.20 for each TB past it. The same size on American Cloud is $65 a month, traffic isn't metered, and when something breaks, our support replies in under 2 minutes.
What does the same site cost on each?
Take a site that deploys once a day (30 production deploys a month), serves 100 GB or 500 GB a month at about 1 million requests per 100 GB, and has no forms or functions. Prices are each host's US list price on November 20, 2026.
| Host | 100 GB a month | 500 GB a month |
|---|---|---|
| American Cloud, smallest server (1 vCPU, 1 GB, 25 GB) | $16.56 | $16.56 |
| Netlify Pro | $20 | $80 |
| Netlify Personal | $29 | $114 |
| Netlify Free | Paused | Paused |
| Render (Hobby) | $14.25 | $74.25 |
| Firebase Hosting (Blaze) | $13.50 | $73.50 |
| AWS Amplify Hosting | $12.75 | $72.75 |
| DigitalOcean App Platform (free static app) | $1.84 | $9.29 |
| Cloudflare Pages | $0 | $0 |
Render, Amplify and Firebase charge $0.15 a GB past a free allowance (5 GB, 15 GB and about 10 GB), and DigitalOcean $0.02 a GiB past 1 GiB. Ours is the flat monthly price, with no traffic charge. Vercel Pro is $20 a month and bills traffic through flat-rate tiers, which our Vercel alternatives post works through for Next.js apps.
Looking for a free Netlify alternative? For a site that's only files, four hosts have a free tier. Cloudflare Pages serves static files free with no traffic charge and 500 builds a month. DigitalOcean gives three static sites free with 1 GiB of traffic each. Firebase's free tier covers about 10 GB a month and then disables the site. GitHub Pages takes a 1 GB site and a soft 100 GB of traffic a month, and its terms rule out running an online business or a SaaS on it.
A form or a function changes the math. Cloudflare bills functions as Workers, with a $5 monthly minimum on the paid plan. Firebase runs them on Cloud Functions, which needs the pay-as-you-go Blaze plan. Render wants a separate web service. On your own server, it's one more process on the same $16.56 machine.
How do you move a Netlify site to your own server?
- Plan and price. Pick the server size and set its monthly price against your Netlify bill.
- Provision. Create the server, build the site and point nginx at the build folder.
- Map the features. Work down your feature list until every item runs on the server.
- Cut over. Lower your DNS TTL ahead of time, check the site on the new server, then switch the records. If your domain is on Netlify DNS, move the zone first.
- Decommission. Leave the Netlify site up until the new server has proven itself, then retire it.
Our Migrate from Netlify playbook runs these steps as one conversation with your AI assistant and the American Cloud MCP server: it reads the repo, prices the server, builds it and translates the rules, and the planning phases change nothing in your account.