I soft-launched a website monitor because alerts became too noisy to trust

I’ve just soft-launched Monitrova, a website monitoring SaaS for freelancers, small agencies and developers who look after client sites.

The idea came from a problem I kept running into while maintaining websites: monitoring tools technically worked, but after enough noisy alerts, repeated recovery emails and vague “SEO issue” warnings, I started ignoring them.

That is the wrong outcome for a monitoring tool.

Monitrova monitors uptime, SSL certificates and homepage health, but the main thing I’m trying to solve is alert quality.

A few examples:

A short wobble should not always become an email.

A site flipping between down and recovered all day should not spam the inbox.

A WordPress database error should be treated as a backend incident, not reported as a missing meta description because the audit ran against an error page.

So I’ve built the alert pipeline around things like confirmation checks, flap detection, daily digests, quiet hours and recovery suppression.

It is still early. The product has been soft launched and beta accounts are available by invite while I keep the first group small and gather feedback from people who actually maintain sites.

I’d really value feedback from other indie hackers, especially anyone running client sites, WordPress sites, SaaS landing pages or small business websites.

The thing I’m trying to learn:

What would make you trust a monitoring alert instead of ignoring it?

Site: https://monitrova.com