Home / Website monitoring for agencies

Website monitoring for agencies

Watch every client site from one account, get the cause when something breaks, and send a monthly report that proves the retainer.

The problem

A client rings before you know their site is down. The certificate expired on a Sunday. A deploy dropped a checkout page and nobody noticed for a day. None of that is a monitoring problem until it is a trust problem.

What you get

One account, every client site

Group monitors per client, tag them, save a dashboard view per client, and give each client their own status page on their own domain. Team members and clients see only what you show them.

The cause, not a red dot

An incident says "TLS handshake failed: certificate expired" or "HTTP 502 from the proxy", with what that usually means. You call the client with the fix, not with a question.

Proof for the retainer

A monthly e-mail report per client with uptime, incidents and response times, ready to forward. Ninety days of history on Free, one year on Solo, two on Team.

Screens are rendered from markup with sample data, not screenshots of a customer account.

Which plan

Usually Team

White-label status pages, 100 monitors, three login seats for colleagues and three notify-only seats for clients. Every number is on the plan table; start on Free and upgrade when you need it.

Questions

Can clients see their own status page without seeing other clients?

Yes. Each status page shows only the monitors you attach to it, on a slug or on the client's own domain (custom domains from Solo, no ErrorDetector badge from Team).

Do I need to give clients a login?

No. Clients get a public status page, subscriber e-mails when it changes, and the monthly report. Logins are for your team.

Where do the checks come from?

One origin in the European Union. Client compliance teams can be told exactly that, and nothing else is invented.