# Next.js hosting without Vercel: the options compared

> Next.js runs on any host that runs Node: next build, then next start, and every feature works, Server Actions and image optimization included. On Livops a repository with next in package.json runs as a server from a push for 39 credits a month (39,000 so'm), and a static export is free. Here is how Vercel, Render, Railway, Fly.io and a VPS compare.

Source: https://livops.dev/en/hosting/nextjs-hosting

By Livops team, the people who build and run Livops. Updated 20 November 2026.

Vercel makes Next.js, and it is the easiest place to run it — but not the only one. Next.js documents a plain Node.js server and a Docker container as supporting every feature, and a static export as supporting the ones that need no server[1]. This page covers what a self-hosted Next.js app needs, compares Vercel, Render, Railway, Fly.io and a VPS with each provider's own numbers, and ends with exactly what Livops builds and starts.

## What does a Next.js app need in production?

### A Node.js server, or no server at all

`next build` then `next start` is the whole deployment, and that server supports all Next.js features[1]. `next/image` optimization and Proxy work with `next start` with no configuration[2]. A static export (`output: 'export'`) is a folder of HTML, CSS and JavaScript any web server can serve, but it does not support features that need a server[1], Proxy among them[2].

### Environment variables at the right time

Variables are server-only by default. A `NEXT_PUBLIC_` variable is inlined into the JavaScript at `next build`[2]: changing it later means building again, and anything put there is public.

### The same Server Functions key across builds and instances

Next.js encrypts the variables Server Functions close over, with a key it makes anew for every build; instances that do not share the key fail with "Failed to find Server Action"[2]. Set `NEXT_SERVER_ACTIONS_ENCRYPTION_KEY`, a base64 AES key, to keep it fixed[2].

### A small runtime, and a clean shutdown

`output: 'standalone'` writes `.next/standalone` with only the files the server needs and a minimal `server.js`, which reads `PORT` and `HOSTNAME`; it leaves `public` and `.next/static` to be copied in[3]. On `SIGTERM` the server finishes requests in flight and pending `after()` callbacks, and Next.js recommends a drain period of 10 to 30 seconds[2].

### Memory for the build

`next build` is the heaviest thing most Next.js projects do — often heavier than serving them. Size the build machine for it, not only the running app.

## The options at a glance

| Option | What it is | Smallest paid plan for a server-rendered app | What you still maintain |
| --- | --- | --- | --- |
| Livops | A platform; servers in Uzbekistan | 39 credits (39,000 so'm) a month; a static export is free | Your code |
| Vercel | The Next.js company's platform: functions and a CDN | Pro: $20 a month per developer seat, with $20 of included credit[4][5] | Your code |
| A VPS in Uzbekistan | A virtual machine with root | 82,000 so'm a month: 1 vCPU, 2 GB, 30 GB HDD (SmartCloud)[7] | Node, a process manager, a reverse proxy, HTTPS, deploys |
| Railway | A platform billed by usage | Hobby plan: $5 a month, including the same amount of usage; then about $10 per GB of RAM and $20 per vCPU a month[8] | Your code |
| Render | A platform | $7 a month: 0.5 CPU, 512 MB[9] | Your code |
| Fly.io | Virtual machines billed by the second | $3.69 a month for shared-cpu-1x with 512 MB; $2.19 with 256 MB[11] | Your code |

Other providers' prices are from each provider's own page, read on 20 November 2026; the dates are in Sources below. Livops prices are the ones the cabinet bills today.

## Each option

### Livops

A Next.js repository is built and run as a server without configuration; one with `output: 'export'` is published as a free static site (details below). Every `git push` ships a new version, and pull requests can get preview environments. Payment is in so'm through Payme or Click, with no card, and the servers are in Uzbekistan — close to users there, farther from users elsewhere. There is no global CDN of edge locations in front of it, and no root.

### Vercel

Where Vercel is better: it is a verified Next.js adapter, run against Next's full test suite[1]. Hobby is free; Pro is $20 a month per developer seat and includes $20 of usage credit[4][5]. On Hobby, a function runs for at most 300 seconds, a team gets 100 deployments a day[5], and cron jobs run once a day at most, at any minute within the hour you chose[6]. Data transfer beyond what a plan includes is billed on Pro, from $0.15 per GB after the first 1 TB[4].

### A VPS

The most control for the money: 82,000 so'm a month for 2 GB at SmartCloud[7]. Next's own advice when self-hosting is a reverse proxy such as nginx in front of `next start`[2], so the setup is Node, the app under a process manager, nginx with a certificate, and a deploy script — and the build runs on the same 2 GB the site is serving from.

### Railway

The Hobby plan is $5 a month including that much usage; then memory is about $10 per GB and CPU about $20 per vCPU a month[8]. It is paid by credit card[8].

### Render

$7 a month for 0.5 CPU and 512 MB[9], a fixed price. Render takes credit and debit cards[9].

### Fly.io

$3.69 a month for 512 MB and $2.19 for 256 MB, billed by the second while the machine runs[11] — the lowest dollar price here, though 256 MB is tight for `next start`. A card is needed once the trial ends[11].

## Vercel or a server: what changes?

On Vercel, Next.js runs as functions across Vercel's network, and the limits are a function's: its duration, its invocations, its data transfer. On a server — Livops, Render, Railway, Fly.io or a VPS — it is one long-running `next start`, and the limit is that machine's memory. A long request, a websocket next to the app, or a background job is ordinary on a server; traffic from every continent at once is what a global network is for.

## Where can you host Next.js for free?

- **Livops** publishes a static export for free. A server-rendered app has no free tier; on an account that has not paid yet, the first bot or app runs for 15 minutes on a zero balance, once.
- **Vercel** Hobby is free, with 100 GB of fast data transfer and 4 hours of Active CPU a month[5], and the limits above.
- **Render** gives free instances to web services; a free one spins down after 15 minutes without inbound traffic and takes about a minute to start again, within 750 free instance hours a month per workspace[10]. Static sites are free too[10].
- **Railway** has a Free plan with $1 of usage a month and up to 0.5 GB per service, whose services sleep after 5 to 10 minutes without outbound traffic; a trial gives $5 of credit for 30 days, with no card[8].
- **Fly.io** has no free tier for new organizations; a trial gives $1 of credit for 7 days[11].

## Next.js on Livops

1. Push the repository. In the cabinet, click **New project** and choose it, upload the folder as a `.zip`, or start from the **Next.js (static)** template.
2. Put your variables under **Variables**. `NEXT_PUBLIC_` ones are read at build time, so change them and deploy again.
3. Deploy. The log shows the install, `next build` and the start.

Livops makes it a Next.js project when `next` is in `package.json`; like `next build`, it needs an `app`, `pages` or `src` folder. The commands, with pnpm, Yarn or Bun instead when `packageManager` in `package.json` names one:

```sh
npm install
npm run build
npm run start
```

`.nvmrc` or `.node-version` picks the Node version. What Livops adds:

- **A server by default.** Unless `next.config` says `output: 'export'`, the project runs as a web app. With the export, the `out` folder (or your `distDir`) is published as a static site, for free.
- **The standalone output.** Livops asks Next for it at build time; when `.next/standalone/server.js` is there, only that tree is shipped, with `.next/static` and `public` copied in, and started with `node server.js`. A project that sets `output` itself keeps its own choice.
- **`NEXT_SERVER_ACTIONS_ENCRYPTION_KEY`** is set for each project, the same at build time and run time and on every build, unless you set your own.
- **The build cache.** `.next/cache` is kept from one build to the next.
- **Build memory.** `NODE_OPTIONS=--max-old-space-size` is set to three quarters of the build container's memory unless you set `NODE_OPTIONS`; the first line of the build log states that ceiling.
- **`PORT` and `HOSTNAME=0.0.0.0`** are set, and the proxy sends `X-Forwarded-Host`, `X-Forwarded-Proto: https` and `X-Forwarded-Port: 443`, so the addresses Next builds point at your domain.
- **If the new version does not answer** within a minute, the deploy fails and the version that worked keeps serving; if the build fails, the running version is left alone. Recent versions stay in **Deploys** for a one-click rollback.
- **Memory for `next start`** is the service's tier: 256, 512, 1024 or 2048 MiB, set with `memory` in `livops.json` when the project is created and in the settings afterwards.

To set it yourself, put `livops.json` in the repository root:

```json
{
  "kind": "web",
  "memory": 1024
}
```

A server-rendered Next.js app is **39 credits a month (39,000 so'm)**; a static export is free. One credit is 1,000 so'm, and bought credits never expire. See [Pricing](https://livops.dev/en/docs/pricing) for plans, which give more credits than they cost, and [Frameworks](https://livops.dev/en/docs/frameworks) for everything `livops.json` accepts.

## Questions

**Does Next.js work fully outside Vercel?**

Yes. Next.js's own documentation says a Node.js server and a Docker container both support all features. Only a static export loses the features that need a server.

**What does Livops run for a Next.js app?**

npm install, npm run build and npm run start, that is next start. When the build writes Next's standalone output, Livops ships only that, with .next/static and public copied in, and starts it with node server.js.

**Is a static Next.js site free on Livops?**

Yes. With output: 'export' in next.config, Livops publishes the out folder as a static site, and static sites are free. There is also a ready Next.js (static) template.

**Do Server Actions survive a redeploy?**

Livops sets NEXT_SERVER_ACTIONS_ENCRYPTION_KEY for each project, the same at build time and at run time and the same on every build, unless you set your own. Next.js otherwise makes a new key for every build.

**My build runs out of memory. What now?**

Livops already sets NODE_OPTIONS for the build to three quarters of the build container's memory. If it still runs out, the log ends with a tip: set NODE_OPTIONS yourself below the stated ceiling, or turn off production source maps.

**How much does Next.js hosting cost on Livops?**

A server-rendered app is 39 credits a month, which is 39,000 so'm at 1,000 so'm a credit. A static export is free. There is no free tier for apps; on an account that has not paid yet, the first app runs for 15 minutes on a zero balance, once.

**Who wrote this comparison?**

The Livops team. Every price and limit of another provider on this page links to that provider's own page, with the day we read it.

## Sources

1. [Next.js — Deploying](https://nextjs.org/docs/app/getting-started/deploying). Checked 20 November 2026.
2. [Next.js — How to self-host your Next.js application](https://nextjs.org/docs/app/guides/self-hosting). Checked 20 November 2026.
3. [Next.js — output (standalone)](https://nextjs.org/docs/app/api-reference/config/next-config-js/output). Checked 20 November 2026.
4. [Vercel — Pricing](https://vercel.com/pricing). Checked 20 November 2026.
5. [Vercel — Hobby plan](https://vercel.com/docs/plans/hobby). Checked 20 November 2026.
6. [Vercel — Usage and pricing for cron jobs](https://vercel.com/docs/schedules/cron-jobs/usage-and-pricing). Checked 20 November 2026.
7. [SmartCloud — VDS plans](https://smartcloud.uz/cloud-services/vds/). Checked 20 November 2026.
8. [Railway — Pricing](https://railway.com/pricing). Checked 20 November 2026.
9. [Render — Pricing](https://render.com/pricing). Checked 20 November 2026.
10. [Render — Deploy for free](https://render.com/docs/free). Checked 20 November 2026.
11. [Fly.io — Pricing](https://docs.fly.io/about/pricing). Checked 20 November 2026.
