Fly.io app and database architecture
Machines close to users, Postgres in the same region, Redis for sessions and rate limits.
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 |
|---|---|---|---|
| Cloudflare CDN | CDN | Pro plan, billed monthly | $25/mo |
| Machines ×3 | Compute | 3 × shared-cpu-1x · 1 GB | $18/mo |
| Fly Postgres | Database | Managed Postgres Basic + $0.28/GB | $38/mo |
| Upstash Redis | Database | Fixed 250 MB plan | from $10/mo |
Every figure is a projection from AWS list prices, before anything is built. One row shows from because those services bill by usage, so the total is a scenario at the stated volumes, not a quote.
Similar templates.
Vercel + Supabase app
The default modern startup stack: hosted front end, managed Postgres and auth, edge cache, payments.
Railway monolith and worker
One web service, one background worker, a serverless Postgres and object storage. The smallest real stack.
GPU batch on Modal
Bursty GPU work triggered from a queue, with inputs and outputs in cheap object storage.
Open Fly.io app and database 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.