Simon Willison calls for default hard budget caps on pay-as-you-go services
What happened
On 4 October 2026, Simon Willison argued that pay-as-you-go APIs and services should have hard budget caps by default, cutting off access and returning an error once $X/month is reached rather than just sending a warning email. He noted that AWS launched monthly spend limits on 16 September, pausing a project for the rest of the month once it hits the limit, though the feature is currently available only to a limited set of customers, and that Google Cloud introduced Spend Caps in July.
Written by AI from the reports · updated 12 d ago
Timeline
Follow the reports to see the event from each side.
- Simon WillisonWe're going to need default hard budget caps on pretty much everything
Here's a product feature which the world is going to need a whole lot more of over the coming months and years: default hard budget caps . I'm talking about the feature of pay-by-usage services and APIs that lets you say "after $X/month, cut this thing off and return errors". These need to be hard limits.