All research

Network Attached Storage — Hardware + Software Prototyping

Topics

Hardware
Linux
Networking
Golang
Self-hosted
Network Attached Storage — Hardware + Software Prototyping — image 1
Network Attached Storage — Hardware + Software Prototyping — image 2
Network Attached Storage — Hardware + Software Prototyping — image 3
Network Attached Storage — Hardware + Software Prototyping — image 4

A self-hosted NAS built from commodity hardware — the goal was to understand the full stack from raw disks to a usable remote file access interface, and to document the build for others who want to escape cloud storage costs.

Hardware

Selected low-power ARM-based hardware for the compute layer, paired with commodity HDDs in a software RAID-1 configuration for redundancy. The build prioritised low idle power draw and silent operation over raw throughput.

Software Stack

  • **OS**: Linux (Debian-based) with a minimal headless server configuration
  • **RAID**: mdadm software RAID-1 for drive redundancy
  • **File sharing**: Samba for Windows/macOS SMB access; NFS for Linux clients
  • **Remote access**: WireGuard VPN for secure remote access without exposing the NAS to the public internet
  • **Web interface**: Custom lightweight REST API in Golang for file browsing, upload, and download; minimal HTML/JS frontend
  • **Monitoring**: Integrated with ArgonWatchGO for uptime and disk health alerts

Custom REST API

Rather than using existing NAS software (TrueNAS, OpenMediaVault), I built a minimal Golang API for file operations. This gave full control over the access model — per-user permissions, audit logging, and integration with other self-hosted tools.

Outcome

A working self-hosted NAS running continuously on local hardware. All personal files, project backups, and media are served from this device. Total cost: significantly less than equivalent cloud storage over a 3-year horizon.

The build is documented for community reference.