What One-person SaaS Healthchecks.io uses for hosting, hardware and software
blog.healthchecks.io
What One-person SaaS Healthchecks.io uses for hosting, hardware and software
1–10 of 180 posts
Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software
#2This is such a great blog post. Succinct and to the point. Read it from start to finish without pause even though the stack used (which is great!) is only remotely applicable to my workflow.
Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software
#3How much does it all cost?
Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software
#4How much does it all cost?
No post body was provided.
Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software
#5How much does it all cost?
[deleted]
Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software
#6How much does it all cost?
Hi, the author of the blog post here. I don't have a precise number, but somewhere in the €800/mo region.
Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software
#7I'm someone who likes configuring & running my own servers, it is always a pleasure reading how others small / solo businesses are running their show.
It is so cool to see one-person SaaS business running on old school bare metal servers without needing any fancy devOps / containerize tooling.
Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software
#8Great stuff.
Off topic, any pgDash alternatives for MYSQL?
Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software
#9How much does it all cost?
The monthly Hetzner bill is €484.
Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software
#10Very cool setup.
I know it's a bit silly, but anyone building out cloud services should look at this post and think about how easy it is to set up this. This is just slightly more complex than a static site, has a bit of heterogenity, but otherwise is a lot of known tools.
Can your stack provide all of this without breaking the bank for the people signing up? Can it be done without having to learn a bunch of bespoke systems? I think that Heroku's success in particular is totally down to managing this bespoke-ness balance (that is still kinda missing from container-based setups).