Connect Postgres for Next.js · Ample Computer
Connect Postgres for Next.js
Connect a Next.js app to PostgreSQL on Ample from a route handler. Read DATABASE_URL at request time (force-dynamic) with pg; with no DATABASE_URL supplied, Ample auto-provisions a managed PostgreSQL 16 database and injects its connection string as an encrypted environment variable.
Verified November 6, 2026
What it runs on
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and noDATABASE_URLis supplied.
You need
- The pg driver in dependencies and a route handler that reads
process.env.DATABASE_URLat request time - Either a production
DATABASE_URLto pass with --env, or nothing (auto-provision) - An Ample account token with
servers:writeanddatabases:read
Exact tested configuration
- build
npm run build --if-present - install
npm install - runtime
node - sizes
1vcpu-1gb - start
npm run start - template
node-22
Steps
Keep the database out of the build. Mark the route handler dynamic and open the client per request; next build must not need the database.
Deploy. Omit
DATABASE_URLto auto-provision, or pass--env DATABASE_URL=...to use an existing database.
$ ample deploy . --name <app-name> --public
Test through the app. Fetch the route; it should report
postgres=okafter a real query.Verify. Fetch the live URL and run the success checks below. On failure read the build log, then the runtime log, fix the cause and deploy again; do not blind-retry.
$ ample logs <deployment_id> --kind build
How it was checked
✓ database route reports a live connection · http get/api/db → “postgres=ok”
Evidence
November 6, 2026 · canary run
Next.js 15 route handler using pg with noDATABASE_URLsupplied: Ample auto-provisioned a managed PostgreSQL database and/api/dbreportedpostgres=ok.November 6, 2026 · canary run
Node app needing PostgreSQL with noDATABASE_URL: a managed database was auto-provisioned and/dbreportedpostgres=ok.
Tested examples
- Next.js + pg canary. Route handler
/api/dbwith an auto-provisioned managed database.
What it doesn’t cover
- Verified on the node-22 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
- Apps and their managed databases are placed together, in the same region.
- The app is one long-lived process, so one connection pool serves every request.