Monitoring client websites: one panel, a separate report for each
Thirty websites means the same setup thirty times, thirty inboxes receiving alerts, and one question at the end of the month: did anything go down. Uptimo splits services into groups that match your clients, measures availability to the second and sends a separate report for every group.
What thirty websites actually cost an agency
Maintaining other people's websites is a different problem from maintaining your own. It is not about whether you can fix it in time. It is about whether you can show what happened, and how long it takes to onboard the next client.
The client asks whether the site was up
Without measurement it is one recollection against another. The conversation about the quality of your work ends in impressions, and theirs are usually fresher.
Alerts from every client in one inbox
Nobody knows whose site it is or who should react. After a week the team stops reading notifications altogether.
A new client means an hour of clicking
The same set of checks entered from scratch on every onboarding, with the risk that somebody's certificate or DNS quietly gets missed.
The client wants visibility, not the ability to break things
Read access without edit rights is a reasonable request. In most tools it means either full access or none at all.
A group per client, a role per person
You split services into groups, one group per client. That decides who receives alerts, what they see in the panel and how the report looks.
Four roles
Owner, Administrator, Member and Observer. An Observer sees status and history and cannot change a single setting.
Alerts per group
Notifications go to the recipients of that group, so whoever is on call does not get incidents from a client they do not handle.
Audit log
A record of who changed what and when. With a team and a rotating on-call schedule it is the only way to reconstruct a decision made a month ago.
We create accounts on request
The person you add receives a message and sets their own password. We never mail passwords, and there is no invite screen inside the client panel.
A report you can send with the invoice
The SLA report covers availability, downtime, incident count and mean time to repair. It goes out by e-mail weekly or monthly, separately for each group.
- Availability calculated to the second from incident history, not estimated.
- A planned maintenance window silences alerts, and excluding that period from the SLA figure is a separate, deliberate decision. The client can therefore see what was planned downtime and what was a failure.
- The report carries your agency's branding: we upload the logo during onboarding, it is not a switch in the panel.
- History on the Agency plan reaches 180 days, so a conversation about last quarter has something to stand on.
The next client without starting from zero
We export the monitoring configuration to a file and load it for the next website, leaving secrets out. We do this on request, so do not look for a button in the panel. The effect is that onboarding cost stops growing linearly: a proven set of checks for a shop on the same platform gets copied instead of rebuilt.
What it costs across a portfolio of clients
You pay for the number of services, scenarios and check frequency, not for the number of people on your team or the number of alert recipients.
Annual billing is 20% cheaper. Unlimited alert recipients and service groups are in every plan, including the free one. If you need more than 150 services or a separate check location, that is a conversation about a dedicated instance.
What is missing, stated plainly
- There is no public status page for your clients. It is on the roadmap and we do not sell it as finished. Today visibility comes from the Observer role and the recurring report.
- Your client cannot invite users from the panel. We create accounts on request, so that the split of roles between the platform and the organisation stays airtight.
- The logo in the report and the configuration export are handled by the operator. Neither is a switch in the panel.
- Checks run from a single location in the European Union. Separate or private locations are part of a dedicated instance.
What agencies ask
No. The group is the boundary: an Observer added to one client's group sees only the services, incidents and reports of that group. Accounts are created on your request, so you decide who lands in which group.
Yes, and that is the usual model. You pay for the plan and invoice your clients for maintenance with your own margin. An SLA report in your branding is the argument that the retainer covers something, rather than being a fee for standing by.
You set a maintenance window for the duration of the work: alerts go quiet, and excluding the period from the SLA is a separate decision. If the deployment changed the page permanently, a scenario step is fixed in the panel in a minute, without writing code.
The limit is 150 services and 30 scenarios, not a number of clients. A client with three checks and one checkout scenario takes four slots, so thirty such clients fit with room to spare. Beyond that we talk about a dedicated instance.
Yes. The fourteen day trial needs no card, and the Solo plan is free indefinitely and watches three addresses together with their certificates. Many partners start with one demanding client and add the rest after the first report.
Take one client and look at the first report
Create an account, add one client's website as its own group and schedule a weekly report. In a week you will have a document you can forward without editing it first.