About
What
This series covers the practical process of running your own digital infrastructure. Not in theory, not in a lab that gets torn down afterwards, but for real, day to day, for yourself.
The things most people outsource to big tech without thinking about it and these are usually the kind of services that feel almost invisible until you start asking who actually owns the data behind them. However, these are all things you can run yourself. It takes more effort up front but it pays back over time.
- Documents and files
- Calendar and contacts
- Instant messaging
- VoIP
- Audio and video
- E-books
- Notes and tasks
- Bookmarks
- News feeds
- Blogs and websites
- Social networks
- P2P file sharing
All of the above can be made accessible from anywhere, and all of them synchronised across your devices. These are things you already get from the large internet companies, the cable providers, or the cloud hosters. It is possible run these services on hardware you own and software you control.
Why
You never lose control over your data. And everything is encrypted, both at rest and in transit.
That is the short version. The longer version is about trust, and what happens when you extend it uncritically to organisations whose incentives do not align with yours.
When your data lives on someone else’s infrastructure, you are operating under their terms of service, their security posture, their decisions about what gets retained, shared, or sold. Most of the time nothing bad happens. But you have no real visibility into any of it, and no meaningful recourse when something does go wrong. Rolling your own changes that relationship entirely. You become the person responsible, which is more work, but also means you are the person in control.
Encryption matters here too. Data encrypted at rest means that if a device is lost, stolen, or seized, the contents remain protected. Data encrypted in transit means what moves across the network stays between the intended parties. These are not paranoid concerns. They are just good hygiene, and the tools to achieve them are freely available and well documented.
How
Open source software, running on hardware you own. That is the foundation of everything in this series.
The specific tools change over time as better options emerge or old ones fall out of maintenance. What stays constant is the principle: prefer open source over proprietary, prefer self-hosted over cloud-hosted, prefer standards-based protocols over locked-in ecosystems. When you build on open standards, you retain the ability to swap components without starting over.
This series documents a real build. The network design section lays the groundwork. Everything after that builds on it incrementally. You can follow the whole thing from the beginning, or dip into individual sections as they become relevant to what you are working on. Either approach works.
The source material this series draws on most heavily is roll.urown.net, a comprehensive technical reference by Alain Wolf and contributors, licensed under CC BY-SA 4.0. Where that documentation is thorough and precise, this series aims to be readable and honest about the journey, including the parts where things did not go smoothly the first time.
The goal is a network you understand, built on software you trust, running data you actually own.