Monitrova

A couple of weeks ago I posted about soft-launching Monitrova, a website monitor I started building because alerts had become too noisy to trust.

Since then, I’ve been tightening up the product and the positioning.

Monitrova is now live as a website monitoring tool for freelancers, small agencies and developers who look after client sites.

It monitors:

Uptime
SSL certificates
Homepage health

But the bigger focus is still alert quality.

I do not want Monitrova to be another tool that sends an email every time a site has a tiny wobble, then another one five minutes later saying it recovered.

So the alert pipeline now works around a few principles:

Non-critical issues should be confirmed before they become alerts.

Critical issues should still alert immediately.

Repeated flapping should be summarised instead of spamming the inbox.

Recovery emails should not be sent if the original alert was held back.

Backend failures should be classified properly instead of being mistaken for SEO issues.

That last one is important.

A WordPress site can return a response but still show a database error, PHP fatal, blank page or broken homepage. A basic uptime check may say the site is online, but the client still sees a broken website.

That is why Monitrova checks homepage health as well as uptime and SSL.

I’ve also added the WordPress Site Agent on paid plans, which creates a timeline of useful events before an incident, such as plugin updates, theme changes, WordPress core updates, PHP fatal errors, cron issues and WooCommerce problems.

The goal is simple:

Find out your client’s site is broken before they call you, and get an alert that is actually worth opening.

There is now a free plan for one site, no card needed.

I’d still really value feedback from other indie hackers, especially anyone managing client sites, WordPress sites, WooCommerce stores or SaaS landing pages.

The question I’m still trying to answer:

What would make you trust a monitoring alert enough to act on it straight away?

https://monitrova.com

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