Monitrova — find out your client's site is down before they call you
fallback covers the rare no-JS visitor. System-font<br>fallbacks (DM Sans → ui-sans-serif → -apple-system → ...) absorb<br>any FOUT for the ~200ms it takes the webfont to arrive. -->
Free for 1 site · No credit card · Two-minute setup
Find out your client's site is down<br>before they call you.
Confirmed uptime, SSL, and homepage health on every site you ship — set up in two minutes, with no 3am false alarms.
Start free
Confirmed alerts only<br>Slack & webhook delivery<br>Paid from €5.99/mo
Check any site's uptime now
Check now
Full report →
Free instant check — no signup. See the full checker →
Real monthly report from a site I monitor.
Built by one person at sourcecode.es · Running on 16 of my own sites · Why this matters →
This is you<br>Three kinds of people end up here.
Each one runs sites for a slightly different reason. Pick the closest match — the rest of the page is written for all three.
Freelance web developer
“My client called me about an outage I didn’t know about.”
Most monitors flood your inbox until you mute them. Monitrova confirms the problem first, classifies what actually broke, and sends one alert with the answer. Plus a monthly health report per site — ready to forward as part of your maintenance retainer.
On Starter and up: Site Agent adds a WordPress timeline so you know which plugin broke things, not just that they broke.
See the alert pipeline →
Small agency or studio
“The Slack channel goes off for every blip and nobody reads it anymore.”
Per-site sensitivity, flap bundling, and a daily digest mean the channel pings when it matters. Audit log shows which alert decisions fired and why — so when a senior dev asks “did we miss it?”, you have an answer.
Pro covers 50 sites with 1-minute checks — agency volume at €19.99/month .
See per-site controls →
Solo developer / indie hacker
“I just want the JSON and to be left alone.”
Drop a webhook URL, pipe it anywhere — PagerDuty, OpsGenie, a personal Slack, a Discord bot. Confirmed alerts only. Quiet hours. Exponential backoff that spaces out repeat alerts so you’re not paged every minute. No marketing email from the monitor itself.
Free plan covers one site, forever — no card, no trial countdown.
See the webhook payload →
What gets monitored<br>Three layers, one timeline per site
Uptime, SSL, and homepage health — all stitched together so you see the cause, not just the symptom.
Uptime
HTTP/HTTPS checks at plan intervals. Per-site timeout, redirect handling, response time logged in milliseconds.
SSL certificates
Issuer, expiry, hostname match. Tiered alerts at 30/14/7/3 days remaining — each fires once.
Homepage health
Title, meta, h1, canonical, robots.txt, sitemap. Plus integrity classification: a "database error" page reports as a backend incident, not a missing meta tag.
Daily view<br>All your sites on one screen
Open the dashboard with your morning coffee. Health, last-checked time, and what’s flagged — before anything turns into a phone call.
What I check first thing in the morning.
WordPress intelligence Starter plan and up
Alerts that name what changed, not just what broke.
Site Agent is the WordPress plugin that turns alerts into a timeline — every plugin update, theme switch, admin login, fatal error and WooCommerce gateway failure, captured back to Monitrova. So when an alert fires, the answer’s already on the incident page.
Real Site Agent dashboard from a WordPress site I run — the heartbeat snapshot is what fires when an alert is held back.
A timeline per site
Plugin / theme / core / user changes, fatal PHP errors, debug.log lines, WooCommerce signals, performance trends, security events — each one a human sentence with severity, timestamp, and metadata.
Root cause, at a glance
When a fatal fires at 03:14 and a plugin auto-updated at 03:10, both rows show up on the incident page. No SSH session, no log diving — the "what changed?" answer is already there.
Privacy-conscious by design
No customer or order detail. IPs and User-Agents SHA-256 hashed by default. Zero frontend output. All heavy work runs on WP-Cron, off the request path.
What Site Agent captures →
The no-noise pipeline<br>Other monitors send by email.<br>Monitrova sends through a decision service first.
Every alert decision — sent, suppressed, deferred, or summarised — is logged with a reason. No silent dropouts.
Pipeline log<br>Last 24h · 5 decisions
09:14
acme-shop.com<br>Site is down
Critical issue — skips confirmation, fires immediately
Email sent
11:02
blog.acme.com<br>Sitemap.xml briefly unreachable
Non-critical — wait for second scan to confirm
Deferred
11:32
blog.acme.com<br>Sitemap.xml back at next scan
Resolved before alerting — no email sent, no recovery email either
Silently cleared
13:00–17:30
api.acme.com<br>Same issue opens & recovers 3+ times in...