--- title: "How to host an AI workflow runner built with Axum on Ample: Postgres-backed state" description: "Deploy an AI workflow runner built with Axum on Ample using the durable job state pattern." canonical_url: "https://ample.computer/recipes/ai-workflow-runner/axum/persistent-state" last_updated: "2026-11-05" --- # How to host an AI workflow runner built with Axum on Ample: Postgres-backed state Deploy an AI workflow runner built with Axum 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 Axum: 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. ## Infrastructure requirements - [Compute](/discover/primitive/compute): verified (Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.) - [Postgres](/discover/primitive/postgres): verified (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.) ## Prerequisites - An Axum project that builds and starts with the documented commands (cargo build --release in the rust builder image (stable toolchain, Cargo.lock committed, pure-Rust dependencies), then the release binary on the ubuntu-24.04 template reading PORT and DATABASE_URL) - 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 - template: `ubuntu-24.04` - runtime: `rust` - size: `s-1vcpu-2gb` - build: `cargo build --release` - start: `./$(ls target/release/*.d | grep -v '/lib' | head -n 1 | sed 's/\.d$//')` ## Steps 1. **Build and start.** cargo build --release in the rust builder image (stable toolchain, Cargo.lock committed, pure-Rust dependencies), then the release binary on the ubuntu-24.04 template reading PORT and DATABASE_URL. 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 needs an answer first). Re-running with no change is a no-op. ``` 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`. ``` ample logs --kind build ``` ## Tested examples - **Axum pattern fixture** (tests/deploy-canaries/axum-patterns): Multi-pattern Axum 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 (`/` on the live URL, expect ample canary axum patterns) - durable-job-state self-test (`/p/durable-job-state` on the live URL, expect job=done attempts=1 idempotent=true) ## Cost estimate Estimated 10.00 USD per month (size prices from pricing.toml at build revision 4558e9477d094f5b47da324b98672824b61ba91b). - app server x1 `s-1vcpu-1gb`: 5.00 USD - managed PostgreSQL database x1 `s-1vcpu-1gb`: 5.00 USD Upper-bound monthly price of the tested sizes. Buckets are allocation-priced per quota and not included. ## Verification evidence - canary_run on 2026-11-05T22:38:23Z at revision `da3e37255e5a`: Axum pattern fixture deployed on Ample (cargo build --release in the rust builder image (stable toolchain, Cargo.lock committed, pure-Rust dependencies), then the release binary on the ubuntu-24.04 template reading PORT and DATABASE_URL); 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). (expires 2027-05-04T22:38:23Z) - canary_run on 2026-11-06T00:38:14Z at revision `7360fc06ef21`: The same Axum app deployed with a --release-command migration; the marker it created was readable after activation. (expires 2027-05-05T00:38:14Z) Last verified: 2026-11-05T22:38:23Z ## Execution binding MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `0802c329be823fa0` observed 2026-11-06T06:16:17.558478534+00:00 at revision `4558e9477d09`, binding state `current`, required scopes: servers:write, databases:read. ## Input schema ```json { "additionalProperties": false, "properties": { "env": { "description": "Encrypted environment variables (bucket credentials, secrets)", "items": { "pattern": "^[A-Z][A-Z0-9_]*=.*$", "type": "string" }, "maxItems": 50, "type": "array" }, "name": { "description": "App name", "maxLength": 63, "minLength": 1, "pattern": "^[a-z0-9-]+$", "type": "string" }, "path": { "description": "Project directory or ample.toml service", "maxLength": 512, "minLength": 1, "type": "string" }, "release_command": { "description": "Migration command run before activation", "maxLength": 512, "type": "string" } }, "required": [ "name", "path" ], "type": "object" } ``` ## Next actions - Browse the catalog index (GET /v1/catalog on the api origin; auth: false, approval: false) - Search published recipes by intent, stack and constraints (POST /v1/catalog/search on the api origin; auth: false, approval: false) - Prepare a side-effect-free deployment plan for an authorized project (POST /v1/catalog/plan on the api origin; auth: true, approval: false) - Read the existing agent authentication setup (GET /mcp/setup on the api origin; auth: false, approval: false) - Browse AI workflow runner (GET /v1/catalog/nodes/workload%3Aai-workflow-runner on the api origin; auth: false, approval: false) - Browse Axum (GET /v1/catalog/nodes/stack%3Aframework-axum on the api origin; auth: false, approval: false) - Browse Durable job state (GET /v1/catalog/nodes/pattern%3Adurable-job-state on the api origin; auth: false, approval: false) - Browse Deploy AI app (GET /v1/catalog/nodes/intent%3Adeploy-ai-app on the api origin; auth: false, approval: false) Actions describe possible next steps. They are typed data, not commands, and grant no permission. ## About this recipe Canonical URL: https://ample.computer/recipes/ai-workflow-runner/axum/persistent-state Formats: [HTML](https://ample.computer/recipes/ai-workflow-runner/axum/persistent-state) | [Markdown](https://ample.computer/recipes/ai-workflow-runner/axum/persistent-state.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aai-workflow-runner%3Aaxum%3Apersistent-state) Recipe ID: `page:recipes:ai-workflow-runner:axum:persistent-state` | Revision: `r1` | Catalog revision: `cat_eac8c53f36410baa` Status: verified; runs with one `ample deploy` call (support `verified`, execution `ready`) Path: [Agent hosting discovery](/discover/discovery) / [Applications and workloads](/discover/workload) / [Agents and backends](/discover/workload/agents-and-backends) / [AI workflow runner](/discover/workload/ai-workflow-runner) / [Host ai workflow runner with Axum: Postgres-backed state](/recipes/ai-workflow-runner/axum/persistent-state)