About

I built this because I got tired of two failure modes.

Cheap monitors flood your inbox. Premium monitors miss the real outages and report database errors as SEO problems. Monitrova is an attempt at a third option.

What this is

Monitrova is a SaaS website monitor. It watches three layers of every site you add: uptime (HTTP/HTTPS reachability and response time), SSL (validity, hostname match, expiry), and homepage health (a daily audit of title, meta description, h1, canonical, noindex directive, robots.txt, and sitemap.xml — plus integrity classification for backend errors and crash pages).

The differentiator is the alert pipeline. Every alert decision passes through a service that knows the difference between a one-off blip and a real problem, bundles repeating issues into a daily digest, and never sends a "recovered" email for an alert it never fired.

Where it's at

Auth, account scoping, CSRF, prepared statements, output escaping, and the alert pipeline have all been reviewed and tested (71 of 71 unit tests passing as of late April). What's still in flight: deliverability warmup, a few empty-state polish items on the dashboard, tokenised "view this incident" deep-links from emails, and per-day-of-week quiet hours.

If you sign up early, expect rough edges and direct contact. I'd rather you find a problem before the next person does.

Who built this

Built by , a solo developer working out of sourcecode.es. I write everything end to end and ship it under my own name. PHP 8.4 on MariaDB, dark by default. The scan loop, alert pipeline, decision service, dashboard, and Stripe integration are all hand-written — no framework, no Composer, no SDK lock-in. Outbound email goes through Mailgun because running my own SMTP reputation for transactional alerts is a fight I don't need to pick; everything else is mine. The whole thing audits in an afternoon.

I chose that stack on purpose. A monitor needs to keep running. The fewer moving parts, the fewer things break in the next dependency CVE cycle.

Voice

I don't write "game-changer" or "AI-powered" or "10x". The audience for an uptime monitor is engineers and tech-aware site owners who appreciate competence more than enthusiasm. I try to write the way I'd want to be written to.

Get in touch

hello​@monitrova.com for anything — feedback, integration questions, or to tell me I'm wrong about something.

Security disclosure

Found a vulnerability? Email security​@monitrova.com. I aim to acknowledge within 72 hours and patch critical issues within 30 days. Please give me a reasonable window before disclosing publicly — I’d rather get it right than fast. Machine-readable contact lives at /.well-known/security.txt.

Want to try it on a real site?

The free plan covers one site forever. Add a URL and the first uptime check fires within a few minutes.