Cloud providers are finally letting you switch your wallet off before it empties itself
AWS and Google Cloud have both quietly added hard spending limits this year - but only as opt-in extras, not the default, and that's the bit worth arguing about.
The claim
Developer Simon Willison has made a simple, if pointed, argument: pay-as-you-go cloud services should shut themselves off by default once you hit a spending limit, rather than merely emailing you about it. He’s not describing a new product. He’s describing a gap - and pointing at two companies that have just started to fill it.
What’s actually changed
AWS quietly rolled out a feature in mid-September letting builders set a monthly spend limit on a project, which pauses that project outright once the limit is hit. Google Cloud got there first, launching “Spend Caps” back in July, which let you set a hard monthly ceiling on specific services within a project.
Both are real, shipped features - not roadmap promises. That’s the checkable part. What’s not yet confirmed is how widely available they are: AWS’s own documentation states the new experience is being rolled out to “a limited number of customers” only, so if you’ve got an existing AWS account, you likely can’t switch this on yet.
Why this matters now
The underlying problem isn’t new - anyone who has rented a server has heard a horror story about a misconfigured script quietly running up a bill. What’s changed is the volume of code being written by non-experts with the help of AI coding assistants. Willison’s point is that “personal agents” - his phrase for coding agents wrapped in friendly chat interfaces - make it trivially easy to spin up something that calls paid APIs or provisions billable storage, without the person doing it fully understanding what happens if it runs unattended.
The nightmare scenario isn’t exotic: a hobby project left running overnight racks up hundreds or thousands of dollars in charges before anyone notices, because the only warning was an email sent at 2am while you slept.
So who is actually affected
Right now: almost nobody, directly. These caps exist for a small rollout cohort on AWS, and for Google Cloud users who’ve gone looking for Spend Caps and switched them on manually. This is not a new default that’s suddenly protecting everyone’s wallet.
If you’re not spinning up your own cloud infrastructure or experimenting with AI agents that can call paid services autonomously, none of this touches you yet. If you are - particularly on personal or side projects - you’re still largely relying on soft limits, which Willison rightly dismisses as “will not cut it,” since a warning email changes nothing about the money already spent.
What to do about it
If you run anything on AWS or Google Cloud that costs money per use, check whether the new limit features are available on your account today, and set them if so. Treat “send me a warning” billing alerts as better than nothing but not as protection. For now, the safest assumption is that any uncapped service will, eventually, bill you for whatever it’s capable of doing - and that’s a design choice by the provider, not an inevitability.
The takeaway
This isn’t a security breach or a product launch with a catch - it’s an industry slowly catching up to a problem AI coding tools have made more common. AWS and Google Cloud have built the tool; they just haven’t made it the default, and that’s precisely the detail worth watching as these features reach general availability.