The Best Vercel Alternatives in 2026: The Same Full-Stack App Priced on 6 Platforms

I priced one full-stack app, a Next.js site with Postgres and a background worker, on six Vercel alternatives. At 1 million page views a month (about 1 TB of traffic) and a 10 GB database, it costs $30 on Cloudflare, $71 on Fly.io or Railway, $195 on Netlify and $203 on Render. On Vercel, with the database and worker it can't host itself, it's $152. On a rented server with Ployz it's $16.

Prices checked 2026-10-01, every one from the platform's own pricing page or docs, linked next to the number. All prices are USD before tax.

Most "best Vercel alternatives" lists I read compare free tiers and feature checkboxes. None of them price the same app on every platform, and most skip the part that hurts: Vercel doesn't run your database or a long-running worker, so a full-stack app on Vercel is really two or three bills. I've lived that. Railway cost me $500+ a month at its peak, mostly the database. Today one €80 dedicated server runs more than I ever ran there. So I'm biased toward renting a server, and the maths is below so you can check me.

What would your app cost on each Vercel alternative?

Move the sliders to match your app. Every row prices the same three pieces: the Next.js site, a Postgres database and a small background worker. The assumptions behind each row are in the sections below.

What app did I price?

The reference app is a Next.js site with server-rendered pages, a Postgres database and a background worker that sends emails and processes jobs. At the default sliders it serves 1 million page views a month at 1 MB each (1 TB of transfer), makes 20 requests per page view, and keeps a 10 GB database. These are assumptions, not measurements.

The details, so you can adjust them:

• Pages: 1 MB transferred per page view, 20 requests per page view (HTML, JS chunks, CSS, fonts, images, one API call), one server render per page view with 30 ms of CPU and 250 ms of wall time.
• Database: Postgres, 10 GB, about 20 KB of query results per page view. Past 10 GB I move every managed database up one size, because 1 GB of RAM stops being enough.
• Worker: a small always-on process, 256 to 512 MB of RAM, mostly idle. On Netlify and Cloudflare, which can't run an always-on process, I assume you rewrite it as background functions or a queue consumer.
• Team: one person deploying, 30 production deploys a month.

Where a platform has no Postgres of its own that I could price, I used Supabase Pro: $25 a month including a Micro compute, 8 GB of disk then $0.125 per GB, and 250 GB of egress then $0.09 per GB. Past 10 GB I use the Small compute (~$15, 2 GB RAM), which Supabase recommends for databases up to 50 GB. My Supabase pricing breakdown goes deeper.

What does the same app cost on each platform?

At 1M page views, 1 TB and a 10 GB database: Cloudflare $30, Fly.io $71, Railway $71, Vercel's split stack $152, Netlify $195, Render $203, own server $16. Bandwidth decides most of these bills. Render and Netlify charge about $0.13 to $0.15 per GB, Railway $0.05, Fly.io $0.02, and Cloudflare and a Hetzner server nothing at this size.

The middle column, line by line:

For the Vercel line, I used the same model as my Vercel pricing breakdown: 20M CDN requests put this app in the $100 Flat Rate CDN tier, and its functions use about $7 of the $20 credit.

Is Cloudflare a good Vercel alternative?

On price, Cloudflare is the cheapest platform here: $30 a month for the reference app, and $25 of that is the database. Workers Paid is $5 a month with 10 million requests and 30 million CPU milliseconds included, static assets are free, and there's no bandwidth charge. The catch is shape. Next.js needs an adapter, and an always-on worker doesn't exist.

From the Workers pricing page: past the included amounts it's $0.30 per million requests and $0.02 per million CPU milliseconds, and "there are no additional charges for data transfer (egress) or throughput (bandwidth)." Requests to static assets "are free and unlimited", so only the server render counts.

What you trade:

