Hosting client apps or sites is one of the more overlooked ways to add recurring revenue to freelance or agency dev work. You already build apps and sites for clients. Hosting them too is a small step, and it's monthly income instead of a one-time invoice.
It's also the part nobody explains well, because it looks simple until you have more than one client on it.
The version that actually scales badly
Most people start the same way: one client, one VPS. Works fine. Second client, second VPS. Still fine, just double the maintenance. By client five or six, you're not running a hosting side business anymore, you're running a small fleet of servers that each need their own security patches, OS upgrades, and babysitting, and none of them are identical because each client's app or site has slightly different requirements.
The maintenance work scales roughly linearly with client count. Every new client is a proportional amount of new upkeep, forever.
What actually changes the math
The fix isn't a bigger server, it's a shared platform layer that isolates clients from each other without giving each one their own OS to maintain. Kubernetes is the standard tool for this, not because it's trendy, but because the orchestration problem (schedule workloads, restart what dies, isolate resource usage between tenants) is exactly the problem you have once you're past a couple of clients.
I've written what that actually means in plain terms if the term itself is new, and the specific maintenance-load argument with a real cost breakdown if you want the numbers: €136 a month, total, for 4 sites on a shared cluster right now. Not per site. Total.
What this actually requires from you
Being direct about this, since most "start a hosting business" content skips it: you need to actually understand the platform you're running, not just click deploy on a managed product. If a client's app or site goes down at 11pm, you're the one who gets the call, and "I don't know why" isn't an acceptable answer when someone's paying you monthly for this.
That's real time investment up front. It's not a weekend project. It's also not a full platform-engineering career either, the setup only needs to be built once, then it's mostly maintenance that doesn't grow linearly with client count anymore, which is the entire point.
Where to actually start
Don't start by provisioning your first client's server manually and figuring it out live. Build the platform layer first, on your own infrastructure or a test site, before a paying client is depending on it. Get comfortable with what happens when you deploy a change, what happens when something crashes, before either of those happens with someone else's business on the line.
If this is useful, tell me
I'm building a course and template repo around exactly this, the real setup I run client apps and sites on right now, not a generic "learn to host websites" guide. I haven't built the full thing yet. I want to know if this is genuinely useful to people who are actually trying to do this before I spend months building it.
If you're thinking about turning client hosting into recurring revenue, or you're already doing it the one-VPS-per-client way and feeling the maintenance pile up, get on the list below. You'll get real build notes as I hit them, and a say in what it actually covers.