Next.js hosting the whole app, server included.
Push to GitHub. We read package.json, install with your package manager, run next build and start your app with next start, so server rendering, API routes and middleware all work. Previews of each pull request too.
- Node.js22 and 24
- Runsnext start, your server
- Installs withnpm, pnpm, Yarn
- Priced byWhat it uses
We read your code, so you don't write a build script.
Every build shows what we found and each command we ran, line by line. Anything we found, you can change in the app's settings.
| File | What we do with it |
|---|---|
package.json | Next.js from its next dependency, your build script, and your start script when it has one. |
pnpm-lock.yaml | pnpm. A yarn.lock means Yarn, and a package-lock.json means npm ci. Dev dependencies are installed too, because the build needs them. |
.nvmrc | The Node.js version you use. Without it, the engines field of package.json, or the newest we offer. |
tanzahost.json | Optional: the version, system packages, and the install, build and start commands. |
Everything Next.js does, on a server of its own.
Your app runs as a Node.js server, not as files: what works with next start on your laptop works here. NODE_ENV is production.
Server rendering and API routes
Pages rendered on each visit, route handlers, server actions and middleware, all in your app's own sandbox.
Variables at build time too
Variables are encrypted and given to the build as well as the app, so NEXT_PUBLIC_ ones are built into your pages.
Your own server too
With a start script, like one that runs your own server.js, we run it instead of next start.
Previews and deploys without downtime.
The new version starts beside the old one. Visitors switch only once it answers its health address.
A preview for each pull request
With GitHub connected, each pull request gets its own address to try, gone when it closes.
If it fails, nothing changes
A failed build stops the deploy, and the version before it keeps serving your visitors.
Roll back in one click
The version before, deployed again without downtime.
A database next door.
Add what a real app needs beside its web process, each with the app's code and variables.
- PostgreSQL with connection pooling for Prisma or Drizzle, MySQL or Valkey in the same project: attaching one adds DATABASE_URL or REDIS_URL.
- Run prisma migrate deploy as the “before going live” command: once per deploy, before the switch.
- Up to 5 workers and 10 scheduled tasks beside your app, with its code and variables.
Node.js 22 and 24.
We use the newest version that meets what your code asks for, or the one you pick in the app's settings. The next build uses it.
- Node.js 24Recommended
- Node.js 22Supported
Node.js 22 gets security fixes until 30 April 2027. A version past its end of life shows a warning and the date it's removed.
A Next.js app, priced in the open.
Say a Next.js shop holds 0.3 GB of memory and uses 3% of a processor, awake all month. You pay for that use, hour by hour, from your wallet. The limits you set cost nothing by themselves.
reading today's prices