How I built a profitable SaaS web app: from idea to first sales
In this technical retrospective (2017), @mskvsk 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.
Out of interest, how did you work out that you could make $10,000 MRR?
CATEGORY Frugal Engineering →
HISTORICAL ERA Cloud & Mobile Era (2014–2019)
COMMUNITY SCORE ★ 16 points
TOTAL DISCUSSIONS 5 comments
This is my third tutorial on building a simple and profitable SaaS. As usual, I'm happy to answer any questions.
Thanks for reading!