Chajio Cloud
App Hosting

Next.js Hosting

Your app runs exactly as next start runs it, so server rendering, API routes, middleware and the App Router all work. Push to GitHub and it goes live on two replicas, next to a managed database.

$ git push origin main
▸ Detected Next.js: package.json, next.config.js
▸ Using Node.js 22, from package.json
▸ npm ci
▸ npm run build
▸ Starting the web process: next start
✓ Live on 2 replicas: https://my-app.live.chajio.cloud

How it works

How we build and run your Next.js app

  1. Install

    Your dependencies install from your lockfile, on the Node.js version engines in package.json names. Recent Next.js releases need a recent Node.js, so set one.

  2. Build

    npm run build runs next build, with your NEXT_PUBLIC_ variables baked into the browser code.

  3. Run

    npm run start runs next start, which listens on the port the platform hands it, so there is nothing to configure.

  4. Roll out

    The new version takes visitors once its health check passes; the old one finishes its requests and stops. No downtime between deploys.

Get ready

Getting your Next.js app ready

package.json
{
  "engines": { "node": "22.x" },
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start"
  }
}

What create-next-app gives you, plus a Node.js version. Using Prisma? Make start prisma migrate deploy && next start; Prisma takes a lock, so two copies starting together is safe.

app/api/health/route.ts
export function GET() {
  return Response.json({ ok: true });
}

If your home page redirects to a login or renders slowly, point the health check at /api/health instead of /.

Works with

What you can run

App Router

Server components and server actions.

Pages Router

getServerSideProps and API routes.

Middleware

Runs on every request, as with next start.

ISR

Each copy keeps its own cache of regenerated pages.

Auth.js

Set AUTH_TRUST_HOST=true behind the platform’s HTTPS.

Prisma

Run migrations as the app starts.

In production

Running your Next.js app in production

Two kinds of variables

Server variables such as DATABASE_URL stay on the server. NEXT_PUBLIC_ variables are baked into the browser code at build time: public values only, and a new value needs a redeploy.

Signing in with Auth.js

Set AUTH_SECRET, AUTH_URL (your https address) and AUTH_TRUST_HOST=true, or sign-in fails with an “untrusted host” error.

Files that last

Don’t write uploads into public/ while the app runs: each deploy starts from a fresh copy. Keep them in object storage and sessions in your database or signed cookies.

Your own image, if you want one

You don’t need a Dockerfile, but with output: "standalone" Next.js builds a small one. Declare an ARG for each NEXT_PUBLIC_ variable.

Every plan

Included on every plan

2 replicas of every app

Two copies behind a load balancer, so a restart or a failed machine never takes you offline.

A managed database

PostgreSQL, MariaDB or MongoDB, with its own standby replica on another machine.

Deploy on every push

Connect GitHub once; every push to your branch builds and goes live.

One-click rollbacks

Go back to any earlier successful deployment from the Deployments tab.

Free SSL, your domain

Certificates issued and renewed for you, plus a free .live.chajio.cloud address.

Build and runtime logs

Watch builds as they run, and see what your app prints as it serves visitors.

CPU, memory and network

Metrics for every app, from the last 15 minutes to the last 30 days.

Zero-downtime deploys

A new version takes visitors only once its health check passes.

Pricing

Next.js hosting plans

Free Plan

5GB DB Storage · 2GB RAM

Free 1st month

Then $3.50/mo

  • 2 vCPU
  • 2 Apps
  • 1 Database
  • 2 App Replicas (HA)
  • 2 Database Replicas (HA)
  • PostgreSQL, MariaDB or MongoDB
  • Deploy from GitHub
  • Auto-deploy on push
  • One-click rollbacks
  • Deployment history
  • Build & runtime logs
  • CPU, RAM, disk & network metrics
  • Disk usage tracking
  • Environment variables
  • Custom domain
  • Free SSL
Start Free

Growth Plan

10GB DB Storage · 2GB RAM

$8.99/mo
  • 3 vCPU
  • 4 Apps
  • 2 Databases
  • 2 App Replicas (HA)
  • 2 Database Replicas (HA)
  • PostgreSQL, MariaDB or MongoDB
  • Deploy from GitHub
  • Auto-deploy on push
  • One-click rollbacks
  • Deployment history
  • Build & runtime logs
  • CPU, RAM, disk & network metrics
  • Disk usage tracking
  • Environment variables
  • Custom domain
  • Free SSL
Choose Growth
Most Popular

Business Plan

20GB DB Storage · 4GB RAM

$18.99/mo
  • 4 vCPU
  • 6 Apps
  • 3 Databases
  • 2 App Replicas (HA)
  • 2 Database Replicas (HA)
  • PostgreSQL, MariaDB or MongoDB
  • Deploy from GitHub
  • Auto-deploy on push
  • One-click rollbacks
  • Deployment history
  • Build & runtime logs
  • CPU, RAM, disk & network metrics
  • Disk usage tracking
  • Environment variables
  • Custom domain
  • Free SSL
Choose Business

Pro Plan

30GB DB Storage · 8GB RAM

$37.98/mo
  • 8 vCPU
  • 10 Apps
  • 5 Databases
  • 2 App Replicas (HA)
  • 2 Database Replicas (HA)
  • PostgreSQL, MariaDB or MongoDB
  • Deploy from GitHub
  • Auto-deploy on push
  • One-click rollbacks
  • Deployment history
  • Build & runtime logs
  • CPU, RAM, disk & network metrics
  • Disk usage tracking
  • Environment variables
  • Custom domain
  • Free SSL
Go Pro

FAQ

Next.js hosting questions

Yes. Your app runs with next start, the same server you run on your computer, so everything Next.js does there works here: the App Router, the Pages Router, server actions, API routes and middleware.

For apps that run with next start, yes: deploys from GitHub, HTTPS, your own domain and a managed database next to your app. Features that only exist on Vercel’s own platform aren’t part of it.

The one you develop on, set in the engines field of package.json, for example "node": "22.x". Without it, your app builds on the current long-term-support release of Node.js. An .nvmrc file is not read.

Yes. If your next.config sets output: export, your app is static files in the out folder. The Next.js deploy guide shows how to serve them.

No. Next.js is recognised and built without one. A Dockerfile is optional, for when you want control over the image; standalone output keeps it small.

You can start on the Free plan: free for your first month, then $3.50 a month, with 2 vCPU, 2GB RAM, 2 apps and a managed database. The Growth, Business and Pro plans add more CPU, memory, apps and databases as you grow.

Plans are priced and billed in US dollars, and you pay by card at checkout.

Deploy your Next.js app today

Your first month is on us, with a managed database and two replicas from day one.