How this works
Five short pages: getting a first site watched, what is actually checked, who hears about a failure, how the numbers on a report are calculated, and how to turn all of it into an invoice.
- Quick startFrom signing up to a site that is genuinely being watched — about five minutes.
- What is actually checkedEvery check the product runs, what makes it fail, and what it needs from you before it will run.
- Alerts and who hears themChannels, escalation, grouping and maintenance windows — plus what happens when delivery is not configured.
- Reports, uptime and SLAHow uptime is calculated, what MTTR covers, and how an SLA target turns into an error budget.
- The APIA read-only HTTP API over your workspace — keys, endpoints, and why version 1 does not write.
- Billing your clientsPlans, subscriptions, invoices and VAT — the part that turns monitoring into revenue.
Two things worth knowing before you start
Everything here describes what the software does today. Where a feature is built but cannot run on this installation — e-mail delivery is the main one — the page says so in the place it matters, rather than in a footnote.
There are two audiences and two consoles. You are an agency: you sign in and see every client. Each of your clients gets a portal of their own showing only their own sites, under your name and colours. Wherever this matters, the documentation says which of the two it is talking about.
If you would rather click than read, the live demo opens the real console with sample data and no sign-up.