There is no single best Netlify alternative. Cloudflare Pages fits static content, Vercel fits Next.js, Render fits a long-running server, and Fly.io fits anyone who wants to choose where containers run. That split matches the shortlist rules in the 2026 comparisons from Render and Omid Saffari, though one is a vendor and the other carries partner links, so read both with that in mind. Below you get a decision table by project type, a pricing-model comparison that separates new credit accounts from legacy ones, a migration checklist and a recommendation per project. Prices move, so check each provider's own pricing page before you commit.
Why teams leave Netlify (and why some should not)
Netlify moved new accounts to credit-based plans, and its changelog from September 5, 2025 says a single credit balance replaces 15+ separate metrics. Render's article dates the switch for all new accounts to September 4, 2025. Tidy on paper. The catch is that production deploys, bandwidth, compute, form submissions and web requests all draw from the same pool, so a busy deploy month and a busy traffic month compete for the same credits.
The reasons people actually move tend to fall into four groups:
- Credit economics. On the Free plan, 300 credits is a hard limit. Render says projects pause until the next billing cycle once it runs out, and there is no auto recharge on Free.
- Workflow. You want previews, rollbacks and pull request feedback somewhere your framework vendor controls, or you want your CDN, DNS and functions under one account.
- Runtime needs. Temps, which competes with Netlify, says synchronous functions time out after 60 seconds on every plan and that Edge Functions run on Deno rather than Node.js. Treat that as a competitor's claim and check Netlify's docs for your own case.
- Team constraints. This one has weakened. Netlify's pricing announcement says seat-based pricing is gone and Pro now costs $20 a month with unlimited seats.
That last point matters for agencies. If per-seat cost was your only complaint, moving to Vercel could put the problem straight back on the table, because Temps reports Vercel Pro as $20 a month with one deploying seat plus $20 for each extra one.
Sometimes leaving is the wrong move. If your sites are small, your credits last the month and you use Netlify Forms, a migration costs you time for no gain.
Decision table: Cloudflare Pages, Vercel, Render and Fly.io
Start with the provider view. Entry prices come from the sources named, with dates, and they buy different things: a tiny virtual machine, a request allowance and a seat are not equivalent.
| Platform | Best fit | What it does well | Trade-offs |
|---|---|---|---|
| Cloudflare Pages | Static sites, edge logic | Render says static asset requests are free and unlimited on free and paid plans. Workers Paid starts at $5 a month per Omid Saffari (3 November 2026). | Pages Functions bill as Workers. Temps lists the free dynamic tier as 100K requests a day with 10 ms CPU. Node-shaped code may need rework. |
| Vercel | Next.js apps | Vercel says ISR and image optimisation run on infrastructure built for how Next.js renders and caches. | Pro is $20 a month including one deploying seat, then $20 per extra deploying seat (Temps). Hobby is non-commercial only. |
| Render | Servers, workers, cron, Postgres | Persistent services at a set monthly price per instance. Paid web compute from $7 a month (Omid Saffari). | Temps says free web services spin down after 15 minutes idle and free Postgres expires after 30 days. Less CDN-first than Cloudflare. |
| Fly.io | Containers, placement control | Docker-native Machines. Omid Saffari lists the smallest displayed Machine from about $2.19 a month equivalent. | Temps says new organisations get only a trial (2 machine-hours or 7 days). You own more of the operations. |
Now the same thing by project type, which is how you should really decide.
| Project type | Look first at | Why | Watch out for |
|---|---|---|---|
| Astro or static content | Cloudflare Pages (or Render static sites) | Static assets are cheap to serve, and Vercel itself describes Astro as suited to blogs, docs, marketing sites and portfolios. | Netlify extras such as Forms, Database and Blob storage do not move with you. |
| Next.js | Vercel, or stay on Netlify | Vendor-built ISR and image handling. Omid Saffari still shortlists Netlify for a managed Next.js workflow. | Seat charges on Vercel, and Hobby cannot be used commercially. |
| Edge logic | Cloudflare Workers and Pages | Edge-native runtime, free tier to test on. | Netlify Edge runs on Deno, so expect a rewrite either way. |
| Container or background-heavy apps | Render, then Fly.io | Long-running processes. Render Workflows run TypeScript or Python functions up to 24 hours per run, though they are not HTTP handlers. | Fly.io wants you to think about regions and Machines. |
How the pricing models compare
Same word, different meters. That is the main thing to grasp before comparing sticker prices.
New Netlify credit accounts
Accounts created on or after September 4, 2025 sit on credit-based plans. Per Netlify's pricing page:
- Free is $0 with a 300 credit monthly limit.
- Personal is $9 a month with 1,000 credits.
- Pro is $20 a month with unlimited members, starting at 3,000 credits and scaling by tier up to 20,000.
- Add-on credits need auto recharge, which is off by default: $5 for 500 on Personal, $10 for 1,500 on Pro.
- Concurrent builds: 1 on Free, 1 on Personal, 3 on Pro, with extras at $40 each on paid plans.
- Every new project starts private and becomes public when you publish. Deploy Previews and branch deploys are unlimited.
The credit rates are where sources disagree. The September 2025 changelog lists production deploys at 15 credits, compute at 5 credits per GB-hour, bandwidth at 10 credits per GB and web requests at 3 credits per 10,000. A LICENSEWARE wiki page and Figment list 10 credits per GB-hour, 20 credits per GB and 2 credits per 10,000. The changelog also shows Pro at 5,000 credits, while the live page starts it at 3,000. So the rates have probably changed since launch. Before you model a bill, pull the current numbers from Netlify's credit docs. Flexprice converts the $10 pack into roughly $0.13 per GB of bandwidth and about $0.10 per production deploy, but that rests on the newer rates. The longer breakdown is in our Netlify pricing explainer.
Legacy Netlify accounts
Netlify's legacy billing FAQ defines a legacy plan as a team account created with a Free, Starter or Pro plan before September 4, 2025. Netlify says those accounts can keep their plan with no changes needed, and legacy Pro customers can switch to credit plans at any time. Forms are different too: on legacy plans, enabling form detection puts a site on Forms Level 0, with 100 submissions and 10 MB of uploads a month. Render's article makes the same 100-per-site point for legacy Free and Starter.
If you are on a legacy plan and your bill is fine, there is no deadline forcing you out. Check the Usage and billing dashboard before assuming anything.
The alternatives, by what they meter
- Cloudflare: requests and Workers usage, with static assets free per Render.
- Vercel: a platform fee plus deploying seats, with usage caps (BirJob reports Hobby capped at 100K function invocations and 100 GB of bandwidth).
- Render: a monthly price per instance type, prorated to the second per Render.
- Fly.io: Machine time, so you pay for what is running.
Treat one source with care: NextByte lists Netlify Pro at $19 per seat a month, which contradicts Netlify's own flat $20 with unlimited members. Ignore that figure.
Migration checklist
Most failed moves are not really about the host at all. They fail on something small that nobody wrote down: a redirect rule, a form, a variable scoped to one context. If you would rather hand this over, there is a site migration service that covers the DNS cutover and redirect checks for you.
- Inventory first. List every Netlify feature the site touches: redirects, headers, forms, functions, Edge Functions, Identity, Blob storage, Database. Render warns that Netlify extras like Database and Blob storage do not move with you.
- Redirects and headers. Export your redirect rules and header rules and translate them to the new host's format. Then crawl the old production site, save every URL and status code, and test the same list against the new build.
- Environment variables. Netlify lets you scope variables per deploy context, such as staging against production. Recreate each variable per environment on the new host, and rotate any secret that lived in a shared team variable.
- Forms. Netlify form handling is a hosted feature. On credit plans Netlify's changelog lists 1 credit per submission, while Render says forms are free and unlimited on credit plans. Whichever is right, plan a replacement endpoint (your own function, or a third-party form service) and test a real submission.
- Functions. Check runtime, timeouts and paths. Netlify functions live under their own path convention, so front-end calls may need updating. If you use Edge Functions, remember Deno and Workers are different environments.
- Previews. Netlify includes unlimited Deploy Previews and branch deploys on credit plans. Confirm how the new host builds pull request previews, whether they are public or protected, and whether your CMS webhook still points at the right place.
- DNS. Lower the TTL on your records a day or two before the cutover so changes spread quickly. Add the domain on the new host, wait for SSL to issue, and only then switch records. Do not move nameservers and hosting in the same hour.
- Rollback. Keep the Netlify site live and deployable until the new one has run cleanly through a full traffic cycle. Netlify lists one-click rollbacks as a feature, so your old site is a ready fallback. Write down the DNS records you started with.
One ordering tip. Do redirects and DNS last, after the new build matches the old one page for page.
Recommendation by project type
No universal winner here. Pick by what the site actually does.
Astro and static content sites
Start with Cloudflare Pages. Static asset requests are free and unlimited per Render, and NextByte claims 500 builds a month and 100 sites on the free tier, a secondary claim, so confirm it on Cloudflare's page. Render static sites are the alternative if you expect to add a backend on the same platform later. For purely static work, Vercel and Netlify are both fine but neither is clearly cheaper.
Next.js
This is the one case where I would not push you off Netlify by default. Vercel builds both the framework and the infrastructure, and says ISR and image optimisation are tuned for it. The price is seat-based billing and non-commercial Hobby limits. If your complaint is credits, test Vercel against your real traffic. If your complaint is only seat cost, Netlify's flat Pro may already fix it. Our Netlify vs Vercel comparison goes through the head-to-head.
Edge logic
Cloudflare. Redirects with logic, geolocation tweaks, auth checks at the edge: the Workers runtime is built for that job, and Workers Paid starts at $5 a month per Omid Saffari. But it is a port, not a copy. Netlify Edge Functions run on Deno, and your code will need testing on the Workers runtime. Our Cloudflare Pages vs Netlify piece covers that pair in more depth.
Container and background-heavy apps
Render if you want a managed web service, workers, cron and Postgres at fixed monthly prices. Fly.io if you care where Machines run and are comfortable owning more infrastructure. Omid Saffari's rule is a good one: Render or Railway when you own a running process, Fly.io when placement and control are requirements. Neither is a drop-in for a Jamstack site, so only move here if the app needs a real process.
Agencies running many small sites
Check two numbers before choosing: how many sites sit near their credit limit, and how many need forms or functions. Mostly static brochure sites with no forms point to Cloudflare Pages. A mixed estate is usually better served by two hosts than by one awkward compromise. For a wider provider view, see our cloud hosting roundup.
FAQ
Will moving hosts hurt my search rankings?
Not by itself. Rankings drop when URLs change, redirects break, pages return errors or the new host serves slower, thinner pages. Keep every URL identical, carry over redirects and headers, and compare a crawl of the old site with the new one before DNS changes.
Should I change any URLs while I migrate?
No. Do one thing at a time. Move the host, confirm everything behaves the same, and only later consider URL restructures or a redesign. Mixing them makes it impossible to tell what caused a ranking change.
How long should I keep the Netlify site after the DNS switch?
Until the new host has handled a normal traffic cycle with no surprises, including any scheduled jobs, form submissions and CMS webhooks. A few days is common, but there is no official figure. Keeping it costs little, and it gives you a rollback target.
Is Cloudflare Pages really unlimited?
Only for static asset requests, per Render. Dynamic requests through Pages Functions use Workers pricing, and Temps lists the free tier at 100K requests a day with 10 ms of CPU. So a mostly static site is cheap to run, while heavy function use is not unlimited.
Do I need to move if I am on a legacy Netlify plan?
No. Netlify says accounts created before September 4, 2025 can keep their plan with no changes needed. Check your Usage and billing dashboard, then decide on cost or runtime grounds, not because of the new plans.
The sharpest caveat is that credit rates differ between Netlify's own changelog and later secondary sources, so price a move from the current Netlify docs, not from any comparison article, including this one. Pick the host by what the project does at request time: Cloudflare for files and edge logic, Vercel for Next.js, Render or Fly.io for processes.