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

You need

Exact tested configuration

Steps

  1. 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.

  2. Deploy. Omit DATABASE_URL to auto-provision, or pass --env DATABASE_URL=... to use an existing database.

   $ ample deploy . --name <app-name> --public
  1. Test through the app. Fetch the route; it should report postgres=ok after a real query.

  2. 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

  1. November 6, 2026 · canary run
    Next.js 15 route handler using pg with no DATABASE_URL supplied: Ample auto-provisioned a managed PostgreSQL database and /api/db reported postgres=ok.

  2. November 6, 2026 · canary run
    Node app needing PostgreSQL with no DATABASE_URL: a managed database was auto-provisioned and /db reported postgres=ok.

Tested examples

What it doesn’t cover