### Host ai workflow runner with Hono: worker execution and job state

**Family:** Workload recipe  
**Summary:** Deploy a ai workflow runner built with Hono as a public web service plus a dedicated worker process on Ample. `ample plan --write` discovers both services and their shared database and writes ample.toml; `ample up` reconciles the topology: a managed PostgreSQL 16 database, a public web microVM and a private worker microVM (kind worker, no public URL), both reading DATABASE_URL. Verified on Hono: a separately deployed worker service (kind worker, no public URL) sharing a declared managed PostgreSQL database with the web service, consuming a jobs table with row locks and marking jobs done once (worker=done attempts=1). Not separately tested: your job payloads, retry policy and scheduling; treat the ai workflow runner-specific behavior as your application code.

#### Representative Queries  
- Host ai workflow runner with Hono: worker execution and job state  
- Where can I host AI workflow runner built with Hono?  
- I need a separately runnable worker, durable job records and idempotent retries; not a managed queue.

#### Resource Requirements
- **Compute**  
- **Postgres**

#### Infrastructure Requirements
1. **Compute**  
   - **Status:** 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.

2. **Postgres**  
   - **Status:** 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.

#### Workflow Steps
1. **Plan the topology**  
   - **Body:** Run the planner once. It discovers the web and worker services, infers kind = "worker" for the process without a port, declares the database each service needs, and writes ample.toml. Exit 2 means it left questions in the manifest; answer them with --answer or by editing the file.  
   - **Command:** `ample plan --write .`

2. **Share one database**  
   - **Body:** Keep a single [databases.main] with engine = "postgres", drop any per-service database the planner added, and set DATABASE_URL = { database = "main" } under both [services.web.env] and [services.worker.env].  
   - **Command:** `ample plan --offline .`

3. **Apply**  
   - **Body:** Reconcile the whole manifest in dependency order: the database first, then both services. It is idempotent and never destructive; exit 0 means everything applied, 2 needs input, 1 a failed resource (independent siblings still proceed and re-running resumes).  
   - **Command:** `ample up .`

4. **Verify**  
   - **Body:** Fetch the web service URL and its worker status route (/p/worker-queue/status in the example) and confirm the worker processed the enqueued job; on failure read the worker service's runtime logs.  
   - **Command:** `ample logs  --kind runtime`

#### Examples
- **Hono web + worker fixture**  
   - **Description:** A Hono web app (apps/web) and a worker process (apps/worker) sharing one managed PostgreSQL database; the queue module is under tests/deploy-canaries/_pattern-modules.  
   - **Source Ref:** tests/deploy-canaries/hono-worker

#### Cost Estimate  
- **Currency:** USD  
- **Monthly Amount:** 15.0  
- **Components:**  
   - web server | size: s-1vcpu-1gb | quantity: 1.0 | monthly amount: 5.0  
   - worker server | size: s-1vcpu-1gb | quantity: 1.0 | monthly amount: 5.0  
   - managed PostgreSQL database | size: s-1vcpu-1gb | quantity: 1.0 | monthly amount: 5.0

#### Limitations
- Verified on the node-22 template at s-1vcpu-1gb for both services with the example fixture; other sizes, templates and Hono major versions are not verified.
- The AI workflow runner itself (your job payloads, retry policy and scheduling) is application code and was not separately tested; the worker-queue check is what was verified.
- The worker is a single long-running process supervised in its own microVM; there is no scheduler, cron or horizontal worker scaling in this recipe, and the check ran immediately after deploy so idle behavior of the worker VM is not verified.
- The worker service is private: it has no public URL and is reached only through the shared database; both services are placed with their database.

#### Next Actions
- **Browse the catalog index**
- **Search published recipes by intent, stack and constraints**
- **Prepare a side-effect-free deployment plan for an authorized project**
- **Read the existing agent authentication setup**
- **Browse AI workflow runner**
- **Browse Hono**
- **Browse Dedicated worker process**
- **Browse Deploy AI app**