--- title: Monitoring for Agencies & Client Sites description: Watch every client site from one account: a status page per client, tags and alert routing per client, and the checks that catch an expiring domain before the client does. canonical: https://watchfor.io/for-agencies --- # Be the agency that calls the client before the client calls you Fifty client sites, each needing uptime, a certificate watch and a domain watch: on most tools that is a pricing problem before it is a monitoring one. Here all three are ordinary monitors from one allowance on every plan — no SSL or domain add-on, no per-site or per-seat fee — and every client can have a status page with their name on it. When something breaks, you hear first, and you are already on it when they notice. [Start free](/auth/sign-up)[See pricing](/pricing) 9:41 9:41 ## The expiry that ends the relationship A lapsed domain or an expired certificate is the one outage a client never forgives, because it was entirely preventable. Domain expiry and SSL certificate monitoring are ordinary monitor types on every plan, drawn from the same allowance as uptime checks rather than sold as an add-on — so a renewal thirty days out is an alert in your inbox, not an angry Monday-morning phone call. - [Domain expiry monitoring](/domain-expiry-monitoring) - [SSL certificate monitoring](/ssl-monitoring) ## A status page with each client's name on it Give each client their own status page at its own short address (clientname.watchfor.io), showing only the monitors that concern them and password-protected if the work is under NDA. During an incident they see that you already know and are on it — which is most of what a client wants from you at that moment. Three are included on the free plan and 25 from €7 a month. - [Status pages](/status-pages) ## The monthly report you currently write by hand Uptime and SLA reports are calculated from confirmed incidents rather than from raw failed checks — so a single blip from one probe never turns a perfect month into 99.4%. Print any report to PDF or export it as CSV and the monthly update is done, with a number you can stand behind when the client asks how it was measured. - [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. And with the open-source watchfor-agent you can watch your clients' servers too — CPU, memory, disk and processes from inside the machine, per organization — on Starter and up. - [CDN monitoring](/cdn-monitoring) - [Email deliverability](/email-monitoring) - [Blacklist monitoring](/blacklist-monitoring) - [Server monitoring](/server-monitoring) ## Where we are not the right answer - There is no white-label: status pages live on a watchfor.io address and carry a small "Powered by WatchFor" footer, and clients cannot log in to see only their own monitors. - There is no per-client billing or invoicing on our side; you buy one plan and organise clients into monitors and status pages. - Server monitoring needs the agent installed on the client's machine — a VPS you have no shell on can only be watched from the outside. ## Questions people ask Can I put a client's status page on their own domain? Not yet. Each status page gets its own address on watchfor.io (clientname.watchfor.io), 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/sign-up)[See all monitor types](/monitoring) --- Canonical page: https://watchfor.io/for-agencies · Site guide: https://watchfor.io/llms.txt