Queue-backed workers architecture
Accept work fast, process it out of band, and keep failures in a dead-letter queue instead of the logs.
AWSsqsworkersdlqasync
What is in it
Every resource, and what it costs.
Projections from August 2026 list prices for always-on resources. Connect an account and these become the figures your provider actually bills.
| Node | Type | What it is | Projected |
|---|---|---|---|
| Submit endpoint | Network | 10M requests | $10/mo |
| Work queue | Messaging | 5M requests | $2.00/mo |
| Workers ×3 | Compute | 3 × 1 vCPU · 2 GB | $108/mo |
| Dead-letter queue | Messaging | low volume | $0.50/mo |
| RDS PostgreSQL | Database | db.t4g.large · single-AZ · 100 GB | $105/mo |
| Results | Storage | 100 GB standard | $3.00/mo |
Agent steps are priced from provider-reported token usage once the agent runs, not estimated. Guardrails cost nothing and are the reason a runaway agent cannot.
Open Queue-backed workers on the canvas.
It loads as an editable graph. Connect an account or instrument an agent and the projected figures above become measured ones.