Host Next.js without Vercel.
run.zero builds your app with next build and runs it with next start as a Node server in Germany. Server rendering and route handlers run in that process.
Needs the Developer plan, the free plan only covers websites. Pricing · Check the limits first
- App Router and SSR tested
- One Node process per replica
- Hosted in Nuremberg
> Deploy the nextjs folder to run.zero.
runzero_create_appdoneexample-nextjs
runzero_push_filesdoneone commit
runzero_deploydoneservices created
runzero_wait_for_builddonelive
live at https://web-example-nextjs-6733689e.run-zero.de
- Live demoRunning on run.zero(opens in a new tab)
- Example codeMIT, on GitHub(opens in a new tab)
- BuildpacksNode, Python, Go, PHP, Java
- Hosted in GermanyHetzner, Nuremberg
Live in four steps.
Tested with Next.js 16 in the example that runs live.
- 01
Adjust the scripts
Pin Node 22 and build with
next build --webpack. Turbopack, the default in Next.js 16, cannot findnextin the buildpack’s module layer.package.json (excerpt) "engines": { "node": "22.x" },"scripts": { "build": "next build --webpack", "start": "next start -p ${PORT:-8080}"} - 02
Keep next in dependencies
next,reactandreact-dombelong independencies. The buildpack prunesdevDependencies. - 03
Add run-zero.yaml
One service, port 8080.
run-zero.yaml version: "1"services: web: port: 8080 - 04
Create an account and deploy
Create an account, connect your agent with this command, then sign in from Claude Code with
/mcpand Authenticate.- Then tell your agent: deploy this repo to run.zero.
Without an agent
Create the app in the dashboard and connect your GitHub repo. Every push rebuilds.
Connect Claude Code claude mcp add --transport http \ -s user run-zero \ https://api.run-zero.de/mcp \ --client-id runzero-cli \ --callback-port 53761
After 1 to 3 minutes the app is live at https://web-<app>.run-zero.de. Check a route of your app, in the example /api/health. If the build is red, runzero_get_build_logs tells you why.
One project, one service.
The scripts in package.json decide everything.
build uses --webpack, start takes the port from $PORT.
{ "name": "run-zero-example-nextjs", "version": "1.0.0", "private": true, "engines": { "node": "22.x" }, "scripts": { "dev": "next dev", "build": "next build --webpack", "start": "next start -p ${PORT:-8080}" }, "dependencies": { "next": "16.4.5", "react": "19.3.1", "react-dom": "19.3.1" }}Rendered on the server for every request, the timestamp shows it.
Example on GitHub(opens in a new tab)// Rendered on the server for every request, so the time shows that SSR runs on run.zero.export const dynamic = 'force-dynamic';export default function Home() { return ( <main> <h1>Next.js on run.zero</h1> <p>Server-rendered at {new Date().toISOString()} by next start.</p> <p><a href="/api/health">/api/health</a></p> </main> );}What changes compared to Vercel.
Only what you notice in operation.
| On Vercel | On run.zero |
|---|---|
| Serverless functions per route | One Node process with next start per replica |
| Build at Vercel | next build at image build time with Paketo |
| Project environment variables | env: in run-zero.yaml, secret values as secrets |
| Vercel domain | https://<service>-<app>.run-zero.de, custom domain with Let’s Encrypt |
| Vercel Postgres, KV, Blob | Postgres addon, no KV or Blob |
What does not work today.
So nothing catches you off guard.
Needs the Developer plan
Free has no server apps and no Postgres, a deploy stops with an error.
See pricingNo Turbopack build
Build with
--webpack, otherwisenext buildfails on the buildpack.No Vercel services
Vercel’s Edge Network, KV, Blob and Analytics are not available here.
ISR not tested
No shared cache across replicas is set up, and we have not checked ISR.
What you stop doing yourself.
Builds, HTTPS, the database and backups run on the platform.
Data stays in Germany
Servers and backups at Hetzner in Nuremberg. With a data processing agreement.
HTTPS by default
Every service gets an address on
run-zero.de, custom domains a Let’s Encrypt certificate.Postgres as an addon
One entry in
run-zero.yaml,DATABASE_URLarrives as an environment variable.No lock-in
Your code stays in your repo, the database is a dump you can download.
Questions.
About Next.js.
Can I use a static export?
We have not tested that with Next.js. The Vite example shows how serve delivers finished files.
Which Next.js version is tested?
Next.js 16 with React 19 in the example. The live demo renders every request on the server.
How do I use a database?
Attach the Postgres addon to the service in run-zero.yaml. Your server components and route handlers read DATABASE_URL.
My project comes from v0. Does this apply?
Yes. A v0 export is a Next.js project, so you follow the same steps.