Where your credits go
Published rate basis checked September 13, 2026. At the standard purchase rate, 100 credits represent $1 of credit value. Credit consumption and the amount of a subscription payment are different.
| Measured quantity | Credits |
|---|---|
| Build minute | 1.642857 |
| One million Worker requests | 98.571429 |
| One million Worker CPU milliseconds | 6.571429 |
| Standard database CU-hour | 72.942857 |
| Performance database CU-hour | 91.178571 |
| Database GB-month | 115 |
| File-storage GB for 30 days | 4.928571 |
| 1,000 mail recipients, published Essentials example | 52.571429 |
Actual charges use the active rate card, measured quantities and microcredit rounding. Your agent can read those cards and usage through the usage API. Storage, history and other operations may add consumption; different mail configurations can have different rates.
An example workload
Twenty build minutes (32.857143 credits), 100,000 worker requests (9.857143), one million CPU milliseconds (6.571429), four standard database CU-hours (291.771429), one database GB-month (115), and 2,000 Essentials mail recipients (105.142857) total 561.2 credits: $5.612 in credit value.
Five identical workloads total 2,806 credits. At the standard pack rate, 3,000 credits would cover these selected quantities. This is arithmetic, not a benchmark, a guaranteed bill or a complete estimate for an unspecified app.
A separate subscription scenario
One developer on Vercel Pro ($20), one Supabase Micro project on Pro ($25 total) and Resend Pro ($20) totals $65/month before extras and taxes. With five Supabase Micro projects, that scenario totals about $105/month. Vercel and Resend base plans are not charged again for each project. Free allowances can reduce the alternative cost, and the services do not offer identical capacity or features.
Sources: Vercel, Supabase billing, Resend.