The miller who chained his well to the meter: a Denial-of-Wallet fable
In the village of Wellspring there was a spring that never ran dry, and a lord who owned it. He called it Bedrock, because it was said to be solid as stone — a fixed and trusty floor a man could build his life upon. Able the miller believed him. He unhooked his mill from the little stream he’d always used, chained his mill-race to the lord’s spring instead, and slept easier for it. No more dry summers. No more mending the stream’s banks. The lord tended everything.
What the lord did not say loudly was that the spring was billed by the drop, and the tally never slept. On a good day Able milled his grain, the water ran, the tally ticked, and it all seemed fair.
Then came the night a stranger — call him Charlie — slipped down to the water gate and opened every tap. Not to steal the water — he carried none away — but simply to let it run. By dawn the spring had poured out a year’s worth into the dark. Able had milled no extra grain. He had sold no extra flour. And his purse was empty all the same.
"Solid ground" and "fixed price" are two different promises.
He went, hat in hand, to Baker the baker next door. Years back she’d been offered the lord’s spring too and had said no. Instead she rented a walled well at the edge of town — a flat sum each year, a lock on the pump, and a handcart she could wheel the whole rig away on if the landlord ever turned greedy. She didn’t own the water under the ground; no one in Wellspring did. But she owned the lock, she knew her yearly cost to the coin, and no stranger could run her into ruin in the dark. She lent Able his buckets and, over bread, told him what she’d figured out years ago.
The pun is the whole point
In the real world, Bedrock is what Amazon calls its managed AI service — the place you plug in so you don’t have to run the models yourself. The name is doing quiet work: bedrock means solid ground, a floor that won’t move. And that’s exactly the wrong thing to hear, because the floor that won’t move is the service, not the bill. “Managed” means they tend the spring. It has never meant the tally is capped.
Every metered service you plug into — an AI model API, a managed cloud service, anything billed by use — is Able’s spring. Convenient, always-on, someone else’s problem to maintain. And uncapped by default: the drops keep counting whether the water is doing you any good or not.
What a “Denial-of-Wallet” actually is
You’ve heard of a denial-of-service attack — someone floods your system so it falls over and your customers can’t reach it. A denial-of-wallet is the money version, and it’s nastier because nothing falls over. Everything works perfectly. The meter just runs.
You don't need to be breached to be bankrupted. You need a meter and a bad night.
And “Charlie at the water gate” doesn’t have to be a villain. It’s whoever — or whatever — can make your metered thing run:
- An outsider who finds an AI feature on your site with no lock on it and pumps it all weekend for free (your support bot is someone else’s free ChatGPT).
- A leaked key left in the open — one was found and run up to $55,000.
- Your own apprentice. The most common stranger isn’t a stranger at all — it’s your own code, an agent that loops on a broken tool all weekend, calling the expensive model ten thousand times because nobody was there to say stop.
No break-in. No stolen data. Just a bill you didn’t earn.
Why the managed spring feels so safe (and isn’t)
Because someone else tends it, it feels handled — and cloud billing has no seatbelt. There is no factory setting that says “never let this cost me more than X.” The default is the opposite: run the water, send the bill, and if it’s a hundred times last month’s, that’s your problem at the end of the month, not theirs during the night.
The lock on the pump
Here’s the deflating part of the story: the fix is boring, cheap, and about ten minutes of work you keep putting off. Baker’s whole secret was a lock and a daily ration.
- A hard ceiling that fails closed. A cap that, when hit, shuts the tap — not one that emails you after the water’s gone. “Fail closed” is the whole game: the safe state when something goes wrong is off, not keep pouring.
- A daily ration. A rate limit, so the worst a bad night can cost you is one day’s water, not the farm.
- One controlled tap in front. Don’t let every part of your business chain straight to the meter. Route it through a single point you can watch and throttle — a gateway — so there’s one place to slam shut.
- A lock on the water gate. Auth on the AI feature, so a passer-by can’t run it for free.
If Bedrock (or Vertex, or Azure OpenAI) is already your spring and the bill just jumped, there’s a short list of first checks before you do anything else.
Baker’s well
Notice what Baker did not do. She didn’t dig her own aquifer and become her own water company — that’s its own kind of foolish, and I’ll never tell you to self-host everything. She moved to a well with a price she knew to the coin, a lock she held, and a pump she could wheel away if the terms turned against her. That’s the honest version of leaving the meter: not “own everything,” but stop chaining your livelihood to a tally you don’t control, and keep the ability to pick up and move.
Never chain your livelihood to a meter you don't control.
Able kept the lord’s spring in the end — it was convenient. But he put a lock on the pump, set a daily ration, and slept through the next stranger’s visit. It cost him one night’s water. He never noticed the second one at all.
If you’ve wired an AI feature (or a whole business) into a metered service and you’re not certain what the worst night could cost you, that’s the exact thing I check. Send me your setup or a recent bill and I’ll show you where the water gate is open and where the lock goes — free, within a business day. It’s just me, so it comes straight to me and I answer fast. Show me your meter.