Two Months with a DIY NAS: A Complete Journey from Hardware Selection to Private Cloud Deployment

Why More People Are Choosing to Build Their Own NAS Servers

As streaming subscription services become increasingly fragmented, more and more tech enthusiasts are turning to self-hosting solutions. Self-hosting refers to deploying and running services on your own hardware rather than relying on third-party cloud platforms — a concept closely tied to the growing "data sovereignty" movement. According to 2024 market data, there are already over 10 major streaming platforms in the US alone (Netflix, Disney+, HBO Max, Hulu, Amazon Prime Video, Apple TV+, Peacock, Paramount+, etc.), and subscribing to all of them can easily cost over $100 per month. This "Subscription Fatigue" has directly fueled demand for DIY media servers. Recently, a Reddit user shared their complete experience after two months of using a UGREEN NAS, sparking widespread resonance in the community.

This user's core motivation for going the self-hosting route is quite representative: fragmented content across streaming platforms and regional restrictions. Many popular shows bounce between different platforms, and even subscribing to multiple services doesn't guarantee access to the content you want. When using a VPN (they chose ProtonVPN) to bypass regional restrictions, users get caught in a cat-and-mouse game with the platforms — streaming services actively detect and block VPN connections.

ProtonVPN is a VPN service developed by Swiss company Proton AG, known for its strong privacy protections. Its parent company also operates the encrypted email service ProtonMail. VPNs work by establishing an encrypted tunnel between the user's device and the VPN server, making traffic appear to originate from the VPN server's geographic location. However, due to geographically restricted content licensing, streaming platforms employ various techniques to detect and block VPN connections, including IP reputation databases (identifying known VPN server IP ranges), DNS leak detection, WebRTC leak detection, and more advanced Deep Packet Inspection (DPI) technology — making it increasingly unreliable to watch cross-region content via VPN.

Ultimately, they chose a NAS (Network Attached Storage) to solve the problem once and for all. A NAS is a dedicated file-level storage device that provides centralized data access to devices on a local network. Unlike external hard drives connected directly to a computer, a NAS has its own operating system and processor, can run 24/7, and serves multiple devices simultaneously. With a self-hosted media server, users can centrally manage media content locally, access it anytime and anywhere, free from platform restrictions while maintaining full control over their data.

NAS Hardware Selection: UGREEN vs. Terramaster

When it came to choosing a NAS brand, this user deliberated at length between UGREEN and Terramaster, ultimately going with the UGREEN 4800+ model. The UGREEN 4800+ features an Intel N100 processor (4 cores/4 threads, up to 3.4GHz), supports 4 drive bays and 2 M.2 NVMe slots, and runs UGOS Pro, a Linux-based operating system. The Intel N100 is based on the Alder Lake-N architecture with a TDP of just 6W, but it integrates Intel UHD graphics with AV1 hardware decoding support — a critical feature for video transcoding on a media server.

The traditional NAS market has long been dominated by Synology and QNAP. Synology is known for its mature software ecosystem and system stability, but its hardware specs tend to be conservative with higher price premiums. QNAP offers more aggressive hardware specifications, though its software experience has been debated. UGREEN was originally a consumer electronics accessories manufacturer that officially entered the NAS market in 2023, leveraging its supply chain advantages to offer cost-effective hardware. Terramaster is a long-established NAS manufacturer based in Shenzhen, with product lines spanning home to enterprise use. The key difference between the two: UGREEN's UGOS Pro has a more modern interface and better Docker support, but its ecosystem isn't as mature as Terramaster's TOS system. That said, Terramaster has faced some scrutiny recently due to security vulnerabilities (a remote code execution vulnerability in TOS exposed in 2024).

Here's the specific configuration:

• Storage drives: 2× 10TB Seagate IronWolf HDDs in a RAID 1 array
• Memory: 2× 8GB 5600MHz RAM, totaling 16GB
• Cache drive: 1× 450GB Kingston NV3 NVMe SSD

