![]() Plus, doing it this way doesn't mean paying per-subscriber. If your service goes down it's trivial to send out an apology email to your customers, and you should already be sending maintenance emails a few days prior to keep your customers in the loop. If you want to replicate this setup at home, create a repo on GitHub, open Gitpod on that repo and run npx statusfy init. However, I'd argue that having subscribers isn't a necessary feature at all. Statusfy is an open source tool with GitHub stars and GitHub forks. Statusfy is a tool in the Status Page Hosting category of a tech stack. You can easily create a fast Static Generated System and easily deploy it to a variety of hosting services. The only thing that this doesn't have is subscribers - I can't have customers subscribe to our status page to be automatically alerted when there's downtime. Statusfy is a Status Page System, easy to use and completely Open Source. It's completely open sourced at, is statically generated (so it's hosted for free on github pages), displays beautiful uptime graphs for every service (thanks to updown.io), and I can create incidents (like maintenance or downtime investigations) with markdown using the Nuxt Content plugin. The only downside is that I have to create the status page myself - thankfully Nuxt.js and TailwindCSS exist so I made short work of that during the Thanksgiving weekend. That's a lot more economical than what hyperping costs. That's when I found ! If I have 5 APIs (or Websites) that I want to monitor every 5 minutes, it only costs me $0.80/month for all of them - and I'll get 2 months for free. ![]() Self-hosted solutions like are awesome but require having a database and some infrastructure to deploy on, and static solutions like don't do uptime monitoring for you (which is important to some businesses) I've been working on the status pages for Pigeon Post and Lynk during the last week, and when I looked at existing solutions like or, I found that either the prices were ridiculous (Status Page I'm looking at you □) or you couldn't customize the page's CSS too deeply.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |