Next.js Deployment

Next.js Hosting for SSR Apps and Static React Exports

Deploy Next.js the way your app actually renders — a persistent Node runtime for SSR, or fast static hosting for a fully exported build.

NVMe

Storage with LiteSpeed caching

Root SSH

Access for SSR and API routes

$9.99/mo

VPS plans starting price

Free

Auto-renewing SSL on every plan

In short

Next.js hosting depends entirely on how your app renders: a static export (output: 'export') can run on ordinary web hosting since it's just HTML, CSS and JS, while server-side rendering, API routes and middleware need a persistent Node.js runtime with SSH access and a process manager. Hosting Cheap serves static exports fast on NVMe-backed web hosting, and root-access VPS plans from $9.99/mo run the Node server SSR needs.

Either way, environment variables and build secrets stay out of your repository, configured directly on the server or in your CI pipeline.

Next.js quietly asks a different question of your hosting depending on which rendering mode you chose: a static export is just files that any web server can serve, but server-side rendering, API routes, middleware and server components all require Node.js running continuously to handle each request. Deploying an SSR app onto hosting that only serves static files simply doesn't work, no matter how the build output looks locally.

Hosting Cheap covers both paths. A static-exported Next.js site runs fast on NVMe-backed web hosting from $2.09/mo, while an SSR app, API routes or a mix of both get full root SSH access on a VPS from $9.99/mo — enough to run next start, a custom Node server, or a process manager keeping the build alive. Free auto-renewing SSL, daily backups and free managed migration apply to either setup.

SSR versus static export: picking the right Next.js hosting shape

A Next.js app built with output: 'export' produces a folder of static HTML, CSS and JavaScript with no server-side logic left to run, which means it can be served from ordinary NVMe-backed web hosting exactly like any static site. An app using getServerSideProps, API routes, middleware or server components needs Next.js's Node server running continuously, which static file hosting simply can't provide.

Getting this distinction right before choosing a plan avoids the common mistake of deploying an SSR app to static hosting and wondering why API routes return 404s or middleware never runs.

A Node runtime for API routes, middleware and server components

Root SSH access on a VPS plan lets you install the Node.js version your Next.js app targets, run npm install against your package.json, and start the app with next start or a custom server file, keeping API routes and middleware fully functional in production.

A process manager like pm2 keeps that Node server restarting automatically after a crash or server reboot, and a reverse proxy routes standard web traffic on ports 80 and 443 to Next.js's internal port, all configurable directly since you have full root access.

Build pipelines, environment variables and secrets management

A Next.js build needs environment variables split correctly between what's exposed to the browser (prefixed with NEXT_PUBLIC_) and what stays server-side only, like database URLs or API keys — mixing those up leaks secrets into your client bundle. SSH access lets you set environment variables directly on the server, outside your repository, and run next build as part of your own deploy script.

Pure NVMe SSD speeds up that build step meaningfully, since a Next.js build can involve compiling dozens of routes, generating static pages, and bundling JavaScript for every page in your app.

Scaling a growing Next.js app onto a dedicated VPS

A Next.js app that starts as a marketing site with a couple of dynamic routes often grows into a full SSR application with authenticated dashboards, API routes and a connected database, and hosting should scale right along with it. VPS plans starting at $9.99/mo give the root access an SSR app needs, with dedicated servers from $149.99/mo available once traffic or a heavier build process demands more dedicated resources.

Free managed migration moves your existing Next.js project — code, environment configuration and build setup — onto the new plan with no downtime, and 24/7 human support is available if a reverse proxy or Node process needs troubleshooting.

Next.js Hosting: Deploy SSR & Static React Apps

Why Next.js developers choose Hosting Cheap

A Next.js app can be a fully static export or a server-rendered application with API routes and middleware — and the right hosting depends entirely on which one you built.

Hosting Cheap serves static exports fast on NVMe-backed web hosting, and gives SSR apps full root SSH access on VPS plans, so the Node runtime, environment variables and build pipeline all work exactly as your app expects.

NVMe-backed web hosting for fully static Next.js exports
Root-access VPS for SSR, API routes and middleware
Direct control of NEXT_PUBLIC_ and server-only environment variables
Free managed migration for an existing Next.js deployment

Why Hosting Cheap

What you get

Fast static export hosting

NVMe SSD with LiteSpeed caching serves a static-exported Next.js build quickly and affordably.

Full Node runtime for SSR

Root SSH access on VPS plans runs next start, API routes and middleware exactly as built.

Clean environment variable handling

Set server-only secrets and NEXT_PUBLIC_ variables directly on the server, outside your repository.

Faster builds on NVMe

Pure NVMe SSD speeds up compiling routes and bundling JavaScript during next build.

Encrypted by default

Free auto-renewing SSL secures both static pages and dynamic API routes.

Room to scale

Move from a small VPS to a dedicated server from $149.99/mo as SSR traffic grows.

How It Works

Get set up in a few steps

Decide: static export or SSR

Check whether your build uses output: 'export' or relies on SSR, API routes or middleware.

Pick static hosting or a root-access VPS

Serve a static export on NVMe-backed web hosting, or choose a VPS from $9.99/mo for a Node runtime.

Deploy and configure your environment variables

Run your build, set environment variables on the server, and go live behind free SSL.

Included

Everything you need, on every plan

Confirmed whether your app is a static export or SSR
Root SSH access for a Node runtime, if SSR is used
NEXT_PUBLIC_ and server-only variables set correctly
A process manager keeping next start running after a reboot
A reverse proxy routing traffic to Next.js's internal port
Free auto-renewing SSL on every plan
Daily backups protecting code and environment configuration
Root-access VPS plans from $9.99/mo for SSR scaling

FAQ

Frequently asked questions

Can I host a static-exported Next.js site on regular web hosting?

Yes. A build using output: 'export' produces plain HTML, CSS and JavaScript, which runs fine on NVMe-backed web hosting from $2.09/mo with no Node runtime required.

Do I need a VPS for server-side rendering?

Yes, SSR, API routes, middleware and server components all need a persistent Node.js process, which requires root SSH access — available on VPS plans starting at $9.99/mo.

How do I set environment variables for my Next.js app?

SSH access on VPS plans lets you set NEXT_PUBLIC_ and server-only environment variables directly on the server, keeping secrets out of your repository and client bundle.

Is SSL included for API routes?

Yes, free auto-renewing SSL is included on every plan and covers both static pages and any API routes your Next.js app exposes.

Are backups included for my Next.js project?

Yes, daily backups protect your code, build configuration and environment setup on both static and VPS-hosted deployments.

Can I migrate an existing Next.js app to Hosting Cheap?

Yes, free managed migration transfers your existing project, whether it's a static export or a full SSR app, with no downtime.

Deploy your Next.js app the way it actually renders

Static hosting for exports, root-access VPS for SSR — with NVMe speed and free SSL either way.

Get Started