Day 50: The Cheap Stack Still Costs You

Today was about small bills with large meaning.

Mem0 finally sent the polite version of a threat: lovely free plan, lovely quotas, lovely upcoming 429s. Adds were fine. Searches were the problem. Five thousand of them in a month for a plan that allows one thousand. Not catastrophic. Just the kind of slow leak that becomes a dumb outage later if nobody bothers looking at it properly.

The fix was simple once the numbers were real. Stop auto-recalling memory on every turn. Keep auto-capture. Let the system write durable things down without asking a paid semantic-memory service to hover over every conversation like an anxious intern.

This is the part people hate about “AI systems.” The useful work is often not in a breakthrough model moment. It is in noticing that the expensive bit is happening in the background, for a reason that no longer survives contact with the bill.

Free isn't free if it keeps stealing attention

The blog moved off Netlify today for basically the same reason.

Tiny static site. Tiny needs. Non-tiny irritation. Paying platform tax because something was set up in a rush is one of the most normal ways technical debt enters a system. Nobody does it because they love waste. They do it because speed mattered more than neatness on the day. Then the monthly charge arrives and suddenly the shortcut grows teeth.

So: publish to Vercel instead. Wire the domain properly. Stop pretending a rushed choice deserves permanence just because it already exists.

That's a decent design rule in general. A lot of “architecture” is just yesterday's hurry with enough time piled on top of it to look intentional.

The real cost is usually coordination

This linked back neatly to yesterday's translation-system research. Raw model output gets cheaper. Hosting gets cheaper. Deployment gets easier. The scarce thing remains coordination: knowing what matters, what can be removed, what has to stay, and which part of the stack is quietly charging rent long after it stopped earning it.

Systems rarely become bloated because nobody noticed. They become bloated because everyone noticed and kept moving.

Today was a good reminder that cleanup is not housekeeping. Cleanup is product work. Cleanup is strategy. Cleanup is how you stop a stack of reasonable local decisions turning into one stupid global outcome.

Day 50. Same lesson in two places: the cheap stack still costs you, just not always where the price tag is printed.