--- title: Monitoring for Agencies & Client Sites description: Watch every client site from one account: white-label status pages, per-client reports, and the checks that catch an expiring domain before the client does. canonical: https://watchfor.io/for-agencies --- # Monitoring for agencies, priced by monitor rather than by client An agency's monitoring problem is not technical, it is arithmetic: fifty client sites, each needing uptime, a certificate watch and a domain watch, and a tool that counts those as three separate allowances or charges per site. Ours counts a monitor as a monitor, includes teammates on every plan, and lets you hand each client a status page that does not say our name. [Start free](/auth/signup)[See pricing](/pricing) ## The expiry that ends the relationship A client's domain quietly lapsing is the single worst thing that can happen to an agency retainer, and it is entirely preventable. Domain expiry and SSL certificate monitoring run as ordinary monitors here — not as a separate allowance you forgot to buy — so a renewal date thirty days out is an alert rather than a Monday morning phone call. - [Domain expiry monitoring](/domain-expiry-monitoring) - [SSL certificate monitoring](/ssl-monitoring) ## Status pages the client thinks are theirs Each client can have their own status page on their own domain, password-protected if the work is under NDA, with only the monitors that concern them. Three are included on the free plan and 25 from €7 a month, which is usually more than an agency needs before it is profitable. - [Status pages](/status-pages) ## The monthly report you currently write by hand Scheduled uptime and SLA reports go out by email per client, calculated from confirmed incidents rather than from raw failed checks — so a single blip from one probe does not turn a perfect month into 99.4%. That distinction matters more when the number is going to a client than when it is going to you. - [Reports](/reporting) ## Everything a client site can break in ways uptime does not see A site that returns 200 can still be failing the client: the CDN stopped caching and their bill tripled, the mail domain lost its DMARC alignment and invoices went to spam, the IP landed on a blacklist, the CMS got replaced by someone's cousin. Those are separate monitor types here rather than things you find out about later. - [CDN monitoring](/cdn-monitoring) - [Email deliverability](/email-monitoring) - [Blacklist monitoring](/blacklist-monitoring) ## Where we are not the right answer - We do not resell under your brand — the status pages are white-labelled, the account is not. - There is no per-client billing or invoicing on our side; you buy one plan and organise clients into monitors and status pages. - No server agents, so 'the client's VPS is out of disk' is not something we can tell you. ## Questions people ask Can I put a client's status page on their own domain? Yes — a custom domain per status page, with password protection if the engagement is confidential, and only the monitors you choose to show. How does pricing work across many clients? By monitor count, not by client or by site. Fifty client sites with one HTTP check each is fifty monitors; the same fifty with certificate and domain watches is a hundred and fifty. Count endpoints rather than domains when you size a plan. Do teammates cost extra? No. Team members are included on every plan with no per-seat fee, which is unusual in this category and matters when the person who watches alerts is not the person who set them up. ## Start with the thing you would hate to find out late 15 monitors free, commercial use allowed, no card required. [Start free](/auth/signup)[See all monitor types](/monitoring) --- Canonical page: https://watchfor.io/for-agencies · Site guide: https://watchfor.io/llms.txt