### Host ai workflow runner with Gin: Postgres-backed state

#### Summary
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). Not separately tested: your job types, payload schema and retry policy; treat the ai workflow runner-specific behavior as your application code.

#### Representative Queries
- Host ai workflow runner with Gin: Postgres-backed state
- Where can I host AI workflow runner built with Gin?
- I need a durable state schema and retry/recovery semantics implemented by application code.

#### Resource Requirements
- primitive:compute
- primitive:postgres

#### Infrastructure Requirements
- **Compute**: Verified
  - Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **Postgres**: Verified
  - Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

#### Prerequisites
- A Gin project that builds and starts with the documented commands (CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build))
- 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

#### Tested Configuration
- Template: ubuntu-24.04
- Runtime: go
- Size: s-1vcpu-1gb
- Build: CGO_ENABLED=0 go build -o app ./...
- Start: ./app

#### Workflow Steps
1. **Build and start**: CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build). The server must bind 0.0.0.0 on PORT.
2. **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.
3. **Deploy**: Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op. Command: ample deploy . --name  --public
4. **Verify**: 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 read `ample logs  --kind build` then `--kind runtime`. Command: ample logs  --kind build

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

#### Success Checks
- app responds on its public URL (http_get, path: /, expect: ample canary gin patterns)
- durable-job-state self-test (http_get, path: /p/durable-job-state, expect: job=done attempts=1 idempotent=true)

#### Limitations
- Verified on the ubuntu-24.04 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Gin major versions are not verified.
- The ai workflow runner itself (your job types, payload schema and retry policy) is application code and was not separately tested; the pattern checks are what was verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

#### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.
- **Components**:
  - App server: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
  - Managed PostgreSQL database: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0

#### Evidence Summary
1. **Canary run**: Gin pattern fixture deployed on Ample  (observed at 2026-09-21T01:15:54Z). Checks passed for durable-job-state and configuration-secrets.
2. **Canary run**: The same Gin app deployed with a --release-command migration; the marker it created was readable after activation (observed at 2026-09-20T02:43:30Z).

#### Last Verified At
- 2026-09-21T01:15:54Z

#### MCP Binding
- Tool Name: ample_deploy
- Implementation Revision: 49962bcade4f

#### Unknowns
- Region availability is unknown until a verified region fact is recorded.
- Compliance attestations are unknown; none are claimed.

#### Formats
- [HTML](/content/recipes/ai-workflow-runner/gin/persistent-state/index.html)
- [Markdown](/content/recipes/ai-workflow-runner/gin/persistent-state.md)
- [JSON](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aai-workflow-runner%3Agin%3Apersistent-state)

#### Next Actions
- [Browse the catalog index](/v1/catalog)
- [Search published recipes by intent, stack and constraints](/v1/catalog/search)
- [Prepare a side-effect-free deployment plan for an authorized project](/v1/catalog/plan)
- [Read the existing agent authentication setup](/mcp/setup)
- [Browse AI workflow runner](/v1/catalog/nodes/workload%3Aai-workflow-runner)
- [Browse Gin](/v1/catalog/nodes/stack%3Aframework-gin)
- [Browse Durable job state](/v1/catalog/nodes/pattern%3Adurable-job-state)
- [Browse Deploy AI app](/v1/catalog/nodes/intent%3Adeploy-ai-app)