# Connect Postgres for Fastify

Connect a Fastify app to PostgreSQL on Ample. Read DATABASE\_URL at runtime with pg: 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](/content/discover/primitive/compute/index.html)
  Apps run in isolated x86\_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)
  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

- pg reading the DATABASE\_URL environment variable at runtime
- 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

1. build `npm run build --if-present`
2. install `npm install`
3. runtime `node`
4. sizes - `1vcpu-1gb`
5. start `npm run start`
6. template `node-22`

## Steps

1. **Read the URL at runtime.** Open connections from the DATABASE\_URL environment variable inside the app; never commit credentials and never connect at build time.

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

3. **Test the connection through the app.** Expose a route (/items) that runs a trivial query and returns postgres=ok.

4. **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

1. November 5, 2026 · canary run
   Fastify REST API using pg with no DATABASE\_URL supplied: Ample auto-provisioned a managed PostgreSQL 16 database and /items reported postgres=ok after a real insert and count.

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

- **Fastify + PostgreSQL canary.** Auto-provisioned managed database with a real query.

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