Costs and Capacity
This month at a glance
What to buy so nothing stops
Each account's balance against what the rest of this month needs (scheduled monitoring plus planned audits), times a safety factor. "Buy" is the amount that brings the balance up to that line. A balance that was never read or typed shows "not read", never zero.
Accounts and keys
Every paid service the platform and the audit use, whether this server has its key, and how its balance is read. Anthropic, OpenAI, TypeSafe and the others publish no balance, so type it here after you check their billing page.
Before you run an audit
Price one audit on each account before it starts, checked against the balances above. Answer costs are the pipeline's measured rates; reading is the measured Anthropic rate; the Claude Code session is the amount set in config/cost-forecast.json. Saving it as planned counts it into "What to buy" until you mark it done.
Planned audits
Forecast by account
Each organization's recorded spend this month and its monitoring forecast for a full month. "Scheduled" counts the clients the scheduler will run; "sold" counts every saved plan, scheduled or not. A scheduled client with no saved plan is priced at the recommended plan.
Every client in the forecast
Monthly bills
Costs that are not per answer: the Supabase plan, the server, subscriptions, domains. They are charged to a card, so they are in the month's total but not in "What to buy".
Storage
The database and file storage in Supabase, and the server's disk and memory, against their limits. Growth comes from one reading a day, taken when this page opens; the projected full date needs at least two days of readings.
Storage by tenant
An estimate: Postgres keeps no size per row, so each table's size is split by each tenant's share of its rows. Small tables are counted exactly; large ones use the database's own statistics, so a tenant with very few rows can read low.