A hosting provider or an agency can run PingWise for its customers. Each customer gets its own account, with its own monitors, logins and alert channels, under your brand. You and your team can open any of them; your customers see only their own. Their checks are paid from your credits. There is nothing extra to pay: reselling is included in the credits you buy.
Starting
Open Customers in the panel. The page explains what you get and shows the Reseller Agreement, which adds to the Terms of Service: what you may do, what you owe your customers, and how credits, support and data protection work between us. Only an owner can accept it; the acceptance is recorded with the owner's name, the date and the version. Until it is accepted, any customer accounts you already have keep working as before, with PingWise's look on alerts and no caps or usage reports. Nothing changes for your own monitors.
After accepting, Set up reselling on Customers lists what is left: the brand, the first customer, the first invitation.
Your brand
Your customers inherit your brand: their status pages, alerts and invitations carry it, and they cannot edit it. On Branding, a brand has two things to fill in for reselling:
- Alerts in your name: the sender name, the reply-to address and a support URL. Your customers' email and chat alerts carry these, and replies go to you, not to PingWise. Emails come from
[email protected]with your name until you add your own domain. - Your customers' terms: the addresses of your own terms of service and privacy policy. Your customers' users join under your terms, not PingWise's: you are responsible for their data, and PingWise processes it on your behalf. You cannot invite a customer's user until both links are set. What those two documents must cover is in section 5 of the Agreement: our Acceptable Use Policy, or rules no weaker than it; that the service detects and reports problems but does not guarantee that every problem will be detected or that every alert will be correct; that PingWise (Netlayer) runs the service and processes the customer's data for you with a link to our Privacy Policy, and that your staff can enter the customer's account to support it and that this is logged and shown to the customer. For most providers this means a few added sentences in their existing terms and privacy notice, not new documents.
Text you can paste
Two paragraphs you can paste into your own documents. Replace <your name> with your trading name. They cover what section 5 of the Reseller Agreement asks for; keep the rest of your documents as they are. They are not legal advice: your own lawyer may rephrase them, as long as the four points stay.
For your terms of service:
Website monitoring. The website monitoring and status page service that <your name> provides to you runs on PingWise, a service operated by Alexandros Kyrlis, trading as Netlayer (Greece). It checks the targets you configure from several locations and reports what it finds. It does not guarantee that every problem will be detected, that every alert will be correct or arrive within a given time, or that the service will run without interruption; keep your own safeguards. You may only monitor hosts that you own or are authorised to monitor, and PingWise's Acceptable Use Policy (https://pingwise.com/acceptable-use/) applies to your use of the service as part of these terms. To support you, our staff may open your monitoring account and make changes in it; every such access and change is recorded and shown to you in your account under Support activity.
For your privacy notice (it assumes your contract with the customer as the legal basis; change that clause if yours differs):
Website monitoring (PingWise). To provide the website monitoring and status page service, we use PingWise, operated by Alexandros Kyrlis, trading as Netlayer, Eleftheriou Venizelou 31, 16675 Glyfada, Greece, as our processor under a data processing agreement, in order to perform our contract with you. On our behalf it stores the details of the people you invite into your monitoring account (name, email address, role), the addresses you monitor and the results of the checks, the alert channels you set up (such as email addresses, chat identifiers or webhook addresses) and the subscribers of your status pages, and it sends alerts and notices to those addresses in our name. Its servers are in Germany; the checks themselves run from its servers in several countries, including outside the EU, under the standard contractual clauses and the sub-processor list in its Data Processing Agreement (https://pingwise.com/dpa/). PingWise also keeps, as a controller in its own right, the login and security records and the log of our staff's actions in your account that its Privacy Policy describes (https://pingwise.com/privacy/).
The «Powered by PingWise» line stays on status pages and in alerts until the account has bought credits; then it can be switched off, as on status pages.
Your own sender domain. Also on Branding, you can send your customers' alerts from alerts@yourdomain. Add the domain, put the DNS records we show at your DNS provider, and we check every few minutes; until the records are found, alerts come from our address with your name. The emails are sent through Amazon SES in Ireland; the domain's reputation is yours to keep.
Adding customers
Add a customer on Customers creates an account under yours. Give it the name the customer knows itself by, which they see when they log in, and optionally their email, kept for the invitation. Start with an empty account and add their monitors by hand, with Quick add or an import, or pick the customer's Enhance organisation: its websites get monitors in the new account and stay in sync. With the Enhance integration, Create a customer account for each Enhance customer does this for every organisation at once.
When the monitors are in, invite the customer from its Team page. The invitation carries your brand and links your terms and privacy policy, with one sentence saying that PingWise processes the data on your behalf. The customer's users then see only their account.
Credits, caps and usage
Every customer's checks are charged to your pool, at the normal rates. On Credits → Usage by customer, this month you see what each customer used and can set a monthly cap per customer, in credits per calendar month (UTC). At 80 % you get a notice; at 100 % that customer's monitors pause for the rest of the month, with a notice to you and to the customer's users in your brand, and resume on the 1st or as soon as you raise the cap. Usage is counted a few hours behind, so a cap can be passed by a few hours of checks; your other customers and your balance are not affected.
Download usage CSV gives one row per customer per month for the last 12 months. Your owners also get a usage report by email after each month closes, from the first full month after the Agreement was accepted.
Seeing everything at once
A reseller's panel opens on Overview: monitors and open incidents across all accounts, what is down right now and in which account, uptime over 30 days for everything together, credits used this month, and a table of accounts. Monitors and Incidents have an All customers tab next to Yours only, with a Customer column and filters; opening a row takes you into that customer's account. Bulk changes, groups and status pages stay per account.
Supporting a customer
When you or a team member opens a customer's account, a banner says so: «You are in
A team member can be invited as Viewer (read-only): they can open every customer account and change nothing.
Stopping
Stop reselling on Customers switches it off and ends the Agreement, once every customer account has been deleted (or handed over to the customer, where you ask and we can). Your own monitors carry on, and your brand fields stay.
Last change: 2 November 2026.