Hard budget caps are the least glamorous feature in tech right now, and quite possibly the one that saves you the most money. If you've ever handed a job to an AI coding agent and gone to bed, you know the feeling — what if it just... keeps going? On 3 October 2026, Simon Willison made the case on his blog that hard budget caps should be the default on pretty much everything that charges by usage, and the big cloud providers look like they're coming around.
What happened
Willison's argument is short and blunt. Any service or API that bills you by usage should let you say: after $X a month, cut this thing off and return errors. Not “send me an email.” Actually stop.
That difference is the whole point. A soft cap emails you at midnight to tell you you've blown through your limit. A hard cap pulls the plug. Soft caps “will not cut it,” as Willison puts it, because the warning lands while the meter is still spinning.
A bill you don't want to wake up to
The scenario he describes is pretty ordinary. Coding agents — and personal agents, which are really just coding agents wrapped in a less intimidating interface — have made it almost effortless to spin up code that does something useful. Sometimes that something costs money: calls to paid APIs, a hosted web app, extra storage and compute you can be billed for later. You go to sleep. It keeps running.
Then you wake up to an email timestamped just after midnight, warning about a budget limit, and discover that while you slept your little project burned through several hundred — or several thousand — extra dollars.
The obvious pushback is that businesses don't want their hosted apps throwing errors because someone crossed a budget line. Willison's answer: most businesses and individuals would rather see an error than a surprise bill of $10,000 or more. So cap by default, and make going uncapped an opt-in. His suggested wording is a nice, clear checkbox: “Remove the budget cap. My application will not be shut down if I exceed the configured budget limit, and I will be responsible for subsequent charges.”
AWS and Google Cloud are already there
The twist is that the feature is arriving. AWS launched spending limits a few weeks before Willison's post, in an announcement on 16 September titled “New AWS experience helps builders get started and ship faster.” Once you upgrade to a paid plan, you can set a monthly spend limit for your project based on your usage patterns — and if a project's usage reaches that limit, the project is paused for the month. There's a catch: the AWS help page on creating a spend limit in AWS Settings notes that the new experience is currently being released to a limited number of customers.
Google Cloud got there first. It launched Spend Caps in July, which let you set a monthly financial cap on specific services within a project. Two major clouds, the same idea, a few months apart. That's a trend, not a coincidence.
What it means for you
You don't have to run a startup for any of this to matter. Anything that bills by usage — API calls, storage, compute, hosted apps — can quietly outrun what you expected it to cost.
At home
Maybe you built a small dashboard that checks apartment listings every hour. It costs pennies and you forget about it. Then a loop breaks and it starts hammering a paid API every few seconds. With a cap, the service pauses and you fix it over coffee. Without one, you're having an uncomfortable conversation about a few hundred dollars.
At work
This is where a pause gets awkward. If a shared internal tool hits its monthly spend limit on the 12th, someone downstream can't do their job. That's the real trade-off, and it's exactly why the answer isn't “cap everything silently” — it's “cap by default, then let the team decide which projects are allowed to run hot.”
In business
Picture a small shop with an AI chat assistant on its website. Most months it costs pocket change. Then a viral post or a swarm of bots sends usage through the roof. A hard cap means the assistant goes quiet until you fix it. The alternative is a bill that eats the month's profit. Most owners will take the quiet assistant.
For students and self-learners
Beginners are the most exposed group, because they're experimenting on free tiers and don't yet know where the paid lines are. A spend limit turns a potentially expensive mistake into a cheap lesson — you get an error message instead of a debt.
For creative work
Generating images, audio or video is metered with a big appetite, and one enthusiastic afternoon of prompts can trigger hundreds of paid calls. Capping the monthly budget means a wild experiment can't turn into a wild invoice.
For income projects
Here's where it gets serious. If you freelance or sell something built on usage-based tools, your costs are someone else's project budget. Before you quote a client, run your numbers through a free estimator — sites like mykreatool.com have free AI tools that are handy for quick cost and copy work — then set your cap before you deploy, not after the first invoice lands.
How to try it right now
Step 1 (free): set a cap before you spend anything
If you have a Google Cloud project, start there. Google Cloud Spend Caps let you set a monthly financial cap on specific services inside a project. Setting it doesn't cost anything, so you can lock it in on a free-tier project before you write a single line of production code.
Step 2: create a spend limit in AWS Settings
In AWS, head to AWS Settings and create a monthly spend limit for your project, based on the usage you expect. If the project reaches that limit, the project is paused for the month. One caveat: AWS says the new experience is rolling out to a limited number of customers, so you might not see it in your account yet.
Step 3: if you can't get the new feature yet
Do the boring workarounds. Give each experiment its own account or project, so one runaway service can't touch everything else. Put a low-limit card on file instead of your main one. Treat budget alert emails as a nudge to go look, not as protection. And delete resources you've stopped using — idle storage and compute still bill.
Step 4: tell your agents what you want
Willison's closing wish is that AI agents start recommending providers with hard budget caps and warn new, inexperienced builders away from uncapped services. You can push that along today by putting it in your own instructions: prefer providers with hard spending limits, and flag anything that could bill you more than $X a month.
Upsides and what changes
The upside is simple: an error message instead of a financial emergency. Caps make it safe to experiment, which is the whole reason people build with AI agents in the first place.
They also change how providers compete. Once AWS and Google Cloud both advertise a spend limit, the missing cap becomes a reason to pick someone else — and that pressure spreads to smaller API vendors too. Expect caps to show up as bullet points on pricing pages within a year.
For teams, the benefit is predictability. A paused project is annoying, but it's visible and fixable. A five-figure bill is annoying, visible, and already spent.
Limitations
Hard caps aren't magic. Google's version covers specific services within a project rather than your entire cloud bill, and AWS's is still rolling out to a limited set of customers, so you may not be able to switch it on today. A cap also can't tell the difference between a hobby project and a service real customers depend on — when it trips, it pauses everything, and for some teams that outage costs more than the overage would have. And none of this helps you on providers that still don't offer a cap at all; there, the best you can do is separate accounts, limited-balance cards, and alert emails you actually read.
Conclusion
The direction is clear. The same way seatbelts and circuit breakers became standard, hard budget caps are turning into a normal part of pay-as-you-go services. Until every vendor catches up, though, the responsibility sits with you.
One action for today: log into your cloud billing console — Google Cloud Spend Caps or Create a spend limit in AWS Settings — and set a monthly limit lower than the bill you'd be upset about. It takes a few minutes, and it's the cheapest insurance you'll buy this year.
Comments 0