You build the sites. We give them a watch that never clocks off.
You maintain your clients' sites, and between projects it goes quiet. Monitoring, out-of-hours duty and a monthly report are the flat line item that fills that gap — under your brand and your invoice. The platform detects and notifies; you sell the response.
No exclusivity and no entry fee. You pick how to bill per client, not for the whole account.
What monitoring actually catches
Before you sell it, it helps to know what the client pays for. This is not „a ping now and then" — it is a set of checks, each catching a different way a site goes quiet.
Availability and a control phrase
We check that the site responds — and that it responds with what it should. A blank page with a 200 code is still an outage, so we also watch for a word that has to be on it.
SSL certificate
We warn from 14, 7, 3 and 1 day before it ends. No earlier, because automation renews the certificate around 30 days out and an earlier alarm would be false.
Domain expiry
We remind you from 30 days out, because recovering a domain after it lapses takes time, costs money and sometimes fails. We read the date straight from the registry.
DNS and security headers
A changed DNS record or a missing security header is often the first sign someone touched the configuration. We compare against the previous state.
Performance and content review
We measure the addresses you choose in fixed conditions and keep the history. The content review catches missing sections, soft 404s and a shrinking sitemap after a release.
Confirming an outage
Before notifications go out, we repeat the check. One network blink does not wake the client at three in the morning — and your duty keeps its credibility instead of spending it on false alarms.
A limit we state plainly
We check from a single vantage point, not from a dozen locations around the world. For most sites that is exactly enough — but promising „global monitoring from 30 regions" would be selling something we do not do. We would rather you knew what to tell the client.
A report the client understands
A retainer survives on proof of care. At the end of the period a PDF report is produced — you send it as your own, as the summary of the month the client pays for.
What the report contains
- Outages: when, how long, and how we knew it was over
- Time to detect and time to notify — kept separate
- Certificate and domain events, ahead of time
- Content and configuration changes caught in the period
What the report does not contain — and why
We do not put SLAs or prices in the report. The report says what happened, not what was promised — the promise belongs in your contract with the client, not in a document of measurements. Response times and how they are billed are your service, not a number drawn onto a chart.
Your duty on our engine
The platform detects and notifies, and a human responds — on any plan that human can be you. You sell the duty, the response times and the repairs; we supply the signal, the incident, the history and the report the duty stands on.
- 1
Alert
The platform confirms the outage and notifies — by email, in the phone app or in the team channel.
- 2
Incident
The event lands in the panel with time, address and history. You see what is down and since when, without guessing.
- 3
Response
You step in and fix it — this is the part the client pays you for, not the automation.
- 4
Report
The incident and how long it took land in the monthly summary. Proof the duty worked.
On Start and Business the duty is entirely yours — we run none of our own there. On Enterprise you can keep running it on your own terms too; our duty is then an optional add-on, not a condition of the plan.
Two ways to earn from it
Agencies work both at once, so the panel handles both. You choose per client.
You pay, you re-invoice the client
You take the plans on yourself and add your own margin. One combined bill and a shared renewal date for every site in the account — one invoice instead of twenty.
- Your margin, whatever you set
- One combined invoice, one shared date
- The client never sees our pricing
The client pays, you take the commission
You implement and hand over the payment by link — the client pays themselves, in one click, and you get 20% of every invoice they pay, with no end date. You stay with the client, so the commission keeps coming.
- 20% on net, flat and recurring
- Payment handed over with a single link
- Commission for as long as you serve the client
How it works in practice
One panel for everyone
Every client's sites in one place: plan, status, open outages, commissions. You switch between companies instead of signing in twenty times.
You set up a client in a minute
The account belongs to the client, and you get an administrator role in it. The client sees you on the team list and can remove you — we state this plainly, because it is honest and because that is how trust is built.
A plugin with your code
The WordPress plugin and the Neos, Sylius and Magento packages create the account with your referral code straight from the site's panel. For an agency that is a more natural channel than banners.
Settlement with no „paid" that is only planned
You get a statement and a PDF, you invoice us net (a PLN 200 threshold), we pay and mark it off. „Settled" means the money has left the bank — not that it was scheduled.
Worth reading before we talk
Let us talk terms
Tell us how many sites you run and how you want to bill. We start the programme together — we fit the mode, the rate and the way you onboard to how you already work.
The formal programme terms are still being finalised, so we take partners on through a conversation rather than self-service sign-up. The first contact is with a person.