Home Server: Why?

Running a personal server, a physical one, at home, to serve content over the Internet, sounds like an antiquated idea. Over the last 15 years we have virtualised and commoditised everything to do with sharing stuff on the web: Flickr, then Instagram for photos, Github for code, Medium for blog posts, LinkedIn for CVs, and so on and so forth. Even if one wanted to set up and maintain a server, AWS, GCP, DigitalOcean and countless other cloud platforms are happy to provide a virtual one for a few dollars a month.

Choosing to run one’s own isn’t an obvious choice, but there are a few reasons why you might want to consider that:

It is really convenient to have others manage your data, worry about the availability, the backups, publishing. It’s sensible to pay someone to do it, and use your time for something more rewarding. Even better, a lot of services will happily manage your data for free! But is it really free? There’s the obvious angle of serving us “relevant” ads, but the consequences of ceding the processing of our data to opaque systems designed to maximise the profit for their creators is that we might be sacrificing much more than our attention. The recent AI craze is one example: our data ends up in the training sets of various machine learning models, something we might not have knowingly assented to, and that could lead to loss of privacy or income. More generally, we are still like a primitive tribe that does not understand that land (information, in our case) can be valuable, and the value and artifacts derived from it might be out of our control. Keeping the data on our devices and controlling what is shared can help mitigate these risks.