4 ms·

Thanks for sharing your thoughts! To clarify, this has already helped me to ship features to my customers quickly. I actually spend little time working on the

by amzans 6y ago

Thanks for sharing your thoughts! To clarify, this has already helped me to ship features to my customers quickly. I actually spend little time working on the stack. Last time I touched the infrastructure components was probably a few weeks ago. Panelbear was originally built and launched in a weekend ($5/mo DO instance with SQLite), and I've been working on it for the past 3 months. I have been releasing a new feature every week. That is, in addition to my full-time job, so most of the time we're talking about 2 hours per day tops. I'd also like to clarify that I am not suggesting this stack should be used by other solo founder SaaS. I actually advice against it in my post :) I just wanted to share my stack, as it has worked really well in my case, and I thought it'd be interesting material for discussion.

joshmn 6y ago
That's really great, happy to hear. I didn't mean to refute what you shared. In fact I was reinforcing some of your points. Doing things the cheap way is arguably the best way. Learning new tech while building is good, but I wouldn't recommend new tech to build a SaaS. My concern was copycats. Some starters reading your post may have this feeling that "because Panelbear did it with Clickhouse and Kubernetes and Django, that's the only way to do it." What it really should read is "because Panelbear used what he knew best, he was able to focus on getting customers; that's the only way to do it."
- amzans 6y ago
  > used what he knew best, he was able to focus on getting customers That's what I was going for :) Now I realize that I should have highlighted that part more on the blog post.