> ## Content Index > Fetch the complete content index at: https://builtonside.com/llms.txt > Use this file to discover other available public pages before exploring further. # I Host Client Websites As a Side Hustle. Here's the Problem That Almost Made Me Quit. - URL: https://builtonside.com/i-host-client-websites-as-a-side-hustle-heres-the-problem-that-almost-made-me-quit/ - Published: 2026-09-26T08:06:00.000Z - Updated: 2026-09-26T08:07:24.000Z - Author: Mikko - Tags: Side Hustle Ideas "Learn web design, get a few local clients, host their sites" shows up on basically every side hustle list ever written. It's usually filed under "easy ways to make money with your laptop," right next to reselling stuff on eBay. Nobody mentions the part where you become responsible for someone else's website staying online. Forever. Even the ones you built two years ago and haven't thought about since. [I've mentioned before](https://builtonside.com/five-failed-side-hustles-one-pattern/) that most of my week is already spoken for by client dev work. Some of that work is hosting, too, small agency-style stuff, a handful of client sites, hosting included because that's what clients actually want to pay for. It went fine for a long time. Then one afternoon, a site that had nothing wrong with it went down anyway. ## The way almost everyone starts You get your second client, then your third. Each one gets a server. Sometimes it's a proper VPS, sometimes it's "reselling" a platform like Vercel or Netlify under the hood. Either way: one client, one box, one bill. This works. I'd defend it to anyone who says otherwise. It's simple, it's understandable at 2am, and you don't need to learn anything new to do it. It also means every client is its own little island of maintenance. Security patches. That one dependency that only works on the old version of something. The slow realization that "quick side hustle" now involves babysitting a handful of tiny servers like they're plants that die if you look away too long. ## The part nobody warns you about Eventually the maintenance tax gets annoying enough that you look for a shortcut. The obvious one: stop giving every client their own server, put a few of them on one bigger box instead. Save money, save time, fewer plants to water. Here's what actually happens. I found a real thread from another small agency doing exactly this: they'd set everything up properly, isolated each client the correct way, and then one client ran a marketing campaign. Traffic spiked. Two completely unrelated clients' sites slowed to a crawl because of it. I hit my own version of this. Not even a traffic spike, just a normal deploy for one client. It quietly started eating the resources a neighboring client's site needed to stay fast. Nothing that client did wrong. Nothing I'd have caught by watching their site specifically. It just happened, on a completely separate business, because of a stranger's rollout three doors down. That's the moment "host client sites as a side hustle" stopped feeling like a simple weekend skill and started feeling like a liability I didn't fully understand yet. ## What I actually did about it The fix wasn't a bigger server. It was setting an actual limit on how much of the shared box any one client's deploy could grab, so a rollout can't quietly starve someone else. Small config change, once you know it exists. The knowing-it-exists part is the whole problem. That single incident is basically why I started documenting the entire setup properly instead of just patching it and moving on. Real numbers, since "it's cheap" isn't useful without them: running this the automated, shared way costs about €136 a month for four sites. Total. Not per site. I'm turning what I learned into an actual course and template repo. It's not finished. I'm still hitting edge cases and writing them down as they happen instead of tidying them up after the fact. If you want to see where that's headed: [sisuops.dev](https://sisuops.dev/?ref=builtonside.com). ## Why this is on a side hustle blog at all Most of what gets written about "build websites for local businesses" stops at getting the first client. Nobody follows up a year later when you've got six of them and you're the only person who understands how any of it stays online. If that's not you, this probably isn't useful reading, and that's fine. But if you're doing freelance web work, or thinking about it, this is the wall you eventually hit whether anyone warned you or not. I'd rather you hear about it now than find out the way I did.