Show HN: How I built my self-hosted private cloud
In this technical retrospective (2020), @resume384 shares practical architectural lessons learned from running, scaling, or migrating production software under lean constraints.
Core Principles for Independent Builders:
Defaulting to simpler architectures (such as monolithic frameworks, SQLite, or managed VPS) prevents early engineering bankruptcy.
Evaluating true compute and egress costs reveals that high cloud bills can often be slashed by 80%+ through judicious re-platforming.
Code you write at 2 AM as a solo engineer must be easy to debug six months later without complex microservice dependencies.
Community Debate Themes:
HN engineers debated the tradeoffs between cloud convenience and raw server economics, database indexing strategies, and resisting premature architectural complexity.
CATEGORY Frugal Engineering →
HISTORICAL ERA Pandemic Bubble (2020–2022)
COMMUNITY SCORE 4 points
TOTAL DISCUSSIONS 1 comments
I recently decided to make a simple hand built personal private multi-host capable cloud system. I'm really liking how things are going and would like input. What input does the hacker news community have for this project? The intent is to create a repository maintaining contemporary resources for handcrafting and maintaining in a manageable way a personal multi-host capable private cloud system that's accessible internally and externally. P.S. I've found similar projects I'd like to go over in more detail, many of which I looked into briefly but not found in them just what I'm going for, if you're interested in them there's a link to most at the bottom of the git readme. Thanks HN!