Where to Host a React or Next.js App

Updated September 2026 · Written and maintained by the Progression Agency strategy team

React and Next.js applications can be hosted as static files, as serverless functions, in containers or on a plain server, and the right choice depends on rendering strategy, traffic, budget and who operates it. This guide compares the main web app hosting options for React and Next.js, explains what each rendering mode needs, and gives recommendations by project type.

On this page · 6 sections

What a React or Next.js app needs from hosting
The hosting options
Cost: what drives the bill
Performance
Recommendations by project
How Progression Agency hosts React and Next.js

The short answerA plain React single-page app (Vite) is static files: host it on Cloudflare Pages, Netlify, Vercel or S3 with CloudFront for almost nothing. A Next.js app with server rendering needs a runtime: Vercel is the zero-configuration choice, Netlify and Cloudflare work through adapters, and AWS (Amplify, containers on ECS or App Runner) or a VPS gives control and lower cost at high traffic in exchange for setup and operations. Put Cloudflare in front of whatever you choose for DNS, caching and protection.

Comparisons are based on each project’s official documentation as linked in the text. Progression Agency builds with all of the technologies compared and has no affiliate relationship with any of them.

What a React or Next.js app needs from hosting

It depends on how the app renders. Client-side React produces static HTML, JavaScript and CSS that any CDN can serve. Next.js with server-side rendering, Incremental Static Regeneration, Server Components or API routes needs Node.js (or a serverless equivalent) to run per request, plus a place to cache rendered pages and optimized images. A static export of Next.js behaves like plain React. See SSR vs CSR and Next.js vs React.

Hosting requirements by rendering mode
Rendering mode	Needs	Cheapest fit
Client-side React (Vite)	Static file hosting + CDN	Cloudflare Pages, Netlify, S3 + CloudFront
Next.js static export	Static file hosting + CDN	Cloudflare Pages, Netlify, Vercel
Next.js SSR / ISR / Server Components	Node.js runtime or serverless functions, cache	Vercel, Netlify, Cloudflare (OpenNext), containers
Next.js with API routes and auth	Runtime plus a database	Vercel + managed Postgres, or AWS
Heavy SSR at high traffic	Containers or VMs with autoscaling	AWS ECS/App Runner, Google Cloud Run, VPS cluster

Fit by situation (1-5, editorial) — Platforms win without operations staff; containers win at high steady traffic.

The hosting options

Vercel

Built by the Next.js team; every Next.js feature works on deploy, with previews per pull request, image optimization, edge middleware and analytics. Costs are per seat plus usage (bandwidth, function execution, image optimization). Best for Next.js products and teams without DevOps. Next.js on Vercel.

Netlify

Framework-agnostic platform with a Next.js runtime, forms, identity and a strong static-site heritage. Good for Astro, static React and mixed sites, and for Next.js apps that do not depend on the newest features. Next.js on Netlify.

Cloudflare Pages and Workers

Free static bandwidth, a huge edge network and Workers for server logic; Next.js runs via the OpenNext adapter, and React Router, Astro and SvelteKit have first-party adapters. Best for static React sites, media-heavy sites and cost-sensitive apps. Frameworks on Cloudflare.

AWS

Amplify Hosting offers a Git-based workflow for Next.js and static sites; App Runner and ECS run Next.js in containers with autoscaling; S3 with CloudFront serves static React. Most control and the best fit for companies already on AWS with an operations team. AWS Amplify Hosting.

Azure and Google Cloud

Azure Static Web Apps and App Service, Google Cloud Run: sound choices when the organization already runs on the platform. See AWS vs Azure vs Google Cloud.

VPS or dedicated server

A Node.js process behind Nginx or Caddy on DigitalOcean, Hetzner, Linode or a dedicated box, often with Docker and a process manager. Cheapest at scale and fully under your control; you own updates, scaling and uptime. Tools such as Coolify and Dokku give a platform-like workflow on your own server.

React and Next.js hosting options compared
Option	Next.js support	Setup effort	Cost model	Operations	Best for
Vercel	Native	Minimal	Seats + usage	None	Next.js products
Netlify	Runtime adapter	Minimal	Seats + usage	None	Static, Astro, mixed sites
Cloudflare Pages/Workers	OpenNext adapter	Low	Free static; Workers usage	None	Static and cost-sensitive sites
AWS Amplify	Supported	Low-medium	Usage	Little	AWS shops
AWS containers (App Runner, ECS)	Full (Node)	Medium-high	Usage	Some	High traffic, control
VPS / dedicated	Full (Node)	Medium	Fixed monthly	You	Cost at scale, full control

