JavaScript & Node.js

Next.js VPS HostingSelf-Host SSR, ISR and API Routes

Next.js running as a Node.js server supports all of its features: server rendering, ISR, route handlers, middleware and image optimisation. We install Node.js, PM2 and NGINX with HTTPS on a hardened VPS; you build and deploy your app.

Full root & SSH NVMe storage Daily backups Anti-DDoS 99.9% uptime SLA 11 locations

  • Reserved vCores and RAM

    Server rendering without per-invocation billing.

  • Root and SSH access

    Any Node version, sharp and native modules.

  • NVMe storage

    Fast builds and on-disk ISR and image caches.

  • Dedicated IPv4 and IPv6

    Your own addresses, with anti-DDoS included.

Why a VPS

Why Self-Host Next.js on a VPS

Serverless platforms bill for function invocations, bandwidth and image optimisation. A VPS runs the same Next.js server for a flat monthly price.

  1. A flat cost as traffic grows

    No metered function calls or image optimisation charges: the plan price covers the server.

  2. No function time limits

    Long-running route handlers, streaming responses and background work are not cut off by a platform timeout.

  3. Database and cache on the same server

    Run PostgreSQL, MongoDB or Redis next to Next.js and query them over localhost.

  4. Caching you control

    The ISR and image caches live on your disk, and you decide the cache headers and what NGINX caches in front.

The stack

How Self-Hosted Next.js Is Served

NGINX in front, one Next.js Node server behind it, and static assets served straight from disk.

Request from a browser or app (HTTPS)

  1. Reverse proxy

    NGINX

    HTTPS, compression and long cache headers for /_next/static; everything else goes to Next.js.

  2. Process manager

    PM2 or systemd

    Runs next start (or the standalone server.js), restarts on failure and starts on boot.

  3. Application

    Next.js server

    App Router or Pages Router: SSR, ISR, route handlers, middleware and image optimisation.

  4. Runtime

    Node.js LTS

    The Node version your Next.js release requires.

  5. Data

    Your database or CMS

    PostgreSQL, MongoDB, MySQL or a headless CMS, on this VPS or elsewhere.

Worth knowing

  • output: "standalone" produces a minimal server.js with only the files it needs, which keeps deploys small.
  • Image optimisation runs on the server; leave memory headroom on image-heavy pages.
  • Running several instances? Share the ISR cache through a custom cache handler, for example in Redis.
  • A static export (output: "export") needs only NGINX, with no Node process.
What you can run

What You Can Run

  • Marketing sites with ISR

    Pages regenerated in the background as content changes, served at static speed.

  • SaaS front ends

    Logged-in dashboards built with server components and route handlers.

  • Headless storefronts

    Store front ends on Shopify, Medusa or WooCommerce APIs.

  • Headless CMS sites

    Next.js front ends for WordPress, Strapi, Payload or Sanity content.

  • Docs and blogs

    MDX documentation and blogs, statically generated or server-rendered.

  • Full-stack apps

    Next.js with a database on the same VPS, using route handlers or server actions.

VPS Plans

VPS Plans for Next.js

Next.js builds are memory-hungry, so VPS-2 with 8 GB RAM is a comfortable start if you build on the server. VPS-1 suits smaller sites, or apps built in CI.

VPS-1

Small websites, APIs, bots and development servers.

₹1,008 /mo
Get Started
  • 2 vCores
  • 4 GB RAM
  • 40 GB NVMe
  • 500 Mbps
  • Full root and SSH access
  • Free initial stack installation
  • Server hardening and firewall setup
  • Daily backup of the previous 24 hours
  • Unlimited traffic *
  • Anti-DDoS protection
  • Dedicated IPv4 and IPv6
  • KVM virtualisation

VPS-3

Busy stores, SaaS products and several projects.

₹2,748 /mo
Get Started
  • 6 vCores
  • 12 GB RAM
  • 100 GB NVMe
  • 2 Gbps
  • Full root and SSH access
  • Free initial stack installation
  • Server hardening and firewall setup
  • Daily backup of the previous 24 hours
  • Unlimited traffic *
  • Anti-DDoS protection
  • Dedicated IPv4 and IPv6
  • KVM virtualisation

VPS-4

High-traffic apps, large databases and agencies.

₹5,274 /mo
Get Started
  • 8 vCores
  • 24 GB RAM
  • 200 GB NVMe
  • 3 Gbps
  • Full root and SSH access
  • Free initial stack installation
  • Server hardening and firewall setup
  • Daily backup of the previous 24 hours
  • Unlimited traffic *
  • Anti-DDoS protection
  • Dedicated IPv4 and IPv6
  • KVM virtualisation

* Unlimited traffic in Europe and North America. In Mumbai, Singapore and Sydney a monthly allowance applies (VPS-1 500 GB, VPS-2/VPS-3 1 TB, VPS-4 3 TB), then speed is limited to 10 Mbps until the next month.

Sizing guide

Which Plan for Your Next.js App

Running Next.js is light; building it is not. Size for the build if you build on the server.

Recommended VPS plan for each Next.js workload
Workload Start with Why
Marketing site or blog, built in CI VPS-1 2 vCores · 4 GB RAM next start with ISR fits comfortably.
App built on the server VPS-2 4 vCores · 8 GB RAM 8 GB covers a production build while the site keeps running.
SaaS front end with heavy SSR VPS-3 6 vCores · 12 GB RAM More vCores for server rendering under load.
Several Next.js sites VPS-4 8 vCores · 24 GB RAM Room for multiple processes and builds.

