Next.js

Vercel Alternatives: When Self-Hosting Next.js on a VPS Makes Sense

A plain guide to Vercel alternatives, sorted by situation. It shows the cost maths, the ops trade-offs and the exact cases where a VPS beats a managed platform.

Saqib ZahoorSaqib ZahoorFull Stack Web DeveloperNov 22, 202610 min read

Vercel alternatives fall into four groups: other frontend clouds, managed container platforms, self-hosted PaaS tools and bring-your-own-cloud setups. Self-hosting Next.js on a VPS makes sense when your bandwidth or seat count drives the bill up, when you need long-running jobs, or when data must sit in a specific region. Otherwise, staying put is often cheaper.

WeboTech Studio builds Next.js and React sites and web apps for founders and teams in Saudi Arabia, the GCC and worldwide. We build them so they are portable: they run on Vercel today and on a Docker container tomorrow. This guide gives you the decision rules we would want a client to have.

The short answer

Pick by situation, not by hype.

  • Small team, spiky or low traffic: stay on Vercel. The seat fee is small and you pay no ops time.
  • Rising bills, steady traffic, one or two developers who can run a server: a VPS behind a CDN usually wins.
  • Want less lock-in but no server work: a managed container platform is the middle road.
  • Strict data location or long jobs: self-host, or use your own cloud account.

The rest of this guide shows the maths behind each line.

Why teams look for a Vercel alternative

Most searches start with a bill. A few start with a limit the platform cannot move. Here are the three common triggers.

Per-seat pricing

Vercel Pro costs $20 per seat per month and includes 1 TB of bandwidth and 1,000 build minutes, according to Pagepro. Three developers means $60 before any usage. A solo founder will barely notice. A growing team will.

Since September 2025, Pro also works on a credit model: $20 in flexible credits plus allowances for bandwidth and edge requests, and viewers do not need a paid seat, as Fencode reports.

Bandwidth and usage overages

Overage figures conflict between sources. Pagepro reports $40 per 100 GB above the 1 TB on Pro. Fencode reports $0.15 per GB after 1 TB, so 1.5 TB adds $75. Check Vercel's own pricing page before you model your costs, because plans change.

One source also describes a spike where a crawler pulled about 8.4 TB of media and produced a $1,477 invoice, per CheckThat. Treat it as a warning about uncapped usage, not as a typical month.

Serverless limits and lock-in

Functions on Vercel Pro default to 300 seconds and max out at 800 seconds. A self-hosted server has no execution limit, as Adamarant notes. That matters for report generation, video work, imports and AI jobs.

The Hobby plan is free but non-commercial only, per ComparEdge. If you earn money from the site, you are on a paid plan.

The four types of Vercel alternative

Most roundups, such as the ones from DigitalOcean and Encore, list 8 to 14 platforms. They group neatly into four families, which Qovery also uses. We name types, not vendors, because the type is what decides your fit.

Type What it is Best for
Frontend or edge platform Same git-push flow as Vercel, from another company Marketing sites and light apps
Managed container platform You ship a Docker image, they run it Full-stack apps with a database
Self-hosted PaaS An open-source dashboard on your own server Teams who want push-to-deploy on a VPS
Bring your own cloud A control layer over your own cloud account Teams with compliance or cloud credits

Frontend platforms swap one bill for a similar one. Container platforms remove the serverless limits. The last two give you the most control and ask the most of your team.

Can Next.js run outside Vercel? What the docs say

Yes, with every feature. The Next.js docs say a single next start process on a Node.js server handles Server Components, ISR, PPR, Server Actions and after(). Extra infrastructure such as CDN caching, edge compute and a shared cache mainly improves performance and multi-instance consistency.

Node server, Docker, static export

The official deploy guide lists three routes:

  1. A Node.js server running next start.
  2. A Docker container. Setting output: "standalone" gives you a minimal image.
  3. A static export, which does not support features that need a server.