Cost: what drives the bill

For static React, bandwidth is the only cost and Cloudflare makes it free. For Next.js SSR, the bill is function execution time, bandwidth and image optimization on platforms, or instance hours on containers and VPS. Caching (ISR, CDN rules) is the biggest lever: a page rendered once and cached for a minute costs a fraction of one rendered per request. Platforms are cheapest until roughly the point where a small team could justify operating containers; then AWS or a VPS cluster usually wins on raw cost.

Performance

All the platforms serve static assets from global CDNs. For server-rendered pages, latency depends on where the function runs relative to the database: keep the runtime and the database in the same region, cache aggressively, and use edge rendering only for pages that do not need the database. Measure with Core Web Vitals after launch. See speed optimization.

Static — Static React. Any CDN, nearly free..

SSR — Server rendering. Needs a runtime..

CF — Cloudflare. Free bandwidth, Workers..

Cache — Cache first. ISR and CDN cut cost..

Recommendations by project

Where to host: by project type
Project	Host	Why
Marketing site in Next.js (static)	Cloudflare Pages or Vercel	Free or cheap, fast
SaaS product in Next.js	Vercel + managed Postgres (Neon, Supabase, RDS)	Zero-ops, previews, scaling
Internal React tool behind login	Cloudflare Pages or S3 + CloudFront, API elsewhere	Static, cheap, private
Ecommerce storefront in Next.js	Vercel or Cloudflare with ISR	Cached product pages, fast checkout
High-traffic content site with SSR	AWS containers or VPS cluster behind Cloudflare	Cost control at scale
Enterprise app on AWS	Amplify or ECS	Compliance and account structure

How Progression Agency hosts React and Next.js

We deploy Next.js products to Vercel by default, static React and Astro to Cloudflare Pages, and containerize for AWS when traffic or compliance requires it, always with Cloudflare in front and hosting in the client’s own accounts. See React development, Next.js development and Vercel vs Netlify.

Launching a React or Next.js app?

We will pick the host for your rendering mode and traffic, set it up in your accounts and document the cost.

Get a hosting plan

Getting found in search

AI, AEO and what is changing

Paid media and lead generation

Websites and design

Choosing and working with an agency

Software and app development

Web development, platforms and hosting

Social, content and brand

By industry and by situation

Frequently asked questions

What is the best hosting for a React app?

For a client-side React app, static hosting on Cloudflare Pages, Netlify or Vercel; for Next.js with server rendering, Vercel or a container platform.

Where should I host a Next.js app?

Vercel for the least friction; Netlify or Cloudflare through adapters; AWS, Azure, Google Cloud or a VPS for control and cost at scale.

Can I host React for free?

Yes: Cloudflare Pages, Netlify and Vercel free tiers host static React sites; commercial use needs a paid plan on some.

Does Next.js need a Node.js server?

Only if it uses server rendering, ISR, Server Components or API routes; a static export needs no server.

Is Vercel the only host for Next.js?

No. Netlify, Cloudflare, AWS Amplify, containers and plain Node servers all run it.

Can I host a React app on AWS?

Yes: S3 with CloudFront for static apps, Amplify Hosting or containers for Next.js.

Can I host a Next.js app on Cloudflare?

Yes, through the OpenNext adapter on Workers, or as a static export on Pages.

Which is cheaper, Vercel or AWS?

Vercel at low to moderate traffic with no operations staff; AWS or a VPS at high traffic with a team to run it.

How do I host a React app with a backend?

Host the front end statically and the API on a platform (Vercel functions, Cloudflare Workers, AWS Lambda) or a server; or use Next.js route handlers together.

What is web app hosting?

Hosting that runs application code and serves dynamic responses, as opposed to static file hosting.

Where should the database go?

In a managed service (Neon, Supabase, RDS, PlanetScale) in the same region as the app’s server runtime.

Do I need a CDN for a React app?

Yes; every option here includes or supports one, and Cloudflare can front any of them.

How do I deploy previews for stakeholders?

Vercel, Netlify and Cloudflare create a URL per branch or pull request automatically.

Which does Progression Agency use?

Vercel for Next.js products, Cloudflare Pages for static sites, AWS containers for high traffic or compliance.

Can you migrate my app to better hosting?

Yes; see website migration services and DevOps services.

Need help choosing or moving hosting?We recommend, set up, migrate and manage hosting for the sites and apps we build, and for sites built elsewhere.

Get a hosting recommendation

Get a free marketing proposal

Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.