[tibozaurus]

And mostly closed source :)

[typosaur]

Is being open-source the only differentiator you have?

Only software devs care about this. Your competitors make millions of $ annually, without being open-source.

[robertlagrant]

This seems a bit inappropriately toned. Plenty of businesses care about this, as it de-risks things if you know you can self-host if necessary.

[chrisandchris]

Yes, sure. But the difficulty about monitoring is not the hosting per-se, but hosting in different datacenters throughout the world abd keeping all these services up.

My monitoring should not show "just down" if users from location A can't reach it but everyone else can.

[ushakov]

How many web-services out there are actually geographically distributed? Most companies just host everything in us-east1

[chrisandchris]

Uptime monitoring services? I think most of those I tried (and I tried many in the past weeks).

[lucgagan]

I never understood the "de-risk" things angle. Is the idea that you'd self host if the service went under?

[robertlagrant]

Yes, or a new company could post on Reddit, "would anyone like this service?" and spin up a replacement. Probably not worth it in this instance, but I imagine a lot of people sleep better at night knowing that Postgres is available to self-host, or from a variety of cloud providers.

[lmeyerov]

It's worth coming up with a stronger public-facing answer

We went through this last year, I think we have a public one, a private one, + our actual more 'serious' telemetry (opentelemetry, ...). For the status pages, I think one we don't pay for, and the other is like $20/yr.

It's a crowded space, both open + closed, so clearer differentiation seems useful for your users and for your own journey: https://github.com/ivbeg/awesome-status-pages