Servers That Cannot Be Held Hostage
Most teams rent their infrastructure and learn the price of that dependency when a bill, a ban, or an outage arrives. Owning the box is a governance decision.
Most teams rent the ground their business stands on. The servers, the storage, the platform underneath the product. It works, it is convenient, and for a long time you never think about it. Then a bill triples overnight, an account gets flagged by an automated system, or a region goes dark, and you discover exactly how much of your business was sitting on someone else's terms.
That is the hostage problem. Not that renting is wrong. It is that renting quietly converts the foundation of your business into a dependency you do not control, and you only find out the price of that dependency at the worst possible moment.
What the hostage problem actually looks like
It rarely shows up as a dramatic failure. It shows up as a loss of leverage. The provider changes pricing and your margin moves without your say. An automated policy decides your account looks suspicious and your service is gone before a human ever reads your appeal. A platform deprecates the thing you built on and hands you a migration you did not ask for and cannot decline.
In every one of those, the technical layer is fine. The problem is that the decision was never yours to make. You can be the most careful operator in the world and still wake up to a ban, a bill, or an outage you had no hand in and no recourse against. That is what it means to be held hostage by your own infrastructure.
This is the problem HostSSH is named after: servers that cannot be held hostage, because you own the box your business runs on.
Owning the box is a governance decision, not a cost one
The usual argument for self-hosting is price, and yes, owning your infrastructure is often cheaper. But cost is the small reason. The real reason is control.
When you own the box, a different set of things becomes true:
- no third party can price you out of your own foundation
- no automated policy can switch off your business without your involvement
- no platform roadmap can force a migration on your schedule
- the data your business depends on lives somewhere you actually control
Those are not line items on an invoice. They are governance properties. Owning the box is the difference between a business you run and a business you operate at someone else's discretion. The bet on price is small. The bet on control is the whole company.
Why this is the same decision as everything else
I run my whole portfolio on infrastructure I own, and the reason is the same one that governs the rest of how I build: own the things your business depends on. AI is a seam I keep swappable so no provider holds it hostage. The stack is owned so no platform holds it hostage. It is one principle applied all the way down.
A single rented product is an annoyance to lose. A foundation everything sits on is not something you want held by anyone else's terms. The more your business depends on a thing, the more it matters that the thing is yours.
The close
The price of renting your foundation is invisible right up until it is the only thing you can see. Owning the box is how you make sure a bill, a ban, or an outage is never someone else's decision to make about your business.
Control of the stack is a governance choice, not a cost choice. That is the choice I made for everything I run, and the reason is the same every time. More on how I think about owning the stack is on the about page.