Very 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…
What One-person SaaS Healthchecks.io uses for hosting, hardware and software
21–30 of 180 posts
Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software
#22> On app servers: [...] Are "app" servers the haproxy ones or the "web servers", or other ones not mentioned?
Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software
#23Very 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…
> This is just slightly more complex than a static site That's because their product is only slightly more complex than a static site. I wish every project was as basic as a web server and database but it's pretty rare these days.
Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software
#24Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software
#25If I'd run a one man show type of business, I'd love to have some kind of plan B in case I'd be incapacitated for more than half a day. THAT would be an interesting read to me.
Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software
#26Very 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…
If you're running a site like this, it's fine to be down for a bit, people will forgive you as you restore from backup (looks like a very solid foundation the site has).
Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software
#27Hardware redundancy aside (and the good cost efficiency at Hetzner), reading the title, I'm getting the impression, the bus factor at healthchecks.io seems to be 1. If I'd run a one man show type of business, I'd love to have some kind of plan B in case I'd be incapacitated for more than half a day. THAT would be an interesting read to me.
Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software
#28Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software
#29Earlier quoted context omitted.
> This is just slightly more complex than a static site That's because their product is only slightly more complex than a static site. I wish every project was as basic as a web server and database but it's pretty rare these days.
Most saas companies are simple crud apps.
What you're seeing is survivorship bias where the SaaS companies that are doing well are the ones that can provide a simple, clean UI whilst adding the functionality that you need for the product to be useful.
Re: What One-person SaaS Healthchecks.io uses for hosting, hardware and software
#30Very 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…
> This is just slightly more complex than a static site That's because their product is only slightly more complex than a static site. I wish every project was as basic as a web server and database but it's pretty rare these days.
I feel like the overwhelming majority of web based software projects can be catered for with exactly this setup.
If it's rare it's because everybody's drunk the Kool-aid