Show HN: OpenStatus – Open-source monitoring with incident managements
First, congrats on the launch!<p>Why did you end up going with a SaaS model? 30 Euros or $31.50 USD is pretty expensive for something like a status site. You&#x27;d have a lot less to manage day to day and be able to focus more on innovating the product if you <i>just</i> sold the software, imo.<p>Why the focus on synthetic monitoring? As a SRE, I actively eschew synthetic monitoring. It&#x27;s highly error prone and doesn&#x27;t actually indicate regional availability. I&#x27;d like a status site that I could push a certain internally derived SLA for a given service to and the status site reflects the average over time of that windowed SLA.<p>SLA&#x27;s are intended to incur customer refunds when they&#x27;re violated if they&#x27;re meaningful. If your synthetic monitoring shows an SLA of 4 nines but it was actually closer to 4.8 or 4.9 then you could be on the hook for causing your customers a good bit of legal pain. Just something to think about in this space.<p>Other status sites don&#x27;t build external SLAs off of internal metrics because the process of deriving internal metrics that align with external outcomes is sufficiently difficult. Instead, they calculate an SLA based off of posted statuses over a period of time eg: Degraded, Down, Up. Supporting both modes could be a boon to potential customers.<p>Overall looks like a great start; good luck on your venture!