The Seagate IronWolf series is specifically designed for NAS environments and differs from regular desktop hard drives in several key ways: it uses CMR (Conventional Magnetic Recording) technology rather than SMR (Shingled Magnetic Recording), ensuring no performance drops during sustained writes in RAID arrays; AgileArray technology optimizes vibration compensation (RV sensors) for multi-bay environments, reducing interference when multiple drives operate simultaneously; the rated workload is 180TB/year with an MTBF (Mean Time Between Failures) of 1 million hours. The 10TB version uses helium-sealed technology, spins at 7200RPM, and delivers sustained transfer rates of approximately 210MB/s. Comparable alternatives include Western Digital's Red Plus series and Toshiba's N300 series.

This configuration is well-balanced for personal self-hosting scenarios. RAID 1's mirroring mode means the two 10TB drives back each other up, with actual usable capacity of 10TB — a wise choice that sacrifices half the capacity for data redundancy, which is absolutely worthwhile for users storing valuable media libraries and personal files.

RAID (Redundant Array of Independent Disks) is a technology that combines multiple physical drives into a logical unit, first proposed by UC Berkeley in 1988. Common RAID levels include: RAID 0 (striping, doubled performance but no redundancy), RAID 1 (mirroring, complete backup), RAID 5 (distributed parity, requiring at least 3 drives), RAID 6 (double parity), and more. RAID 1 is the simplest redundancy scheme: two drives write identical data in real time, so if either fails, the other continues operating independently, and the array automatically rebuilds after inserting a replacement drive. The downsides are only 50% disk utilization and no write performance improvement (though read performance can theoretically double since different data blocks can be read from both drives simultaneously). For NAS units with 4 or more bays, RAID 5 is typically a more economical choice, sacrificing only one drive's worth of capacity to provide single-drive failure protection.

The Role of the NVMe SSD Cache Drive

You might have noticed that the user also added an NVMe SSD. NVMe (Non-Volatile Memory Express) is a communication protocol designed specifically for flash storage that communicates directly with the CPU via the PCIe bus, achieving latencies as low as microseconds — far superior to traditional SATA-interface SSDs. The Kingston NV3 is an entry-level PCIe Gen 4x4 NVMe SSD with sequential read speeds up to 6000MB/s.

In a NAS system, SSDs typically serve as cache or as the installation location for applications. SSD caching generally operates in two modes: Read Cache stores copies of frequently accessed data on the SSD to accelerate reads; Read-Write Cache accelerates both read and write operations but requires two mirrored SSDs to prevent data loss. Mechanical hard drives excel at high-capacity, low-cost storage but have limited random read/write performance (seek latency typically 8-12ms), while NVMe SSDs can deliver random IOPS in the hundreds of thousands, significantly improving system responsiveness, Docker container performance, and metadata retrieval speed. Many users install Docker containers, database files, and applications directly on the SSD — the experience improvement is especially noticeable when running multiple self-hosted applications simultaneously.

The Self-Hosted App Ecosystem: Infinite Possibilities from a Single NAS

Although the original post didn't list every deployed application, the user's description of "running multiple apps and loving it" highlights that modern NAS devices have far transcended simple file storage, evolving into complete private cloud platforms. The key technology behind this is Docker containerization — Docker is an OS-level virtualization technology that packages applications and all their dependencies into standardized "containers." Unlike traditional virtual machines, Docker containers share the host's Linux kernel, start almost instantly (in seconds), and consume minimal resources, allowing users to run dozens of isolated applications simultaneously on the same device. Docker Compose allows defining and managing the orchestration of multiple containers through a single YAML configuration file, and UGOS Pro natively integrates a Docker management interface, enabling users unfamiliar with command-line operations to deploy containerized applications through a graphical interface.

For users whose primary goal is media streaming, a typical self-hosted application stack usually includes:

• Media server: Such as Jellyfin, Plex, or Emby, for organizing and streaming local media libraries. Plex is the most established commercial product with the most complete client ecosystem; some advanced features require purchasing Plex Pass (approximately $120 lifetime). Emby started as an open-source Plex alternative but later adopted a partially closed-source freemium model. Jellyfin is a fully open-source, completely free project forked from Emby version 3.5, driven by community development. Video transcoding is a core media server function — when a client doesn't support the original video encoding format or network bandwidth is insufficient, the server needs to convert video to a compatible format in real time. The Intel N100's Quick Sync video engine can efficiently handle hardware transcoding for H.264/H.265/AV1, dramatically reducing CPU load.

