Infrastructure · Self-hosted
A laptop that became a small data centre
I turned an old laptop into a Debian server that centralises my files, photos and media on one machine I control, reachable from any of my devices through a private network.
Architecture
From any device to the right service
Hover or tab through the nodes. Addresses, hostnames and credentials are intentionally left out.
Scroll sideways to see the full diagram →
Debian 13 server
AMD Ryzen 7 3700U (4C/8T), Radeon Vega 10, 8 GB RAM. A 2020 laptop repurposed as an always-on, low-power machine.
Hardware
Modest hardware, used deliberately
A mobile CPU and 8 GB of RAM are enough for file serving and media streaming, while drawing far less power than a desktop running all day.
- Machine
- Huawei MateBook D 15 (2020)
- CPU
- AMD Ryzen 7 3700U · 4 cores / 8 threads
- Graphics
- Radeon Vega 10 (integrated)
- Memory
- 8 GB RAM
- System disk
- 512 GB NVMe SSD
- Data disk
- Toshiba Canvio Basics 4 TB (external HDD)
- OS
- Debian 13
System
Storage, services and access
Storage architecture
The internal NVMe holds the operating system and service data. The 4 TB external drive holds the bulk of the library: photos, videos, films, series, music and documents. Separating the two keeps the system disk small and the media easy to move or back up.
Services
Jellyfin organises and streams films and series. Navidrome streams the music library and speaks the Subsonic API, so it works with mobile clients such as Substreamer. Personal files live alongside them on the same drive.
Remote access
Tailscale creates an encrypted WireGuard network between my devices and the server. Services are reachable from outside home without opening router ports or exposing anything publicly.
Challenges
What it takes to keep it running
Design constraints that come with the setup itself:
- A laptop is not designed to run 24/7: power management, lid behaviour and heat have to be configured for an always-on role.
- Bulk data on an external USB drive needs reliable mounting at boot so services never start against an empty path.
- 8 GB of RAM sets a budget: services have to coexist without competing for memory.
- Remote access has to be convenient enough to use daily without weakening security.