Studios, agencies and freelancers who maintain client websites on a retainer run into the same situation again and again: the client is the first to find out about a problem. The site stops opening, a form goes silent, a certificate expires — and the “everything is down” call comes in before the team has had a chance to notice anything.
The Pingvera solves that problem. It watches a fleet of client websites continuously, checks how they work from two sides — outside and inside — and sends a notification as soon as a failure has been confirmed. At the end of the month the client receives a white-label report on the work done.
Not a “ping”, but a check that the site works as a business
Ordinary monitoring answers only one question: does the site open? But a site can open and still not work as a business: enquiries from forms do not arrive, pages return errors, the domain is about to expire.
So Pingvera checks the things that actually bring the client money:
- availability and speed by request phase — HTTP, TCP, DNS, TLS;
- forms and enquiries — a synthetic form submission and a check that the enquiry arrives;
- the registration term of the domain, including the .ru and .рф zones, and of the SSL certificate;
- signs of a hack — suspicious redirects, injected spam, defacement — and SEO problems such as an accidental noindex or broken links;
- the state of WordPress and 1C-Bitrix from the inside — core and plugin versions, outdated components;
- the client's server — through a lightweight agent: CPU, memory, disk, network, containers.
External checks are run from several regions. If the site is alive from the other points, the problem is with one particular provider — and there will be no false alarm.
Alerts you can trust
The main enemy of any monitoring is noise. If a notification arrives for every momentary glitch, people quickly stop reading them.
In Pingvera an alert fires only after confirmation — several failed checks in a row. Flapping and dependent failures are suppressed, and maintenance windows are there for planned work. Notifications arrive in Telegram, by email, in Max, in VK or to any webhook you choose.
White-label reports and status pages
For a studio, monitoring is not only a technical matter but also the justification for the retainer. So Pingvera has tools for working with the client built in:
- a monthly white-label report in the studio's logo and colours — uptime, incidents, causes and resolution times, as a link or as a PDF;
- a public status page on the client's own domain via a single CNAME record — the certificate is issued and renewed automatically;
- event subscriptions for visitors, password protection, an SVG badge and a widget;
- a REST API with an OpenAPI spec and an MCP server, so that AI assistants such as Claude and Cursor can read the state of the monitoring.
The access model
The free plan is a full way in, not a trial period: up to five sites with checks from one minute, every type of external check and a status page. The paid plans are built for a growing retainer base — up to 50 and up to 500 sites, with CMS diagnostics and branding.
What this project shows
Pingvera is an example of a product in which technical depth goes together with an understanding of the user's business. The service does not simply collect metrics: it is built into the studio's real working process — from the first alert to the report the studio sends on to its own client.
For us it is one more confirmation of the approach: first work out how people actually do their jobs, and only then design technology around it.