• Downloads and content management: Tools like qBittorrent, Sonarr, Radarr, and other automation utilities. These belong to the so-called "Arr family" of automated media management tools: Sonarr focuses on TV series management, automatically monitoring RSS feeds, matching quality preferences, sending download tasks, and automatically renaming and organizing files upon completion; Radarr performs the same automated workflow for movies; Prowlarr manages indexers centrally; Bazarr automatically downloads matching subtitles; Lidarr manages music; Readarr manages e-books. All these tools are deployed via Docker containers and communicate with each other through APIs, forming a highly automated media acquisition and management pipeline. qBittorrent is an open-source BitTorrent client that supports Web UI remote management and is one of the most popular download tools for self-hosting scenarios.

• Networking and security: A reverse proxy is a critical component in self-hosted server network architecture, with popular tools including Nginx Proxy Manager, Traefik, and Caddy. All external access requests first reach the reverse proxy server, which forwards them to the corresponding internal service containers based on domain name or path rules, while centrally managing HTTPS certificates (obtained automatically for free through Let's Encrypt), hiding the real ports and IPs of internal services. For DNS-level ad filtering, Pi-hole is a network-wide ad blocker that operates as the LAN's DNS server, resolving known ad domains and tracker domains to a black hole address (0.0.0.0), providing an ad-free experience for all devices without installing ad-blocking plugins on each one. Its alternative, AdGuard Home, additionally supports DNS-over-HTTPS/TLS encrypted queries.

• Personal cloud storage: Such as Nextcloud, replacing commercial cloud storage services. Nextcloud is currently the most mature open-source private cloud platform, with functionality far beyond file syncing: including calendars, contacts, online document collaboration (integrated with OnlyOffice or Collabora Online), video conferencing (Nextcloud Talk), and kanban task management. It provides cross-platform clients and supports selective sync, version history, file encryption, and shared links. When deployed on a NAS via Docker, it's typically paired with MariaDB/PostgreSQL databases and Redis caching for optimal performance. Compared to commercial services like Baidu Netdisk or iCloud, Nextcloud's core advantage is that data is stored entirely on the user's own hardware, with no risk of censorship, throttling, or privacy breaches.

This "invest once, use forever" model is the core appeal of self-hosting. Users no longer need to pay monthly fees for each service, nor worry about content being removed or accounts being banned.

The Core Value and Entry Barrier of Self-Hosted NAS Servers

This user's feedback of "still loving it after two months" reflects a genuine trend in the self-hosting community: more and more ordinary users are transitioning from being pure consumers to becoming managers of their own data.

From a value perspective, self-hosting delivers three key benefits:

• Data sovereignty: Content is entirely yours, unaffected by platform takedowns or regional restrictions
• Cost control: A one-time hardware investment replaces ongoing subscription fees
• Full customization: Install whatever applications you want, built entirely to your needs

That said, it's important to be realistic about the barriers. Compared to plug-and-play streaming subscriptions, self-hosting requires a certain level of technical knowledge: understanding RAID concepts, configuring Docker containers, managing network ports and security policies, etc. While newer brands like UGREEN have significantly lowered the difficulty curve through graphical interfaces, truly mastering it still requires an investment of learning time.

Final Thoughts: A Beginner's Guide to Self-Hosted NAS

This Reddit post is a microcosm of the broader "de-subscription" wave. As streaming platforms become increasingly fragmented and geo-blocking grows more restrictive, a well-configured NAS is becoming an effective way for tech enthusiasts to reclaim control over their content.

For readers considering taking the plunge into self-hosting, this case study provides a practical reference: choose a model with at least two bays that supports RAID, add SSD caching to improve the experience, and most importantly — clarify your core needs (whether it's media streaming, private cloud, or home automation) before planning your hardware and software setup.