Where to host a Next.js app in 2026: Vercel, self-host, or somewhere in between

Most people asking where to host a Next.js app have already been burned once. Either a Vercel bill jumped from nothing to a few hundred dollars in a month nobody planned for, or a cheap VPS fell over the first time traffic spiked. Both stories are common, and both are avoidable if you match the host to the app instead of picking whatever the tutorial used.

We are Zarle Infotech, a studio in Noida. Next.js is our default for web work, so we have shipped it on Vercel, on bare VPS boxes, on Cloudflare, and behind AWS. This piece is the honest version of that experience: what each option actually costs in 2026, where Vercel earns its price, where it stops making sense, and the point where self-hosting starts to pay. If you only remember one thing, remember that where to host a Next.js app is a cost-and-control decision, not a loyalty decision.

The short answer first

• If you want zero infrastructure work and your traffic is modest, ship on Vercel. It is the fastest path and the bill stays small.
• If bandwidth or requests are climbing and the monthly total is scaring you, move to a VPS with Coolify, or to Cloudflare Pages.
• If you already live in AWS or need heavy background jobs, hosting Next.js inside that stack is reasonable.
• If someone tells you there is one correct answer, they are selling something.

Now the detail, because the gap between these choices is real money.

Vercel: the default, and why it is the default

Vercel is built by the same team that builds Next.js. Every feature, ISR, streaming server components, edge middleware, the App Router, works on day one with no config. You connect a Git repo, push, and you get automatic SSL, preview URLs for every pull request, and a global CDN. For a founder who wants a site live this week, nothing beats it on setup time.

The pricing in 2026 has three tiers. Hobby is free but non-commercial. Pro is $20 per seat per month, which is roughly Rs 1,700. Enterprise starts around $45,000 a year, so it is a different conversation entirely.

The catch is that the seat price is not the bill. Vercel meters usage on top of it. Pro includes 1 TB of bandwidth (they call it Fast Data Transfer), and past that you pay about $0.15 per GB, which works out to $40 per 100 GB. Edge Requests are included up to 10 million, then $2 per million after. Image optimization, function invocations, active CPU, and provisioned memory all meter separately. None of that matters until it does, and then it matters all at once.

This is the shape of the Vercel surprise: your seat cost is flat and predictable, and the metered usage is the part that balloons. Image-heavy sites, video, and middleware-on-every-request apps burn through the included allotments fastest.

When Vercel is genuinely worth it

We keep plenty of client sites on Vercel and do not apologise for it. It is worth the price when:

• The site is content or marketing led and traffic sits comfortably under the included tiers.
• The team is small and nobody wants to babysit a server.
• You lean on Next.js features that are painful to replicate elsewhere, like fine-grained ISR or edge middleware.
• Time to launch matters more than shaving the hosting bill.

For a legal or clinic site doing steady but not enormous traffic, the Vercel bill often stays around the base seat cost. Chauhan & Sanskar Law Offices is the kind of build where paying for zero-ops hosting is simply the right call. The inquiries went up 150 percent after the rebuild, and not once did the hosting bill become a topic. That is Vercel doing exactly what it is good at.

When Vercel gets expensive

The trouble starts when metered usage takes over. If your app pushes past roughly 10 million requests a month, or serves a lot of images and media, the bill climbs faster than most people budget for. A jump from $0 to $300 in a month with no code change is a real thing people report, and it is almost always bandwidth or edge requests, not the seat.

Marcoob is a useful example from our own work. It is a fashion ecommerce build, and fashion means images, lots of them, plus an AR try-on flow. That is exactly the profile that makes metered bandwidth hurt. For a catalogue that heavy, the question of where to host a Next.js app is really a question about egress, because the product images are the traffic. On a metered platform, image-first ecommerce is where the meter runs hottest.

Self-hosting on a VPS: the cost floor

Here is the number that reframes the whole debate. You can run Next.js on a VPS from Hetzner, DigitalOcean, or Contabo for roughly $4 to $6 a month, which is about Rs 350 to Rs 500. A Hetzner CPX21 at around €5.19 a month comfortably runs multiple Next.js apps at once.

Compared with a Vercel Pro team of three or more, self-hosting on a small VPS can cost 10 to 20 times less. That is not a rounding error. That is the difference between a hosting line item you notice and one you do not.

The old objection to self-hosting was operational pain: install Node, set up PM2, configure Nginx as a reverse proxy, get SSL sorted, wire up deploys. That objection has largely aged out. Coolify, which is open source and self-hostable, gives you Vercel-style features on your own box: git-push deploys, preview URLs for pull requests, automatic SSL, monitoring, and one-click databases. You install it on a fresh VPS with a single command, and it handles Docker and the rest in a few minutes.

The one honest cost of self-hosting is responsibility. Nobody else is watching your server at 2 a.m. You own updates, backups, and uptime. That is a real trade, and it is why we do not put every tiny site on a VPS just to save a few hundred rupees.

Where the cost crossover sits

People want a clean number for where to host a Next.js app profitably, so here is our rule of thumb, not a law of physics.

