What a year of self-hosting taught me about the cloud

A year ago I did something mildly ridiculous. I bought a small, low-power computer, put it on a shelf in a closet, and started moving my digital life onto it — files, photos, calendar, notes, the lot — off the convenient platforms that had hosted them for years. People who self-host will tell you it is about privacy or control or sticking it to the big companies. After twelve months, I think the real lessons were quieter and more surprising than any of that.

The first lesson: convenience has a price you stop seeing

The big platforms are genuinely, almost magically convenient. Everything syncs, everything is backed up, everything just works, and you pay for it with money and data in amounts you long ago stopped noticing. Running my own version of the same services made that bill visible again. Not because self-hosting is expensive — it is cheap once it runs — but because I suddenly had to think about backups, updates, and storage as real things rather than someone else's invisible problem.

That visibility turned out to be the point. I was not paying less; I was paying attention. And paying attention changed how much I kept, how I organized it, and how casually I uploaded things I would never look at again.

The cloud is not someone else's computer. It is someone else's problem — until the day it quietly becomes yours again.

— a note I left for myself, month three

The second lesson: reliability is a feature you are buying, not a fact

When my closet box went down — and it did, twice — there was no status page to refresh and no support to blame. There was just me, a flashlight, and the dawning understanding of exactly how much engineering I had been taking for granted. The big platforms make uptime look like a law of nature. It is not. It is a vast, expensive, ongoing effort, and running even a tiny piece of it yourself gives you a lasting respect for the people who do it at scale.

The third lesson: most of it was simpler than the fear suggested

The thing that keeps most people from trying is the image of a sprawling, fragile setup that demands constant attention. The reality, for a modest personal setup, was closer to a houseplant than a server farm.

• The hardware was a single small machine that sips power and makes no noise.
• The software was a handful of well-documented, open-source apps that have had years to mature.
• The maintenance settled into a calm rhythm of occasional updates, not a daily firefight.

I am not going to pretend it is for everyone. If something breaks, you are the help desk, and there are weekends when that is exactly the chore it sounds like. But the difficulty curve is front-loaded. The first month is genuinely fiddly; the eleven that follow are mostly quiet.

What I actually kept, and what I let go

The honest ending is that I did not leave the cloud entirely, and I no longer think that should be the goal. I kept the central services for the things where scale and reliability genuinely matter, and I moved home the things that are personal, sensitive, or simply mine — the photos, the documents, the notes I would hate to lose to a policy change I never agreed to.

The lesson was not that the cloud is bad. It was that "the cloud" had quietly become the default answer to questions I had never actually asked. Self-hosting did not make me an ideologue. It made me deliberate. A year on, I keep things in the cloud on purpose, keep things at home on purpose, and the difference between those two sentences is the whole point.