Vercel + Supabase app architecture
The default modern startup stack: hosted front end, managed Postgres and auth, edge cache, payments.
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 |
|---|---|---|---|
| Next.js app | Compute | 1 seat | $20/mo |
| Postgres + auth | Database | 1 organization · 8 GB | $25/mo |
| Upstash Redis | Database | Fixed 250 MB plan | from $10/mo |
| File storage | Storage | 500 GB · no egress fee | $8.00/mo |
| Stripe | External | per-transaction | no direct cost |
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. 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.
Fly.io app and database
Machines close to users, Postgres in the same region, Redis for sessions and rate limits.
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 Vercel + Supabase app on the canvas.
It loads as an editable graph. Connect an account or instrument an agent and the projected figures above become measured ones.