Deploy Next.js on your own server.
Run your Next.js app as a long-lived Node server on a machine you choose, with previews for every pull request and no per-function billing.
- Build
- Railpack (auto)
- Start
- npm run start
- Port
- $PORT, set by Beep
- Pre-deploy
- npx prisma migrate deploy
- Health check
- /api/health
Step by step.
Connect a server
Use Beep Cloud, a server in your own cloud account, or any Ubuntu or Debian VPS. Beep installs its runtime and agent and locks the server down: inbound traffic is denied, and app ports are reachable only from Beep’s edge.
Create a service from your repository
Pick the GitHub or GitLab repository and the branch to track. In a monorepo, set the root directory for this service; watch paths limit rebuilds to changes that touch it.
Let Beep build it
Railpack detects Next.js from package.json, installs dependencies with your lockfile’s package manager and runs your build script. You can override the install, build or start command on the service.
Start command npm run startListen on $PORT
Beep sets PORT for every service unless you set it yourself, and routes traffic from its edge to that port. Bind to 0.0.0.0 so the edge can reach the container.
package.json "scripts": { "build": "next build", "start": "next start" } // next start listens on $PORT, which Beep sets for youAdd a database
Add managed Postgres (16 to 18, with pgvector and PostGIS), Redis or Valkey to the project, then reference its connection string from your service. References resolve at deploy time.
Environment variables DATABASE_URL=${{ postgres.DATABASE_URL }}Run migrations before each release
Set a pre-deploy command. It runs before each release, so the schema is ready before the new version takes traffic.
Pre-deploy command npx prisma migrate deploySet a health check and deploy
Set the health check path to /api/health. Every push to the tracked branch builds and releases; traffic moves to the new version only once it passes, and rolling back re-releases an earlier image without a rebuild.
Add your domain
Every service starts with a URL on edge.usebeep.sh. When it works, point a CNAME for your domain at Beep; the certificate is issued and renewed for you. Each GitHub pull request also gets its own preview environment, removed when it closes.
Next.js tips.
A site built with output: "export" can run as a static service instead: set the output directory to out and Beep serves it from its edge.
Server actions, API routes and middleware run as a normal Node server, with no serverless limits.
Keep build-time variables (NEXT_PUBLIC_*) set before the build, since Next.js inlines them.
Next.js on Beep, answered.
Straight answers. Anything missing, ask us directly.
Do I need a Dockerfile to deploy Next.js?
No. Railpack detects Next.js from package.json, installs dependencies with your lockfile’s package manager and runs your build script. If your project already has a Dockerfile, you can build with that instead.
Where does the Next.js app run?
On the server you connected: Beep Cloud, your own cloud account or any Ubuntu or Debian VPS. Beep bills per server, so databases, workers and previews on the same server add nothing to the plan.
Can I SSH into the server?
No, and that’s deliberate: Beep manages each host end to end so manual changes can’t drift from its setup. To debug, open a shell inside any container from the dashboard, next to its logs and metrics.
Where to run it.
Other guides.
Own your infrastructure again.
Plans from $1 a month, billed per server, never per service.
Early access · We’ll set up your workspace
Or talk to us →