Why I chose to own my own stack

There's a version of running a business where you outsource everything that's boring and critical — the hosting, the backups, the uptime, the "it just works" promise. You pay for it, and you never think about it. That version is comfortable. It is also, eventually, someone else's machine, someone else's schedule, and someone else's answer when things break at 2 a.m.

A few years ago I had that uncomfortable morning — the one where the platform my whole operation depended on was down, and I could do nothing but refresh a status page and wait. I resolved then that the systems my business runs on would be mine.

Ownership is a responsibility, not a flex

I want to be honest about what this costs. Owning your stack means you are the fallback. When a service dies, there's no ticket to file — there's a terminal, a log, and you. You carry the pager even when nothing is wrong, because you know that you are the reason it's still up.

But that responsibility buys back the thing I actually wanted: agency. I can move, change, scale, and fix without asking permission or waiting on a roadmap. The ceiling isn't "what my provider offers" anymore.

Outsourcing isn't bad. Outsourcing the thing your business depends on, without understanding it, is.

What I actually run

The systems behind my companies now live on hardware I control, behind a reverse proxy I set up and a certificate I own. One server runs a lot of what keeps the operation moving — the platforms, the automation, the agents that help with the daily work. It's not exotic; it's a deliberate pile of open tools, each one chosen because I understand it.

What ownership returned

Three things I didn't predict. First, speed — changes that used to take a ticket and a day now take me an evening. Second, a real understanding of how the machine underneath my business works; that understanding has paid for itself many times over. Third — and this surprised me most — a kind of calm. The 2 a.m. moments still happen, but now they're mine, and I can do something about them instead of refreshing a page.

I'm not saying everyone should host their own everything — that would be terrible advice for most people. I'm saying the question is worth asking, and the answer isn't automatically "pay someone else and forget it." Sometimes the most important system you own is the one you actually, literally, own.

If you're weighing the same decision, I wrote a companion guide on how I choose the right tool for each job, and one on building teams of software agents.