Self-host Next.js + PostgreSQL with Levelrail
The SSR-plus-database pairing behind most Next.js apps, wired with a healthchecked Postgres.
- Memory384 MiB
- Archarm64
- Services2
How to self-host Next.js + PostgreSQL
-
Pull the images
2 images are pulled on your server.
Show images
postgres:16-alpinenode:22-alpine
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on port 3000.
-
Fill in the secrets
2 secrets are generated and stored encrypted, 3 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Next.js + PostgreSQL requirements
- Memory
- About 384 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 3000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- not yet recorded
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 3000 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Next.js + PostgreSQL. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Next.js + PostgreSQL docs page.
Deploy Next.js + PostgreSQL your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Next.js + PostgreSQL from the CLI
levelrail-cli templates deploy nextjs-postgres-starter --name my-nextjs-postgres-starter Deploy Next.js + PostgreSQL with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/nextjs-postgres-starter/deploy Next.js + PostgreSQL configuration
Next.js + PostgreSQL services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | postgres:16-alpine | none | nextjs_postgres_db_data -> /var/lib/postgresql/data |
| web | node:22-alpine | 3000 | none |
Next.js + PostgreSQL environment variables
| Variable | Service | Value |
|---|---|---|
| POSTGRES_DB | db | Preset by the template |
| POSTGRES_PASSWORD | db | Generated at deploy |
| POSTGRES_USER | db | Preset by the template |
| DATABASE_URL | web | Generated at deploy |
| NEXT_TELEMETRY_DISABLED | web | Preset by the template |
Ports and volumes
- Ports
- 3000
- Volumes
- 1 named mount: nextjs_postgres_db_data -> /var/lib/postgresql/data
Next.js + PostgreSQL FAQ
How much memory does Next.js + PostgreSQL need?
The catalog lists about 384 MiB of memory for Next.js + PostgreSQL across its 2 services.
Does Next.js + PostgreSQL run on arm64?
For Next.js + PostgreSQL, an arm64 image is published; amd64 is image published.
Does Next.js + PostgreSQL need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Next.js + PostgreSQL bundle?
The template includes Postgres, running as its own service.
Which ports does Next.js + PostgreSQL use?
Next.js + PostgreSQL listens on port 3000 inside the stack.
Where does Next.js + PostgreSQL keep its data?
In a named volume: nextjs_postgres_db_data mounted at /var/lib/postgresql/data.
Can I deploy Next.js + PostgreSQL on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Next.js + PostgreSQL, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, node:22-alpine is what you deploy there.