For most business sites and apps, option two is the sweet spot. It runs the same on a VPS, a container platform or your laptop.

What changes with multiple instances

One instance is simple. Two or more need care:

  • Cache: with Kubernetes, each pod keeps its own cache copy. A custom cache handler keeps ISR and the data cache consistent. That note comes from an older docs version, so check the current docs before you build.
  • Streaming: your reverse proxy must pass streamed responses through without buffering.
  • Images: image optimisation uses server CPU, so plan for it or put a CDN in front.

If you stay on one instance, none of this applies. Many sites never need a second one.

Vercel vs VPS: the real cost

Cost posts disagree, and many ignore your time. Here is a fair way to work it out.

Cost assumptions and a worked example

One source cites roughly €6 to €20 a month for a small VPS, against $20 per deploying developer on Pro, per Legacies. Makerkit estimates a 250k-visitor workload with 3 seats at about $305 a month on Vercel against $30 on a VPS behind a CDN. Those are the publishers' own estimates, not a quote for your site, so run your own numbers.

A simple worked example using the sourced rates: a team of three on Pro pays $60 in seats. If traffic reaches 1.5 TB, the overage is $75 at the $0.15 per GB rate. That is $135 a month, against a VPS in the tens of dollars.

Break-even

Three numbers move the line: seats, bandwidth and requests. One model puts break-even near 7.3 million requests a month. Below it, Vercel Pro's credit usually wins. Above it, a fixed-cost VM does. It assumes about 100 ms of active CPU per request and a VM at around $30 a month, per Markaicode.

Makerkit's advice is to start on Vercel and move to a Docker VPS once the bill passes roughly $100 a month. That is a reasonable rule of thumb, not a law.

The hidden cost, which is ops time

The cheap VPS figure ignores your hours. Legacies puts maintenance at 2 to 4 hours a month. Price that at your own rate. For a solo founder or a two-person team, Legacies concludes Vercel is usually cheaper overall. We agree.

When self-hosting on a VPS makes sense

Self-host when most of these are true:

  • Your monthly Vercel bill passes about $100 and keeps growing.
  • Traffic is steady, not spiky, so a fixed server is used well.
  • You serve heavy media or large downloads, which drives bandwidth.
  • You need jobs that run longer than serverless limits allow.
  • Your data must live in a chosen country or region.
  • Someone on the team is comfortable with Linux, Docker and backups.
  • You want to move later, and you value owning the setup.

If you tick only one or two, the saving may not cover the work.

Not sure which setup fits your app and traffic? Talk to us about a Next.js build that stays portable, and get a fixed-scope quote after a call.

Planning a portable Next.js build

The cheapest migration is the one you planned before launch. We build Next.js and React sites and apps so the hosting choice stays open: standalone output, a clean Dockerfile, environment variables kept out of code and no hard ties to one platform's special features.

Our Next.js and React development work and custom web apps go from brief to launch and support, with you talking directly to the senior developer building it. We agree a fixed scope in writing before work starts. Our profile does not list managed hosting or server maintenance, so we will not promise to run your infrastructure. We build the app, launch it on the setup you choose and support it afterwards.

Our background: 6+ years building sites and web apps, 230+ projects delivered, and 150+ reviews on Fiverr and Upwork, averaging 4.9 and 5.0.

When it doesn't make sense

Stay on a managed platform if any of these fit you:

  • You are one or two people and every hour counts.
  • Traffic is low or unpredictable, so you would pay for an idle server.
  • You rely on preview deployments for every pull request.
  • Nobody can respond to a 2 a.m. outage or patch a server.
  • You are a content or marketing site with no heavy media.

A VPS gives you control and also gives you the pager. Be honest about who holds it.

A production-ready VPS setup

