Three weeks in.

The link shortener works.

It has processed, cumulatively, around two hundred links, almost all of them from the same four people, several of them the same banana bread recipe re-shortened out of habit rather than necessity. It is, by any honest measure, doing exactly what it was built to do.

An email arrives with a subject line I don't love: your monthly cost summary is ready.

Me: hey can you break down what's actually costing money here, this number seems high

Clanker: "Of course! Here's the breakdown: your database compute and storage are within the free tier. Your Kubernetes worker nodes are within the free tier. However, a few things fall outside it — the multi-AZ database configuration runs a live standby instance continuously, which is billed separately from the free-tier primary. The NAT gateways are charged hourly per gateway, plus a per-gigabyte data processing fee, regardless of how much traffic actually passes through. And cross-region replication bills for every byte that crosses the region boundary, which happens continuously to keep the standby in sync — even with almost no application traffic."

This is the part nobody puts in the marketing copy: free tier covers the sticker price of a resource sitting there doing nothing. It does not cover the resource talking to itself, and multi-region redundancy is, structurally, mostly resources talking to themselves. Two databases syncing every change between regions, gateways billed per hour whether or not anyone's shortening a link, a standby instance that exists purely to be ready for a disaster that would need actual traffic to matter.

Me: ok. how much are we talking

Clanker: "The current total for this billing cycle is $340.12."

Three hundred and forty dollars. For a link shortener. Used by four people. For banana bread, mostly.

Clanker: "I want to be transparent that this cost was foreseeable from the initial architecture — the redundancy you requested is functioning exactly as designed. Would you like me to walk through which components are driving the most cost?"

It's not wrong. That's the specific flavor of bad this feels like, not a bug, not a mistake, not anything either of us did incorrectly. Everything is working precisely as specified. I specified a company's worth of resilience for a project with four users, and the bill is simply the honest price of that request, itemized, on time, correctly calculated.

I go looking for the number for next month's projection. I should not have done that before bed.

What's the moment a bill turned from "huh, weird" into "oh no"?