alt Hacker NewsThe thing about status pages is they have to be up when you're down, and (if your service is non trivial) they have to be able to handle a traffic profile that basically looks like DDOS. So, you're paying for the hosting infra more than the software.
Replies
Yeh, I've tackled this problem a few times, and just like back-ups you at some point need something external, because if you're down, you don't want your status page to go down too. This means you need to make sure to sandbox it pretty hard if rolling your own, ideally on a separate cloud behind a different CDN etc...
Chrome tells me that page is almost 4MB? I feel like you could better handle loads against a nicely formatted text file.
Hosting a static page updated once per minute or so is hardly rocket science.
when you are funded by investment money, you don't need to care much about these things.
This is fundamentally the argument against all "SaaS is dead due to AI" claims.
Replicating the basic functionality for most SaaS is trivial, it's the "everything else" part that you're actually paying for.