Serverless API architecture
HTTP API with function compute and a key-value store. Scales to zero; the floor is the gateway.
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 |
|---|---|---|---|
| API Gateway (HTTP) | Network | 10M requests | $10/mo |
| API handlers | Compute | 5M invocations · 512 MB · ~150 ms | from $8.00/mo |
| DynamoDB | Database | on-demand · ~5M writes, 20M reads | from $15/mo |
| Attachments | Storage | 100 GB standard | $3.00/mo |
| Secrets | External | 1 secret, all your keys | $0.40/mo |
| CloudWatch logs | External | 30 GB ingested | $18/mo |
Every figure is a projection from AWS list prices, before anything is built. 2 rows show from because those services bill by usage, so the total is a scenario at the stated volumes, not a quote.
Similar templates.
Container behind a load balancer
The smallest thing that serves real traffic: a public load balancer in two availability zones and one Fargate container. About four minutes to create and roughly 4¢ an hour, so it is the cheapest way to find out whether a deploy works end to end.
Three-tier web application
The default shape: load balancer, containerised app tier, managed Postgres, cache and asset storage.
Static site on CDN
Marketing site or SPA served from object storage behind a CDN, with DNS and a WAF in front.
Open Serverless API on the canvas.
It loads as an editable graph. Ask Archie to change it, then approve the plan and it is built in your own AWS account.