Hetzner Considered Hostile: A PSA
In this technical retrospective (2024), @ggpsv 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 Post-ZIRP & AI (2023–2026)
COMMUNITY SCORE 6 points
TOTAL DISCUSSIONS 5 comments
And yet writes up a blog post that clearly explains that their porn was on S3, not Hetzner. Sounds like the report was accurate. But it makes me wonder what the result would have been had they taken the time to have that conversation to begin with.
How can OP be so sure that this is actual hostile behavior rather than an honest mistake on Hetzner's side?
Sure, they could have made a DNS lookup to avoid that misunderstanding. However, who knows the volume of tickets their support people are dealing with.
From that single incident alone, I'm not entirely convinced about Hetzner being hostile.