Host ai workflow runner with Gin: Postgres-backed state · Ample Computer
Host ai workflow runner with Gin: Postgres-backed state
Deploy an AI workflow runner built with Gin 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 Gin: 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 5, 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 noDATABASE_URLis supplied.
You need
- A Gin project that builds and starts with the documented commands (
CGO_ENABLED=0 go build -o app ./...then./appon the ubuntu-24.04 template (go.sum committed for a reproducible build)) - A PostgreSQL driver reading
DATABASE_URLat runtime (auto-provisioned when omitted, or supplied with--env) - An Ample account token with
servers:write, databases:read
Exact tested configuration
build CGO_ENABLED=0 go build -o app ./...
runtime go
sizes - 1vcpu-1gb
start ./app
template ubuntu-24.04
Steps
Build and start.
CGO_ENABLED=0 go build -o app ./...then./appon the ubuntu-24.04 template (go.sum committed for a reproducible build). 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 gin patterns”
✓ durable-job-state self-test · http get /p/durable-job-state → “job=done attempts=1 idempotent=true”
Evidence
November 5, 2026 · canary run
Gin pattern fixture deployed on Ample (CGO_ENABLED=0 go build -o app ./...then./appon the ubuntu-24.04 template (go.sum committed for a reproducible build)); 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 Gin app deployed with a--release-commandmigration; the marker it created was readable after activation.
Tested examples
- Gin pattern fixture. Multi-pattern Gin 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 ubuntu-24.04 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.