Transmission // 24
Owning the machine again
1 min
Every agent you run on someone else's hardware is a decision you have delegated. Here is what changes when the machine is yours.
There is a version of this industry where “AI tooling” means a browser tab, a monthly invoice, and a model you cannot name running in a region you cannot choose. It works. It is also a rental agreement, and rental agreements have terms that change.
The alternative is not romantic self-hosting for its own sake. It is narrower than that: the parts of the loop that decide things should run where you can see them. The model can live wherever the good models live. The orchestration, the context assembly, the logs, the decision to retry or stop — those belong on hardware you control.
What you get back
A record that outlives the vendor. A session that ran locally left files. You can grep them next year. A session that ran in someone’s console left a UI that may not exist next year.
The ability to say no. When the runtime is yours, an upgrade is a thing you schedule. When it is not, an upgrade is a thing that happens to you, usually mid-task, usually to a prompt you had spent a month tuning.
Honest cost. Local runs have a bill you can read: watts, disk, your time. Hosted runs have a bill that is deliberately hard to attribute to any single decision you made.
What it costs
Latency, mostly, and setup. The first hour of owning your own runtime is worse than the first hour of a hosted one, and anyone who tells you otherwise is selling something too. The trade only pays off past the point where you care what happened last Tuesday.
That is the line we build on. Not “local is pure” — local is legible, and legible is what an operator needs to stay an operator instead of a passenger.