• Under about 1 TB of bandwidth and 10 million requests a month, Vercel or another managed platform usually wins once you price in your own time.
• Above those numbers, especially with media, the metered bill starts to overtake what a capable VPS plus a few hours of setup would cost.
• Once you are paying Vercel more than roughly $100 to $150 a month purely on overages, a VPS with Coolify has almost certainly become cheaper, even after you value your maintenance time honestly.

The crossover is not about how big your company is. It is about your traffic shape. A small startup serving huge video files hits it early. A mid-size firm with a lean content site may never hit it at all.

Netlify, Cloudflare, and the middle ground

Vercel and a raw VPS are the two ends. Most teams also weigh a few managed options in between.

Netlify is the closest peer to Vercel. Pro is about $19 per seat and also includes 1 TB, but overage bandwidth is pricier at roughly $55 per 100 GB. It is solid for static and mostly-static sites. On heavier dynamic Next.js workloads it lags, partly because its functions run on Lambda and cold starts land in the 200 to 500 ms range.

Cloudflare Pages is the one to watch on cost, because bandwidth is effectively unlimited and free on every tier. There is no per-GB egress charge, ever. For a bandwidth-heavy app, that single fact can settle the decision. The trade is that some Next.js features need more care to run on Cloudflare's runtime than they do on Vercel, so it rewards a team that knows what it is doing.

AWS Amplify is the enterprise-leaning choice. It gained full ISR support in late 2025, so it is more capable than it used to be for Next.js. It makes the most sense when you are already inside AWS and want hosting next to your other services rather than as a separate bill.

Comparison table: real numbers for 2026

Prices move, so treat these as the shape of the market rather than a quote. The pattern holds even when the exact figures shift: managed platforms charge for convenience and meter usage, and a VPS trades a bit of your time for a much lower and more predictable bill.

What we actually do at Zarle

We right-size the host to the project instead of defaulting to one answer.

• Content, marketing, and brochure-style sites with modest traffic go on Vercel. The convenience is worth it and the bill stays flat.
• Media-heavy or high-traffic apps get a VPS with Coolify, or Cloudflare when bandwidth is the main worry. Predictable cost beats a scary meter.
• Anything already tangled into AWS stays near AWS.

Optima Learning is a good example of matching host to app. It is an edtech platform with AI-driven CAT prep and an SEO-ready CMS, so it needs dynamic rendering that still ranks. We picked the host around that requirement, not around a habit. That is the whole method: decide where to host a Next.js app after you understand its traffic and feature needs, not before.

A short checklist before you pick

Run through this and the answer usually reveals itself:

1. Estimate monthly bandwidth and request count honestly, including images and video.
2. List the Next.js features you actually rely on, like ISR or edge middleware.
3. Decide who owns the server at 2 a.m. If the answer is "nobody," lean managed.
4. Price the metered overages at your expected traffic, not the base seat.
5. If overages beat a VPS plus setup time, self-host. If not, stay managed.

Getting where to host a Next.js app right is mostly about doing this small amount of homework before you deploy, not after the first bill.

Frequently asked questions

Is Vercel too expensive for a small business?

No, usually the opposite. For a small business site with normal traffic, Vercel often stays near the base seat price of about $20 a month. It gets expensive only when metered bandwidth or requests climb, which is a high-traffic or media-heavy problem, not a small-business one.

Is self-hosting Next.js hard now?

Much less than it used to be. Tools like Coolify on a Hetzner or DigitalOcean VPS give you git-push deploys, preview URLs, and automatic SSL with a one-command install. The remaining work is ownership: you handle updates, backups, and uptime yourself.

What is the cheapest way to host a Next.js app?

A small VPS, roughly $4 to $6 a month, with Coolify handling deploys. Cloudflare Pages is the cheapest managed route because its bandwidth is unlimited and free. Both beat metered platforms once traffic gets heavy.

Does Cloudflare Pages support all Next.js features?

Most of them, but its runtime differs from Vercel's, so certain features need extra configuration to run cleanly. If your app leans hard on advanced Next.js behaviour, test it there before committing, or keep it on Vercel where those features are native.

When should I move off Vercel?

When your metered overages start beating the cost of a VPS plus a few hours of setup, roughly once you are paying more than $100 to $150 a month on usage rather than seats. Media-heavy and high-traffic apps hit that point first.

Can I host Next.js and a database on the same server?

Yes. A single mid-tier VPS can run Next.js and a database together, and Coolify offers one-click databases to make that simple. For larger apps we separate them, but for many projects one box is plenty.

Which host is best for an ecommerce Next.js store?

It depends on image volume. Heavy product catalogues push bandwidth, so Cloudflare Pages or a VPS often works out cheaper than a metered platform. If the store is small and you value fast launch, Vercel is still fine.

Getting it right the first time

Where to host a Next.js app is one of those decisions that is cheap to get right and expensive to get wrong, and the right answer changes as your app grows. Start where the setup cost is lowest, watch your bandwidth and request numbers, and move when the meter tells you to.

If you would rather not guess, our team builds and hosts Next.js apps every week and can size the right setup for your traffic and budget. Take a look at our website development service, or email us at contact@zarleinfotech.com and we will point you at the cheapest option that still fits.

For more on the money side of hosting, see our guides on the best web hosting for small business, the differences between shared, VPS, and cloud hosting, and what web hosting actually costs.