Host ai workflow runner with NestJS: Postgres-backed state · Ample Computer
Host ai workflow runner with NestJS: Postgres-backed state
Deploy an AI workflow runner built with NestJS on Ample using the durable job state pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL. Verified on NestJS: a jobs table with a state and attempts counter, processing inside a row-locked transaction, and a second run that is a no-op (job=done attempts=1 idempotent=true). The AI workflow runner-specific behavior (your job types, payload schema and retry policy) is your application code on that verified basis.
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 no DATABASE_URL is supplied.
You need
A NestJS project that builds and starts with the documented commands:
npm install,nest build(TypeScript) thennode dist/main.json the node-22 template.A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
An Ample account token with
servers:write,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
Build and start.
npm install,nest build(TypeScript) thennode dist/main.json the node-22 template. The server must bind 0.0.0.0 on PORT.Implement the pattern on PostgreSQL.
The fixture's module implements durable job state: a jobs table with a state and attempts counter, processing inside a row-locked transaction, and a second run that is a no-op (job=done attempts=1 idempotent=true). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.Deploy.
Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 needs an answer first). Re-running with no change is a no-op.$ ample deploy . --name <app-name> --publicVerify.
Fetch the live URL and the pattern self-test route(s) (/p/durable-job-state) from the example; then run your own checks. On failure readample logs <deployment_id> --kind buildthen--kind runtime.$ ample logs <deployment_id> --kind build
How it was checked
✓ app responds on its public URL · http get/ → “ample canary nestjs patterns”
✓ durable-job-state self-test · http get/p/durable-job-state → “job=done attempts=1 idempotent=true”
Evidence
November 6, 2026 · canary run
NestJS pattern fixture deployed on Ample (npm install, nest build (TypeScript) then node dist/main.js on the node-22 template); checks passed for durable-job-state and configuration-secrets. Pattern proof: a jobs table with a state and attempts counter, processing inside a row-locked transaction, and a second run that is a no-op (job=done attempts=1 idempotent=true).November 6, 2026 · canary run
The same NestJS app deployed with a --release-command migration; the marker it created was readable after activation.
Tested examples
- NestJS pattern fixture.
Multi-pattern NestJS app whose durable job state module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
What it doesn’t cover
Verified on the node-22 template at s-1vcpu-1gb with the example fixture.
The pattern checks verified the platform side; the AI workflow runner itself (your job types, payload schema and retry policy) is your application code.
Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.