garden@josh — self-host.md

My personal self-hosting journey. Opinions, guides, criticisms, random thoughts, and everything in between.

# the cloud doesn't have to be a privacy nightmare or a $200/mo subscription for all eternity. take control of your data — once you start, you never go back.

Online·~/garden/self-host
[02services]
Chapter 01
Contrast
Chapter

First,
The realization.

As a self-proclaimed computer boy I have always been interested in technology. I remember the first time I could carry a computer in my pocket with the iPod Touch, and how magical that felt. I would daydream about the things I could do with it even before there was an official app store. Innovation and new developments in the tech sphere should, by nature, always feel this way. Technology should always be a key that opens the door and broadens the range of human creativity.

But for years, it wasn't.

Every new innovation — the cloud, voice assistants, AI, smart anything — came with the same deal underneath: you don't own the data, you don't own the account, you rent access on someone else's terms, and get spied on for your trouble. The features got better and the trade got worse, and after enough years of that I started seeing every announcement the same way. I could only see the potential downsides, and it was never exciting the way that first iPod was. "We can identify your friends in photos automatically!" was the exact stuff of my childhood day dreams, but now that it was here it felt more like a nightmare. "Innovation" had become synonymous with (personal) invasion.

If you are not paying for it, you're not the customer; you're the product being sold.

Because of this mentality I opted out of almost everything. No cloud photos. No smart speakers. No AI. My backup strategy was a folder of files I pulled off my phone every few months and hoped for the best. As someone who had always loved adopting and tinkering with new technology I found myself using less and less. I had integrated less technology into my daily life than the average Facebook Granny asking Alexa to set a 15 minute timer.

Then one day, and I can't even remember what inspired it, I did an online search for "Private Google Photos Alternative" and it all started to change.

The rack on day one
Immich — Self-hosted photo and video management solution

Because none of these new innovations are inherently a violation of your privacy or dystopian. Cloud storage that syncs your photos to every device is incredible. AI that picks faces out of a decade of pictures, or surfaces the one beach photo from 2017 when I type "beach", is genuinely magic. Voice control. Shared albums. Search across years of files. The features were never the problem, the ownership was, and giving up ownership was never actually required. Run the same software on hardware you own, on data you control, in a closet you can walk to, and everything changes. The AI rules are tweakable and transparent. The cloud is yours. The features that used to feel like traps are actually cool and useful time savers. The simple thought, the possibility, of these technologies existing but not as a part of Privacy Invasion Suite 2000 ™ re-sparked the excitement I had lost.

The technology was always fun, the magic was always there. Profiteering and exploitation had just been masking it.

Chapter

Then,
the hardware.

The realization was instantaneous but going full self host was going to be real work. It is simple enough to download and run Immich on a laptop, but as I delved deeper I learned that the gap between consumer and server hardware was wider then I thought. If I was going to take ownership of my data, I had to take ownership of the infrastructure too.

That meant a real server. Actual server hardware, built around the assumption that things break. Drives fail. RAM bit-flips. Power flickers. The cloud providers I'd spent years avoiding had teams of engineers and warehouses of redundancy hiding behind every "save" button. I needed a tiny version of the same idea, on my budget, but built with the same posture.

What real redundancy looks like.

ZFS for the filesystem — copy-on-write, end-to-end checksums on every block, scheduled scrubs that walk the entire pool and catch silent corruption before it creeps into your backups. Multiple drives in raidz2, so two of them can die and the data survives. ECC memory, because uncorrectable bit-flips in RAM corrupt the data before it ever hits disk. A UPS, so a flickering outlet doesn't take the pool down mid-write. Off-site backups to a second box, because a single roof is a single point of failure.

Chapter

Now,
the avalanche.

Here's what nobody tells you about building a NAS or home server infrastructure. You start with one goal. For me, it was photo backup, but then you quickly realize that one decently speced server for one person can do a hell of a lot more than just host photos.

As it turns out, there is an open-source, self-hostable version of basically every service I had forgone using — with a thriving, active, and passionate community to match. Calendar and contacts. Password manager. Notes. Music streaming. Movies and TV. Document management. Home automation. Identity. Monitoring. Git. Ad blocking. VPN. Each one is a docker compose file and an evening of fiddling. Made by people who felt the same way as me, and were making and keeping technology fun.

One real server is usually all it takes.

Since then, the list of tools and services I self-host is long and still growing. Some seem cool and useful at first but end up never being used. Some are no-brainers and have worked flawlessly since day one, and some are just plain bad. This page attempts to document the journey. What I love, what could use some work, where I could see this going, or any other random thoughts from my self-hosted journey.

The stack

What's running

The apps I've hosted, loved, and hated.