Self-Hosting Lessons: The Cost of Underpowered Hardware

Starting a self-hosted infrastructure often involves troubleshooting, unexpected downtime, and services that don’t always function as expected. A recent experience highlighted the limitations of attempting to run too many services on underpowered hardware, specifically a Synology NAS with only 2GB of RAM.

The decision to use existing hardware is common among those starting to self-host, often driven by cost considerations. In regions like South Africa, electronics import taxes and limited local manufacturing inflate prices, making even refurbished mini PCs costly. The author, facing these financial constraints, began with a main PC and later utilized a NAS, originally a review device, to host key services. While initially successful, the 2GB RAM limitation proved restrictive, prompting careful selection of services and the avoidance of resource-intensive applications like Large Language Models (LLMs).

However, deploying Paperless-ngx, a document management application, revealed the device’s shortcomings. Initially smooth, the Paperless-ngx container eventually crashed repeatedly, triggering a cascade of failures affecting other containers and rendering the NAS unusable. The root cause was resource overload, likely stemming from the OCR and AI tagging features within Paperless-ngx struggling with multiple document uploads. The author has since moved Paperless-ngx to their main PC with more substantial resources. To prevent future issues, a RAM usage warning has been implemented on the NAS.

This experience reinforces a critical lesson: while self-hosting offers significant benefits, carefully assessing hardware capabilities and understanding the resource demands of individual services is essential for a stable and reliable infrastructure. Some limitations can only be learned through practical experience.