A safe baseline looks like this:

  1. Build: set output: "standalone" and build a small Docker image.
  2. Run: start the container with a restart policy, behind a reverse proxy.
  3. TLS: terminate HTTPS at the proxy with automatic certificate renewal.
  4. CDN: put a CDN in front for static files and images, which cuts bandwidth and CPU.
  5. CI/CD: build and push the image from your git host, then deploy on merge.
  6. Backups: back up the database and uploaded files off the server, and test a restore.
  7. Monitoring: watch uptime, memory, disk and error logs, with alerts you will see.
  8. Rollbacks: keep the previous image tagged so you can revert in minutes.
  9. Security: patch the OS, close unused ports, use SSH keys and a firewall.

For a deeper walkthrough of the commands, the Server Compass guide covers the steps in detail.

Regional latency and data location

If your users are in Saudi Arabia or the GCC, server location matters. A server far from your audience adds delay to every uncached request, and a CDN only hides part of it. Choose a region close to your users where you can.

Data location is a separate question. Some businesses must keep customer data in a given country. A VPS or your own cloud account lets you pick the region. Check the exact rules that apply to you before you choose, and ask your provider where data is stored.

Migrating from Vercel without downtime

Move in this order, and keep Vercel live until the last step:

  1. Build and run the Docker image locally, and fix any platform-specific code.
  2. Set up the VPS, proxy, TLS and CDN, then deploy a copy on a test domain.
  3. Copy environment variables and move any data or cron jobs.
  4. Test forms, auth, images, redirects and streamed pages.
  5. Lower your DNS TTL a day ahead.
  6. Switch DNS, watch logs and keep Vercel running for a few days as a fallback.

If search traffic matters, keep URLs identical so rankings do not move.

Choosing by scenario

Scenario Likely fit
Solo founder, new product Stay on Vercel
Small team, bill under about $100 Stay, review quarterly
Bill above about $100, steady traffic VPS behind a CDN
Full-stack app with database and queues Container platform or VPS
Long-running jobs, AI or imports VPS or container platform
Strict data location rules VPS or your own cloud
No one to run servers Managed platform

Free and cheap tiers exist on many platforms, as lists from Bootstrap Build and HyScaler show. Check commercial-use terms before you rely on one.

Getting this right

The hosting decision should follow your app, team and traffic, not the other way round. Build portable, measure your real bill, and move only when the numbers and your capacity agree.

If you want a Next.js site or app built to run anywhere, we can scope it with you. See our Next.js and React services or Get a free quote.

Saqib Zahoor, founder and lead full stack developer, 6+ years building sites and web apps for clients worldwide.

Frequently asked questions

Can you deploy Next.js without Vercel?

Yes. The Next.js docs support a Node.js server, a Docker container or a static export. A single next start process handles all features, including Server Components, ISR and Server Actions.

Is it cheaper to self-host Next.js than to use Vercel?

Sometimes. A small VPS costs less than a few Pro seats plus overages, but you add 2 to 4 hours a month of maintenance. For solo founders and two-person teams, Vercel is often cheaper overall.

What happens if I exceed my Vercel bandwidth limit?

You pay overage charges. Sources quote different rates, such as $40 per 100 GB or $0.15 per GB after 1 TB on Pro, so check Vercel's pricing page for the current figure.

Does Next.js streaming work behind nginx?

It can, if the reverse proxy passes streamed responses through without buffering them. Test streamed pages after setup, because default proxy settings may hold the response back.

Need this done rather than read about it? See our Next.js and React development service, or tell us about your project.

Saqib Zahoor
Written bySaqib ZahoorFull Stack Web Developer

Saqib founded WeboTech Studio and has spent 6+ years building websites, web apps and AI tools for clients worldwide. 230+ projects delivered. He writes about web, SEO and AI from real client work.

View profile
All articlesMore in Next.js
Keep reading

More from the journal.

Next article →n8n Pricing: Cloud vs Self-Hosted and What a Business Pays
Start a project

Have a project in mind?Let's talk.

Tell us what you want to build. You'll get honest advice, a clear timeline and a fixed-scope quote. No pressure, no jargon.

Chat on WhatsAppReplies within a few hours
Chat with usReplies within a few hours