Host ai chat application with Axum: Postgres-backed state · Ample Computer
Host ai chat application with Axum: Postgres-backed state
Deploy an AI chat application 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 chat application-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 no DATABASE_URL is supplied.
You need
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
build cargo build --release
run time rust
sizes - 1vcpu-2gb
start ./$(ls target/release/*.d | grep -v '/lib' | head -n 1 | sed 's/.d$//')
template ubuntu-24.04
Steps
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.
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 read
ample 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 axum patterns”
✓ durable-job-state self-test· http get/p/durable-job-state → “job=done attempts=1 idempotent=true”
Evidence
November 5, 2026 · canary run
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).November 6, 2026 · canary run
The same Axum app deployed with a --release-command migration; the marker it created was readable after activation.
Tested examples
- Axum pattern fixture. Multi-pattern Axum 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-2gb with the example fixture.
The pattern checks verified the platform side; the AI chat application 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.