## The short version

Deploy a GraphQL API 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`.

### WHAT WAS VERIFIED

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

## INFRASTRUCTURE

### What it needs

- [Compute](/content/discover/primitive/compute/index.html): verified (Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.)
- [Postgres](/content/discover/primitive/postgres/index.html): verified (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

### Before you start

- 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`

## STEP BY STEP

### How to do it

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

```bash
ample deploy . --name <app-name> --public
```

4. 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 <deployment_id> --kind build` then `--kind runtime`.

```bash
ample logs <deployment_id> --kind build
```

## EXAMPLES

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

### How to know it worked

- 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

### Cost estimate

Estimated 10.00 USD per month (size prices from pricing.toml at build revision ca0b484a7a9957c573a88d3a32dc603c3c10135a).

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

## EVIDENCE

### Verification evidence

- canary_run on 2026-09-21T02:46:37Z at revision `1d28ae0 (CLI 0.1.21)`: 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-03-20T02:46:37Z)
- canary_run on 2026-09-21T02:46:37Z at revision `1d28ae0 (CLI 0.1.21)`: The same Axum app deployed with a `--release-command` migration; the marker it created was readable after activation. (expires 2027-03-20T02:46:37Z)

## EXECUTION

### Execution binding

MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-22T00:31:22.774679+00:00 at revision `e6446ceea69b`. Binding state at export: `schema_changed`. Required scopes: `servers:write`, `databases:read`.

## NEXT ACTIONS

### Typed next actions

- Browse the catalog index (`GET /v1/catalog` on the api origin; authentication not required, approval not required)
- Search published recipes by intent, stack and constraints (`POST /v1/catalog/search` on the api origin; authentication not required, approval not required)
- Prepare a side-effect-free deployment plan for an authorized project (`POST /v1/catalog/plan` on the api origin; authentication required, approval not required)
- Read the existing agent authentication setup (`GET /mcp/setup` on the api origin; authentication not required, approval not required)
- Browse GraphQL API (`GET /v1/catalog/nodes/workload%3Agraphql-api` on the api origin; authentication not required, approval not required)
- Browse Axum (`GET /v1/catalog/nodes/stack%3Aframework-axum` on the api origin; authentication not required, approval not required)
- Browse Durable job state (`GET /v1/catalog/nodes/pattern%3Adurable-job-state` on the api origin; authentication not required, approval not required)
- Browse Deploy API (`GET /v1/catalog/nodes/intent%3Adeploy-api` on the api origin; authentication not required, approval not required)

Actions describe possible next steps. They are typed data, not commands, and grant no permission. Public discovery never provisions anything; planning requires your own authenticated token and approval happens in your client.

## ABOUT THIS RECIPE

### Identifiers and status

Recipe `page:recipes:graphql-api:axum:persistent-state`. Revision r1.

release **published** support **verified** execution **blocked (schema_changed: live tool schema differs from the recorded binding)**

Formats: [HTML](/content/recipes/graphql-api/axum/persistent-state/index.html) | [Markdown](/content/recipes/graphql-api/axum/persistent-state.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Agraphql-api%3Aaxum%3Apersistent-state)