Connect Postgres for Express · Ample Computer
Connect Postgres for Express
Connect an Express app to PostgreSQL on Ample. Read DATABASE_URL at runtime: when you supply one with --env it is delivered encrypted and takes precedence; when you supply none and the app needs PostgreSQL, Ample auto-provisions a managed PostgreSQL 16 database and injects its connection string.
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 no DATABASE_URL is supplied.
You need
- The pg driver reading process.env.DATABASE_URL
- Either a production DATABASE_URL to pass with --env, or nothing (auto-provision)
- An Ample account token with servers:write and databases: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
Read the URL at runtime. Construct the pg Pool from process.env.DATABASE_URL inside the app; never commit credentials.
Choose the source of the database. Pass --env DATABASE_URL=... for an existing database, or omit it to let Ample provision a managed one on first deploy and reuse it on redeploys.
$ ample deploy . --name <app-name> --public --env DATABASE_URL=postgres://...
Test the connection through the app. Expose a route that runs a trivial query and returns postgres=ok, then deploy and fetch it.
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/items → “postgres=ok”
Evidence
November 6, 2026 · canary run
Express REST API using pg with no DATABASE_URL supplied: Ample auto-provisioned a managed PostgreSQL 16 database, injected the connection string, and /items reported postgres=ok after a real insert and count.November 6, 2026 · canary run
Node app needing PostgreSQL with no DATABASE_URL: a managed database was auto-provisioned and /db reported postgres=ok.November 6, 2026 · canary run
A supplied DATABASE_URL was delivered as an encrypted environment variable; the app saw the configured host and the secret was never echoed by the platform.
Tested examples
Express + pg canary. Auto-provisioned managed database with a real insert and count.
Supplied DATABASE_URL. An explicit connection string delivered as an encrypted environment variable.
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.
- A supplied URL is used as-is, so an external database stays where it is; make sure it accepts connections from the app.