Self-Hosting Isn't About the Cloud. It's About Learning.
Why I self-host some services but not everything — and why curiosity is a better reason than ideology.
I don't believe the cloud is bad. I use plenty of commercial services myself — and I have no intention of stopping.
But I do self-host a growing number of services on a Raspberry Pi 5 running in my home. And the reason comes down to two things: independence and curiosity.
Independence from Big Tech
We've become accustomed to having a company provide almost everything for us.
File storage, email, password managers, remote access, calendar sync, photo backup — there is almost certainly a subscription for all of it. And honestly, that's incredibly convenient.
But convenience comes with a trade-off.
When someone else operates the infrastructure, they ultimately control the service. They decide how it works, what features are available, how much it costs, and what happens when they decide to change or discontinue it.
Self-hosting gives me another option. Not independence from Big Tech entirely — that's neither realistic nor the goal. Just the option to not be dependent on them for everything.
Curiosity Is the Better Reason
The second reason is probably the more important one.
When I use a cloud service, I don't have to think about what's happening underneath it. I log in, click a button, and it works.
Self-hosting removes that abstraction.
Suddenly I'm responsible for DNS, networking, authentication, certificates, storage, backups, security, and monitoring. And that's where things get interesting.
You start realizing that the "cloud" isn't magic.
It's computers. It's networking. It's containers and virtual machines. It's authentication systems, firewalls, backups, and automation.
A homelab isn't going to replicate Google's infrastructure — but the fundamental concepts are exactly the same. When I deploy a service at home, I'm getting a small-scale look at the same problems that professional IT environments solve every day.
Self-Hosting Is an IT Education
The biggest benefit I've gotten from self-hosting isn't the services themselves. It's everything I've learned while trying to make them work.
You don't just learn how to install an application. You learn why it works.
Maybe you need to create a DNS record — and suddenly you understand why DNS exists. Maybe you want HTTPS — now you're learning about certificates. Maybe you want remote access — now you're dealing with VPNs, firewalls, and authentication. Maybe your server dies — now you're thinking about backups.
One thing leads to another.
That cascading learning process is actually why this site exists. Most of the guides here started as personal notes — I was figuring something out, got it working, and wrote it down so I wouldn't have to start over six months later. The Raspberry Pi 5 home server series is a good example of that: a project that started as a homelab experiment and turned into a multi-part guide covering Docker, VPNs, remote access, and half a dozen self-hosted services.
Self-hosting has a way of turning "I wonder how that works?" into an actual IT lesson.
Control Means Responsibility
Despite everything I've said, I don't self-host everything — and I don't think you should either.
Running your own services means accepting responsibility for them. If a commercial service goes down, someone else fixes it. If my self-hosted service goes down, I fix it. If something needs updating, backing up, or securing — that's on me.
Self-hosting gives you control. But control and responsibility come together.
My approach is a hybrid. Some things I prefer to self-host because I want the control or the learning experience. Other things I leave to commercial services because they're more reliable, cheaper, or simply not worth the maintenance overhead.
That's a perfectly valid approach — and probably the most honest one.
The Cloud Isn't the Enemy
I think self-hosting is most valuable not as an ideological stance but as an education.
Once you've operated your own services, you start looking at cloud services differently. When a provider says something is "highly available," you have some idea of what that actually means. When a service offers automatic backups, you think about where those backups are stored and how they'd actually be restored. When something works effortlessly, you appreciate how much engineering goes into making it feel effortless.
That's the real value of self-hosting.
Not replacing the cloud. Not proving a point.
Just understanding what happens when you stop letting someone else do all the work.
If you want to try it yourself, you don't need a rack or a datacenter. Start with one service. Set it up. Break it. Fix it. Figure out why it broke. Back it up. Secure it.
You'll probably learn far more than you expected.