• Next.js runs through the OpenNext Cloudflare adapter, not natively. Most features work; test yours before you move.
• Limits: 128 MB of memory per isolate and up to 5 minutes of CPU per request on Paid. Fine for pages, tight for heavy jobs.
• No Postgres. You bring one (I priced Supabase) and connect through Hyperdrive, which is unlimited on Paid.
• No long-running worker. You rewrite it as a Queues consumer (1M operations a month included, then $0.40 per million) or Cron Triggers.

If your app already fits in functions and you're happy with a hosted database, I think Cloudflare is the best Vercel alternative on price. If you have a real worker process, it's a rewrite.

Is Netlify better than Vercel?

Not for this app. Netlify is $195 a month against $152 for Vercel's split stack, because Netlify charges 20 credits per GB of bandwidth, about $0.13 per GB once you buy extra credits. Netlify wins on seats: Pro is $20 a month for the whole team, while Vercel charges $20 per deploying seat.

Netlify moved to credits. From the pricing page and credit docs:

Web requests include "HTML pages, images, JavaScript, CSS files, and other static assets", so all 20 requests per page view count. At 1 TB, bandwidth alone is 20,000 credits, nearly seven times what Pro includes. And if credits run out without auto recharge, "all of your web projects (sites/apps) are paused."

Background Functions run up to 15 minutes, which covers most jobs if you rewrite the worker. Netlify also has its own Postgres, Netlify Database, built on Neon, but its billing page prices compute at 10 credits "per unit" without saying what a unit is, so I priced Supabase instead.

Is Render or Vercel better?

For a full-stack app, Render fits better, because it runs the web app, the worker and Postgres in one place. It doesn't cost less at volume, though: $203 at 1 TB, mostly bandwidth at $0.15 per GB past the first 5 GB. Under about 100 GB, Render is $66 against $72 for the Vercel split stack.

From Render's pricing page: the Hobby workspace is $0 with one seat and 5 GB of bandwidth; Pro is $25 a month with unlimited seats and 25 GB. Compute is per service.

I used the 2 GB web instance because Next.js server rendering on 512 MB is tight. Render also has zero-downtime deploys, preview environments and point-in-time recovery for Postgres. My Render pricing breakdown has the full table.

Is Railway cheaper than Vercel?

Yes, for this app: $71 a month against $152. Railway bills what your services use, about $10 per GB of RAM and $20 per vCPU a month, plus $0.05 per GB of egress. A mostly idle app costs little. A busy database costs a lot, which is how my own Railway bill got past $500.

From Railway's pricing page:

I assumed the three services average 1.75 GB of RAM and 0.1 vCPU. That's the number to check in your own metrics: double the RAM and the bill grows by $17.50. At 1 TB, egress is $50, the biggest line. More in my Railway pricing breakdown.

Is Fly.io cheaper than Vercel?

Yes: $71 a month against $152, and the gap grows with traffic because Fly.io's egress is $0.02 per GB in North America and Europe. Machines are cheap, a 1 GB web Machine is about $6.69 a month. Managed Postgres is the big line, from $38 a month, because every plan includes high availability and backups.

From Fly.io's pricing page and Managed Postgres pricing, in iad:

The Machine prices are Fly's pricing-page rates for iad: about $0.69 per shared vCPU plus $6 per GB of RAM a month. Fly has no plan fee; support starts at $29 a month if you want it. You can run Postgres on a Fly Machine with a volume for a few dollars, but Fly calls that "unmanaged" and unsupported.

Is your own server a real Vercel alternative?

Yes, if you're willing to look after it. The reference app costs $16 a month on a Hetzner CX23 with Ployz, and $20 on a CX33 once the database passes 10 GB or traffic passes 5M views. The web app, worker and Postgres share one box, and 20 TB of traffic is included. You give up the global CDN, managed database backups and someone else on call.

Hetzner's CX servers are in Germany and Finland only. I'd look at Netcup first: more disk for the money, and a US datacenter in Manassas. I used Hetzner in the calculator because it publishes USD prices.

Five million page views is about two a second on average. At 30 ms of CPU each, a 4 vCPU server is mostly idle. The database is the part to respect: on your own server, backups are your job. A nightly pg_dump copied to object storage is the minimum, and restoring it once before you need it is the step people skip.