A starting point, not a limit: every plan upgrades in place, keeping your data, IP address and configuration.

Next.js on Serverless or Self-Hosted?

Serverless adds an edge network and previews; self-hosting adds a fixed price and no function limits.

Feature Serverless platform Next.js VPS
Pricing Usage-based: invocations, bandwidth, images Flat monthly plan
Function time limits Yes, by plan None
ISR and image cache Platform-managed On your disk
Global edge network Built in Add a CDN if you need one
Preview deployments Built in Your own setup
Server administration Handled by the provider Yours, after our free setup
See Plans
After handover

Your First Next.js Deploy

Build on the server and run next start under PM2 behind NGINX.

  1. Clone and install

    Reproducible installs from your lockfile.

  2. Build

    Creates the production build in .next.

  3. Start under PM2

    Starts on boot and restarts on failure.

  4. Ship updates

    Pull, rebuild and reload.

# 1. Clone and install

git clone [email protected]:you/web.git ~/web && cd ~/web

npm ci

# 2. Build

npm run build

# 3. Start under PM2

pm2 start npm --name web -- start

pm2 save

# 4. Ship updates

git pull && npm ci && npm run build && pm2 reload web

Example shell commands; adjust paths, names and versions to your project.

Example commands; adjust names, paths and versions to your project. Deploying and maintaining your application is yours to do (or ask us for a quote).

Free one-time setup

Installed and Secured Before You Log In

The VPS is unmanaged: after handover the server is yours to run. Before that, our engineers do the first setup once, free, so you start from a hardened server with Next.js in place.

  1. Choose a plan and location

    Pick the resources you need and the datacentre closest to your users.

  2. Tell us your Next.js setup

    Versions, database and domain: at order or right after.

  3. We install and secure it

    Server hardened, Next.js installed and tested, HTTPS on your domain.

  4. You take over with root

    SSH access to a working server, ready for your code and data.

Your Next.js stack

  • Node.js LTS, the version your Next.js release needs
  • PM2 with startup on boot, or a systemd service
  • NGINX reverse proxy with cache headers for /_next/static
  • HTTPS with Let's Encrypt on your domain
  • PostgreSQL or MongoDB if you choose one at order

Yours to run after handover

  • Ongoing server administration
  • Application maintenance and updates
  • Debugging your code
  • Migrating existing sites or data

Not included in the free setup, but we can quote for it. No control panel by default: CloudPanel, HestiaCP or Virtualmin on request at no cost; cPanel and Plesk need their own licence.

Under the hood

Platform Specs and Locations

The same KVM platform on every plan; only the CPU, RAM, storage and port speed change.

VPS platform specifications
Virtualisation KVM with reserved vCores and RAM
Storage NVMe SSD on every plan
Network Dedicated IPv4 and IPv6, 500 Mbps to 3 Gbps per plan
Operating systems Ubuntu 26.04, 24.04 and 22.04 LTS · Debian 13, 12 and 11 · AlmaLinux · Rocky Linux · Fedora · FreeBSD
Access Full root over SSH, key-based login
Backups Automatic daily backup of the previous 24 hours; snapshots and longer retention on request
Protection Always-on anti-DDoS mitigation
Availability 99.9% uptime SLA

Secured before we hand it over

  • Non-root sudo user created for daily work
  • SSH key login, password login for root disabled
  • Firewall (UFW) open only for the ports you use
  • Fail2ban blocking repeated login attempts
  • Automatic security updates enabled
  • Free Let's Encrypt SSL on your domain
  • Timezone, swap and hostname configured

Asia-Pacific

  • Mumbai
  • Singapore
  • Sydney

Europe

  • London
  • Limburg
  • Roubaix
  • Gravelines
  • Strasbourg
  • Milan
  • Warsaw

North America

  • Beauharnois

Availability per location changes with demand; we confirm your location before setup. In Mumbai, Singapore and Sydney each plan includes a monthly traffic allowance (VPS-1 500 GB, VPS-2 and VPS-3 1 TB, VPS-4 3 TB); beyond it, speed is limited to 10 Mbps until the next month.

Who it's for

Who a Next.js VPS Suits

  • Teams leaving usage-based billing

    Sites where serverless bills have become hard to predict.

  • Agencies building Next.js sites

    Several client front ends on one server, each its own process.

  • Developers who want one box

    Next.js, the database and the CMS together, managed over SSH.

Running it well

Security and Performance for Next.js

Security

  • Keep server-only secrets out of NEXT_PUBLIC_ variables, which end up in the browser bundle.
  • Keep Next.js updated: framework releases regularly include security fixes.
  • Bind the Node server to localhost and let only NGINX face the internet.
  • Protect route handlers and server actions with authentication and input validation.

Performance

  • Let NGINX serve /_next/static with immutable cache headers.
  • Use static generation or ISR where you can; SSR on every request costs CPU.
  • Build in CI if server builds compete with live traffic for RAM.
  • Deploy the standalone output to keep releases small and quick to copy.
Next.js VPS FAQs

Questions Before You Deploy

Not covered here? Ask an engineer before you order.

Self-Host Your Next.js App

Choose a plan and tell us your Node version. We hand over NGINX, PM2 and SSL ready for next start.