Use case

Know a site is down before your client does

Uptime checks every 5 minutes, alerts delivered where you work, incidents drafted for you and public status pages, so an outage is handled, not discovered.

Start free trial See notifications

From $2.99 a month for 1 site, with a 7-day trial.

The problem

Why this is hard today

Clients notice first

If the first you hear of an outage is from a client, you are already behind.

Alerts get lost

An alert that only reaches one inbox, buried among routine notices, is easy to miss.

Everyone wants an update

During an outage, clients want to know what is happening, and writing updates takes time away from the fix.

How MaintainHQ handles it

From the first failed check to the resolved update.

Monitoring, alerts, the incident and the fix sit in one place, and nothing is published or changed until you approve it.

Step 1: Check
Uptime checks run every 5 minutes, alongside SSL expiry and PHP error monitoring.
Step 2: Alert
You are alerted once an outage is confirmed: in the dashboard, by email, in Slack or to your own webhook.
Step 3: Draft the incident
MaintainHQ drafts an incident with a plain-English update and shows what changed in the 2 hours before.
Step 4: Diagnose and fix
Gus diagnoses the outage and drafts the fix for your approval, with a backup, verification and automatic rollback.
Step 5: Update the status page
You approve the update before it is published. When the site recovers, the resolved update is drafted too.

Routine alerts wait until your quiet hours end. Critical ones, like a site going down, always get through.
Choose which events notify you, whether each is sent straight away or in the digest, and which sites it covers.
Status pages can be public or password-protected, with email updates for subscribers and Slack notifications.
Schedule maintenance windows on a status page, so planned work is not mistaken for an outage.

What's involved