There is a line that circulates among people who work in security: there is no cloud, there is only somebody else’s computer.
It is a joke, and like most good jokes in the trade it is also a description. When you upload your photos, your passwords, your notes and your family’s documents, they do not go into the sky. They go onto a machine owned by a company, in a building you will never see, under terms you did not write and cannot negotiate, and the company can change those terms whenever it likes.
I have spent my working life in information security. For the last few years I have also run most of my own digital life on hardware I own, at home. This section is where I will write about that: self-hosting, privacy, and the part of AI that touches both. This first post is the argument for why I bother.
What you are actually handing over
Start with what an ordinary household puts in other people’s hands. Every photo of your children. Every password you have. Your notes, your calendar, your scanned passports and tax returns. Years of messages. In many cases, a precise record of everywhere you have been.
Each of those services is free or cheap because the arrangement works for the company. Sometimes the arrangement is simple: you pay a subscription and they store your files. Often it is not. The data is the product, or it trains the product, or it is simply an asset, and the terms that govern it are written to protect that asset rather than you.
Three things follow, and none of them require anyone to be malicious.
The terms can change. Several large services have rewritten their policies in recent years to let them use what their users store to train AI models. You were not asked in any meaningful sense. You were notified.
The account can close. People have lost access to entire accounts, email and photos and documents and years of their lives, because an automated system flagged something and there was no human to appeal to. When your data lives inside someone else’s account system, your access to your own memories depends on their moderation process.
The data can leak. Every large store of personal data is a target, and large stores get breached. Not because the engineers are careless; often they are very good. It is because a target that valuable attracts attackers who are very good too.
What changes when it is yours
Self-hosting means running those services yourself, on a machine you control: a password manager, a photo library, file sync, notes, a calendar, backups. The software is mostly free and open source. Much of it is excellent, and some of it is better than the commercial product it replaces.
What you gain is not magic security. A server in your house can be broken into too. What you gain is control over the three things above. The terms are yours. Nobody can close your account. And your data stops being one row in a database of hundreds of millions, which is worth an attacker’s year, and becomes one small target that nobody is looking for, behind defences you understand because you put them there.
There is a quieter benefit, and it is the one I did not expect. When you run a service yourself, you learn how it works. You find out what it actually needs to know about you, which is usually far less than the commercial version asks for.
The money
The cost argument is real, but it is easy to overstate, so let me do it properly.
Add up what you pay each month for cloud storage, photo backup, a password manager, notes, and anything else that exists to hold your own files. For many households it comes to somewhere between a few pounds and a few tens of pounds a month, every month, indefinitely, at a price someone else sets.
Against that, a self-hosted setup has two costs. The first is hardware, paid once. A small, low-power computer and a couple of drives will run a household’s services comfortably, and it does not need to be new.
The second is electricity, and here is the arithmetic so you can check it against your own tariff. A small machine idling at around 10 watts uses 10 × 24 × 365 = 87.6 kilowatt-hours a year. At around 25p per kilowatt-hour, that is roughly £22 a year. Double it for a bigger machine with spinning disks and it is still less than many people pay for a single cloud subscription over a few months.
So in most cases the hardware pays for itself within a couple of years, and after that the running cost is a small electricity bill and your time.
Which brings me to the part most self-hosting advocates skip.
What it honestly costs
Your time is the real price, and it is not trivial.
When you host it yourself, you are the operations team. You apply the updates, or you automate them and then check the automation is working. You design the backups, and you test them, because a backup you have never restored is a hope rather than a backup. I learned that one directly: my own backups once failed silently for three nights running, and I only found out because I went looking. Nobody sends you an alert unless you built the thing that sends it.
You also carry the security responsibility. Put a service on the internet carelessly and you have created exactly the exposure you were trying to escape. Much of what I will write here is about doing that part properly: reaching your services without opening ports on your router, keeping them patched, and knowing precisely what you have exposed.
And some things are not worth hosting at all. Running your own email server is the classic example. It can be done, but getting your messages into other people’s inboxes is a permanent fight with spam filters, and a mistake means your mail quietly disappears. I host a great deal. I do not host that.
So the honest version of the claim behind this post is narrower than the enthusiasts make it. For most of what a household stores, self-hosting is the better option for privacy and, over a couple of years, for cost. It is not free, it is not effortless, and it is not for everything.
Why I think it is worth it anyway
My other writing, mostly about books and civilisation, keeps returning to one idea: that the things in our care are held in trust rather than owned. It sounds like an odd idea to bring to a hard drive. I think it fits here better than almost anywhere.
The photos of your children, your family’s documents, the record of a life: these are things you hold on behalf of other people. Handing them to a company whose business depends on them is not neglect, exactly. But it is passing a responsibility to someone whose interests are different from yours. Self-hosting is taking that responsibility back.
What this section will cover
Practical posts on running services at home safely: what I use, why, and where I got it wrong. Privacy beyond self-hosting: what leaks from ordinary life, and what can realistically be done about it. And AI, particularly whether you can have the benefits of these tools without sending everything you type to somebody else’s computer. Increasingly, you can.
Details will be honest and specifics anonymised. Addresses and names in the examples here will be placeholders, for the same reason this section exists at all.