SavaPato is a self-hosted WordPress plugin for uptime, SSL, and redirect monitoring with email/Slack alerts. See features, pricing plans, and pros & cons.
SavaPato Uptime Monitor is a WordPress plugin for independent, self-hosted website uptime monitoring, positioned as a privacy-friendly alternative to external SaaS monitoring services. Installed directly on a WordPress site, it periodically checks a list of monitored URLs and records their HTTP status, response time, and consecutive-failure counts, storing the history entirely in the site's own WordPress database rather than sending data to a third party. Beyond basic up/down checks, it can watch for specific keywords in a page's response, monitor SSL certificate expiry with configurable notification thresholds, and track HTTP-to-HTTPS and www redirect behavior. When a monitored URL fails, SavaPato automatically classifies the failure reason (DNS failure, timeout, SSL expiry, 4xx, or 5xx) and sends email alerts on downtime and recovery, with customizable re-notification intervals; paid tiers add Slack notifications via an Incoming Webhook and multiple notification recipients. Checks run on WordPress's built-in WP-Cron scheduler, and administrators can define maintenance windows (one-time, weekly, or monthly) that suppress alerts without pausing monitoring. A dashboard lists all monitors with recent failure counts and supports bulk enable/disable/delete operations, plus built-in diagnostics (test email, manual health checks, manual cron triggers, environment checks) for troubleshooting the plugin itself. Historical data includes uptime percentage and average response-time reporting, with paid plans unlocking incident history and downtime-duration tracking. SavaPato is offered on a freemium model: a free tier and three paid tiers differentiated by number of monitored URLs, history retention, check interval, and number of installable sites.
Key Features
All features — Overview page listing every SavaPato monitoring capability, from URL checks to SSL and redirect monitoring.
Monitoring — Core monitoring engine that periodically checks each configured URL for availability and records the result.
URL monitoring — Add any number of URLs and have each one checked on a regular schedule.
Status detection (Up / Down) — Determines a monitored URL's up/down status from its HTTP response on every check.
Consecutive failure count — Tracks how many checks in a row have failed for a monitor, helping gauge how serious an outage is.
Response time tracking — Records the response time in milliseconds for every check, building a history over time.
Max Response Time setting — Lets you set a maximum acceptable response time per monitor so slow — not just down — responses can be flagged.
Enable / disable monitoring — Turn monitoring on or off for any individual URL without deleting its configuration.
Keyword check (contains / does not contain) — Checks a page's response for the presence or absence of a specific keyword as part of the health check.
Failure reason classification — Automatically classifies why a check failed — DNS failure, timeout, SSL expiry, 4xx, or 5xx.
SSL certificate expiry monitoring — Monitors each URL's SSL certificate expiry date and displays the number of days remaining, with configurable alert thresholds.
Redirect monitoring — Monitors HTTP-to-HTTPS and www redirect behavior for each monitored URL.
Pros & Cons
Pros
Self-hosted — all monitoring history and data stay on your own WordPress site rather than a third-party SaaS
Free plan available (3 monitored URLs, 7-day history) with no credit card requirement implied by the pricing page
SSL certificate expiry and redirect monitoring are included alongside basic uptime checks
Automatic failure-reason classification (DNS failure, timeout, SSL expiry, 4xx/5xx) helps diagnose the cause of an outage faster
Cons
Requires an existing WordPress installation — not usable as a standalone monitoring service for non-WordPress sites
The free plan only checks every 5 minutes; the faster 1-minute interval is limited to paid tiers
Slack notifications, multiple notification recipients, and incident history are gated behind paid plans