I build Ployz, which runs this setup on a server you rent: push to GitHub, it builds and deploys with zero downtime once you set a health check, gives every pull request a preview environment, and adds Postgres and a worker as services on the same box. It's free on your own servers; custom domains are $9 a month. It doesn't back up your database, so the pg_dump advice stands.

Other ways to run your own server, fairly: Coolify and Dokploy are open-source panels that do the same job and do things Ployz doesn't, including scheduled database backups (Coolify, Dokploy) and Docker Compose files. Kamal and Dokku are leaner if you like the terminal. The server bill is the same whichever you pick.

Vercel too expensive? What's the cheapest way off Vercel onto your own server?

One VPS, a free deploy tool, and your Next.js app running with next start or in Docker, which the Next.js self-hosting docs cover. The server is the whole bill: a Netcup VPS 500 at €8.26 a month incl. VAT, or a Hetzner CX23 at about $7 in Europe. Coolify, Dokploy and Ployz are free on your own server; Ployz custom domains add $9 a month, which is how the reference app lands at $16.

Vercel usually gets expensive in one of three places: seats at $20 a person, usage past the Pro credit, or the database and worker you pay for elsewhere because Vercel can't run them. On a server, all three go away. Seats are free, traffic is included, and Postgres and the worker share the box.

The order I'd do it in:

1. Rent the server and install the deploy tool. Pick Netcup's Manassas datacenter if your users are in the US.
2. Deploy the app to a temporary hostname with the same environment variables as Vercel's Production environment.
3. Move the database last, with a pg_dump and restore during a quiet hour, if it's leaving its current host at all. A hosted Postgres works fine from a VPS.
4. Switch DNS, and keep the Vercel project for a week so rolling back is one DNS change.

What you lose is the global CDN and Vercel's edge network. For most apps with users in one region, a CDN in front of the server (or none) is fine. If your traffic is spread over every continent, Cloudflare from the table above keeps the edge and still costs less.

Is there a free Vercel alternative?

For a full-stack app, not really. Cloudflare's free Workers plan allows 100,000 requests a day, Netlify Free gives 300 credits (about 15 GB of bandwidth), Render's free web services spin down after 15 minutes idle and free Postgres expires after 30 days, and Railway Free includes $1 of usage a month. Each runs a demo. None runs a real Next.js app with Postgres and a worker for free.

Vercel's own free plan, Hobby, is for personal, non-commercial use; I covered where its limits bite in Is Vercel free?. The cheapest paid full-stack setup in this article is $16 on your own server, then $25 to $30 on Cloudflare or Railway.

Which Vercel competitors should you skip?

It depends on your traffic. If you serve more than a few hundred GB a month, skip the platforms that charge $0.13 to $0.15 per GB: Render and Netlify both pass $800 at 5 TB. If you have a real worker process, Netlify and Cloudflare mean a rewrite. If you have a team, per-seat pricing like Vercel's adds $20 per person.

The fees that don't show up on pricing pages are collected in the hidden costs of PaaS, and if seats are what's driving you away, the Vercel Pro plan breakdown shows when $20 stops being $20.

Which Vercel alternative should you pick?

Pick Cloudflare if your app fits in functions, you're fine with a hosted Postgres, and you want the lowest platform bill with a global network. Test the OpenNext adapter first.

Pick Fly.io or Railway if you want containers, a real worker process and a managed platform for about $71 at 1 TB. Railway is simpler; Fly.io is cheaper on bandwidth and has managed Postgres with backups.

Pick Render if you want everything in one dashboard with managed Postgres and your traffic stays under about 100 GB a month.

Pick Netlify if your site is mostly static and you have a team that would otherwise pay per seat.

Pick your own server if you run a database and a worker, your traffic is steady, and you can take on OS updates and backups. One $16 to $20 server covers what costs $71 to $203 on the platforms above, and the bill doesn't move when your traffic does.

Ployz turns that server into a deploy platform with preview environments and zero-downtime deploys, and it's free on your own servers.