The $91,316 vibe code bill — the podcast
The origin story, out loud: how a weekend of vibe-coding a real-time strategy game turned into a five-figure cloud bill — and why we built a kill switch so it can’t happen again.
Listen
What you’ll hear
The whole arc of the bill that started this company: a side project, an AI coding agent told to give every unit in an RTS its own brain, and a fleet of connections that came to life and never died. By the time the invoice landed, it had five digits and a comma.
- How “vibe coding” quietly wired up thousands of always-on connections.
- Why nothing alerted us until the bill did — cloud providers ship no hard spending cap.
- What we changed, and the kill switch we built so a runaway can trip itself off.
Read the full autopsy
Prefer to read it — commits and all? The written breakdown goes deeper on the architecture and the exact line that did the damage: The $91,316 bug: I gave every unit in my RTS its own AI agent. There’s a video version too.
The bill was the first time we found out — that’s the whole problem. Kill Switch watches your cloud and AI spend and trips before a runaway becomes a five-figure surprise. Free tier, one account. Put the seatbelt on before the wreck.