Host ai workflow runner with Express: worker execution and job state · Ample Computer

Host ai workflow runner with Express: worker execution and job state

Deploy an AI workflow runner built with Express as a public web service plus a dedicated worker process on Ample. ample plan --write discovers both services and their shared database and writes ample.toml; ample up reconciles the topology: a managed PostgreSQL 16 database, a public web microVM and a private worker microVM (kind worker, no public URL), both reading DATABASE_URL. Verified on Express: a separately deployed worker service (kind worker, no public URL) sharing a declared managed PostgreSQL database with the web service, consuming a jobs table with row locks and marking jobs done once (worker=done attempts=1). The AI workflow runner-specific behavior (your job payloads, retry policy and scheduling) is your application code on that verified basis.

What it runs on

You need

Exact tested configuration

buildnpm run build --if-present

installnpm install

runtimenode

sizes-1vcpu-1gb

startnpm run start

templatenode-22

Steps

  1. Plan the topology. Run the planner once. It discovers the web and worker services, infers kind = "worker" for the process without a port, declares the database each service needs, and writes ample.toml. Exit 2 means it left questions in the manifest; answer them with --answer or by editing the file.
   $ ample plan --write .
  1. Share one database. Keep a single [databases.main] with engine = "postgres", drop any per-service database the planner added, and set DATABASE_URL = { database = "main" } under both [services.web.env] and [services.worker.env].
   $ ample plan --offline .
  1. Apply. Reconcile the whole manifest in dependency order: the database first, then both services. It is idempotent and never destructive; exit 0 means everything applied, 2 needs input, 1 a failed resource (independent siblings still proceed and re-running resumes).
   $ ample up .
  1. Verify. Fetch the web service URL and its worker status route (/p/worker-queue/status in the example) and confirm the worker processed the enqueued job; on failure read the worker service's runtime logs.
   $ ample logs <deployment_id> --kind runtime

How it was checked

✓web service responds on its public URL· http get/ → “ample canary express patterns”
✓worker consumed the enqueued job· http get/p/worker-queue/status → “worker=done attempts=1 result=processed-by-worker”

Evidence

  1. November 5, 2026 · canary run

Express web service plus a separate Express worker process deployed on Ample with ample plan --write then ample up (npm install, npm run build --if-present, npm run start on the node-22 template); the web service enqueued a job that the private worker service consumed from the shared managed PostgreSQL database. Pattern proof: a separately deployed worker service (kind worker, no public URL) sharing a declared managed PostgreSQL database with the web service, consuming a jobs table with row locks and marking jobs done once (worker=done attempts=1).

Tested examples

What it doesn’t cover