HomeLab Infra: Building a Private Cloud from Proxmox to TrueNAS Scale

Published on December 20, 20254 min read read
Share:

Introduction

In the world of software engineering, the classic question is "Build vs. Buy."

When it comes to managing our digital lives—storing terabytes of photos, documents, and videos—we face this exact choice. Should we keep paying monthly fees for services like Google Drive, OneDrive, or iCloud? Or should we build our own solution?

As a Computer Science Master's student, facing rising subscription costs on a limited budget, relying on SaaS wasn't sustainable. Naturally, the alternative seemed to be buying an off-the-shelf NAS like Synology or QNAP. However, I chose a different path: repurposing my existing workstation hardware.

By building instead of buying, I avoided the "black box" nature of proprietary OS interfaces. This project isn't just about saving money; it is a HomeLab designed to translate academic theories—virtualization, container orchestration, and storage management—into practical, production-grade experience. This post breaks down how I engineered a TrueNAS Scale based private cloud with High Reliability, Tiered Storage, and DevOps principles using consumer-grade hardware.

1. Technical Decision: The Shift from Proxmox VE to TrueNAS Scale

This migration wasn't a spur-of-the-moment decision. For over a year, I had architected and actively maintained a Proxmox VE environment as my daily driver.

However, my setup was fragmented, consisting of multiple Virtual Machines (VMs) connected via a standard Linux Bridge.

(▲ Legacy Architecture: Direct IP exposure, manual configs, and high VM overhead.)

As illustrated above, despite serving me for a year, this architecture had significant drawbacks:

  • Security Risks: No WAF protection; residential IP directly exposed via GoDaddy DNS.
  • Management Overhead: Manually maintaining nginx.conf and patching 4 separate Guest OS kernels.
  • Resource Waste: High CPU/RAM overhead from running multiple full-blown VMs instead of lightweight containers.

I realized I needed a system that prioritized Storage Stability and Efficiency, leading to the migration to TrueNAS Scale.


2. Hardware Architecture & Resource Provisioning

To handle mixed workloads—database I/O, large file storage, and concurrent container execution—I moved away from the "just enough" mentality and adopted a Workstation-grade configuration.

Crucially, I implemented a strict Tiered Storage Strategy:

ComponentSpecificationArchitectural Reasoning
CPUi9-1090010 Cores / 20 Threads. High concurrency headroom for containers & DBs.
RAM64GB DDR4ZFS Optimization. Maximizes RAM caching to minimize HDD read latency.
Boot DriveNVMe SSDOS Isolation. Separates system logs/updates from App I/O.
App DriveSATA SSDHigh IOPS Tier. Dedicated pool for random R/W (Docker/PostgreSQL).
Data Drive4TB HDD x 2Throughput Tier. RAID 1 Mirror prioritization for cold storage safety.

(▲ ZFS Storage Architecture: Logical isolation of Boot, Apps, and Data pools.)

⚡ Power Efficiency Note: Despite utilizing a workstation-class Intel Core i9, the system maintains a remarkably low baseline power consumption of 28–31W. This demonstrates that with proper power management, high-performance hardware can still be highly energy-efficient for 24/7 HomeLab operation.


3. Network Topology & Microservices Orchestration

The core value of this private cloud lies in its ability to securely deliver multiple services to the public internet, effectively breaking free from expensive Big Tech ecosystems.

To secure these services, I transformed the network topology to a "Single Entry Point, Reverse Proxy" architecture.

(▲ Modern Architecture: Secured flow via Cloudflare WAF -> NPM SSL -> Docker Containers.)

Key Architectural Improvements

  1. Edge Security (Cloudflare):
    • Acts as a shield (WAF). Masks residential IP and filters malicious traffic (DDoS/SQLi) at the edge.
  2. Gateway Layer (Nginx Proxy Manager):
    • Replaces manual config files. NPM handles SSL Termination and auto-renews Let's Encrypt certificates.
  3. Container Efficiency:
    • Services run as lightweight Docker containers sharing the host kernel, significantly reducing resource overhead compared to legacy VMs.

Microservices Stack

I deployed a comprehensive stack to regain full digital sovereignty:

  • Nextcloud: Alternative to Google Drive, OneDrive, and iCloud.
  • OnlyOffice: Alternative to Google Workspace (Docs, Sheets, Slides) and Microsoft 365 (Word, Excel, PowerPoint).
  • Immich: Alternative to Google Photos and iCloud Photos.

(▲ Production Dashboard: The container fleet running on TrueNAS Scale. Note the minimal resource footprint—CPU idles near 0% even with 4 active services.)

📂 Nextcloud and OnlyOffice Live Demo

📂 Immich Live Demo


Conclusion

This TrueNAS Scale infrastructure is more than just a storage server; it is a platform demonstrating Full-Stack Infrastructure capabilities.

From hardware assembly and ZFS tuning to container orchestration and network security, every layer required deep system understanding. Through this HomeLab, I have been able to validate DevOps theories in a production-like environment, continuously refining my skills in System Administration and Architecture Design.

Future Roadmap:

  • Implement Prometheus + Grafana for centralized metrics and alerting.
  • Transition manual configurations to Ansible for Infrastructure as Code (IaC) management.

Leave a comment via GitHub (Giscus). Sign in with GitHub to post.