Categories

VPS vs in-house servers

5 cases50 min of readingLast case: 25 Sep 2026

Everything I talk about on this blog runs on real machines: an internal network of 8 servers and an external network of 6 VPS, which are servers rented on the internet. In this section I explain why I have both, what runs on each and how I decide whether something goes inside or outside: the data, the cost, the availability and how exposed it ends up.

Everything to do with infrastructure belongs here: each machine's hardware, the operating system, how I deploy and configure, the network between home and outside, and what it all costs to maintain. The practical side: how I set up a new VPS before putting it to work, what I do so it doesn't get knocked over in the first few hours, when I use Linux and when Windows, and where each agent, harness and model lives. How models are chosen and used I cover in Local AI. And all of it with the mistakes I made, because most of what I know I learned fixing something I'd done wrong.

And the usual question: is it worth it? I give you the numbers for what the VPS and the in-house servers cost me each month, in money and in maintenance hours, and who each option makes sense for: a freelancer, a small business or someone who enjoys tinkering. You don't need fourteen machines to get something useful out of this section.

What these cases deal with Cases carrying each tag
  1. VPS VPS: 5 of 5 cases
  2. Own server vs VPS Own server vs VPS: 2 of 5 cases
  3. Local AI Local AI: 1 of 5 cases
  4. Set up a VPS Set up a VPS: 1 of 5 cases
  5. VPS for AI VPS for AI: 1 of 5 cases
  6. VPS Linux or Windows VPS Linux or Windows: 1 of 5 cases
  7. What is an AI harness What is an AI harness: 1 of 5 cases

The cases

Closed cases, every Thursday

One email a week with what was verified, what was refuted and what is still on the bench. No news roundups.

You can unsubscribe from any email.