How We built a $1M ARR open source SaaS
In this technical retrospective (2022), @caust1c 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 ★ 522 points
TOTAL DISCUSSIONS 106 comments
Since reading the thread on money-making side hustles on HN a few days back[1], I was able to finally brush off my procrastination and start twiddling with some of my side projects that have been lying dormant over the years! And the model Plausible uses (I think the right term is "Open Core"?) which is also used by the incredible Product analytics tool Posthog [1] aligns really well with how I want to build out my side-hustles. Open source, but also available packaged and hosted if you so prefer.
One thing I was concerned about was about revenue that these "open source by default" products make, so glad that this post has come along just in time to alleviate some of those concerns (of course, as with most engineering side projects, the priority is to build something cool first, and if it ends up making some money, then all the better!) and it's always nice to see successful OSS-driven products in a crowded analytics space.
Congrats folks!
[1] https://news.ycombinator.com/item?id=31764696
[2] https://posthog.com/
All their marketing seems to be pitching the product against Google Analytics. But they don't spend any time differentiating themselves from other privacy-first analytics companies, of which there are many.
I mean, when they started in 2018:
Surely they must have looked around and seen that there were already quite a few products doing privacy-first analytics? But yet they started anyway? And had success even though their marketing doesn't really state any reasons why the user should use them not the many other privacy-first analytics offerings out there?
I mean I'm happy for them that they're successful, but I think there must be more to it than alluded to in this blog post, both in (a) the decision to start in the face of lots of competition and (b) success despite not trying to differentiate themselves from the competition.
I like Plausible, and ethical analytics services in general. I'd certainly use them over Google Analytics. But it does frustrate me that Plausible (and others) take the stance that because they are doing what they can to preserve privacy, they have an absolute right to collect telemetry about users.
This includes things like CNAME cloaking, and adding a local JS proxy script so that visits can be sent back to Plausible's servers to make it harder to block for the user. The user has expressed a clear preference for their visits not to be logged, and Plausible (to satisfy site owners who want every visit logged) have done whatever they can to circumvent that.
I get it - it's a business, and making sure the site owners are happy is a big part of making money. But it grates that the whole thing is supposed to be about privacy while ways to get around privacy preferences are baked in.
I use plausible analytics to measure traffic on my observable notebooks. I did try with GA but it didn't work with Observable's iframe sandboxing. Because plausible is open source, I could fiddle with it a little and could get it to report the top level page user facing URLs instead of the iframe's. Very happy I can get traffic stats from a site I don't own and very happy I don't need user consent because it's GFPR compliant. It tracks just what I am interested... My traffic, and with a little config it excludes my own page views. Great product, perfect for my use case I wish them well.
https://observablehq.com/@endpointservices/plausible-analytics
“We’re intentionally small, profitable and sustainable.”
This here ^^. Too many fall in the trap of agiling themselves to death. Instead, find the right people with the right skills and dont force process. Communicate well and frequently and you’ve got yourself a well oiled team. Current client has successfully managed to daily, retro and refine themselves to a drop in productivity by at least 20%. My invoices are coming in nicely, despite wasting days on meetings that could have been an email or a short call with the relevant stakeholders, but i’ll fire the client first chance i find one that actually wants me to work and not play “fun” t-shirt planning pokers.