Using credits
Catalog row in Vendor License Sources · Cited
- Kind
- Product documentation
- Format
- HTML
- Applies to
- Credit packages, refills, expiry, prepaid billing, fixed-date allocation, plan sharing, rounding, active users, open source credits and Docker layer caching. Page last_updated 2026-10-06.
- Evidence
- Usage rounds up to the next second and then the next credit
- Credits are sold in packages of 25,000 at USD 15
- Performance credits expire one year after purchase
- Free plan receives 30,000 credits and is blocked at zero
- Free plan receives 30,000 credits and is blocked at zero (2)
- Performance plan refills about 25% of the package when credits reach zero
- Scale plan auto-refill triggers at 10% and notifies at 20%
- Declining CAR interrupts service at zero credits
- Prepaid billing discounts start at 5 million credits
- Fixed-date allocations divide the purchase equally
- Child organizations bill usage to the parent organization
- Child organizations bill usage to the parent organization (2)
- Active user is anyone who triggers compute on non-open-source projects (2)
- Open source organizations get 400,000 Linux credits per month
- Open source organizations get 400,000 Linux credits per month (2)
- Open source macOS allowance is stated as 30,000 and 25,000 credits
- Open source macOS allowance is stated as 30,000 and 25,000 credits (2)
- No open source discounts on the Performance plan