Sell monitoring to your clients without building it

Who it is for

What you get

• Client workspaces under one bill. Each client is a separate workspace (monitors, servers, status pages, alert channels, team members, branding) that runs on your plan. Your clients never see a Vigil invoice.
• White-label status pages. Paid plans can hide Vigil's branding; every plan allows custom domains, a logo and custom CSS on status pages.
• The Partner API. Create, list, rename, suspend, restore and delete client workspaces over HTTPS with JSON, idempotent on your own id. Documented below and in the interactive API reference.
• WHMCS provisioning module. Create, suspend, unsuspend, terminate and single sign-on from the WHMCS admin and client area, with usage shown to the customer. Download vigil-whmcs.zip (PHP 8.1+, no dependencies).
• Login links. A one-time URL, valid for 5 minutes, that logs your customer (or your own staff) straight into their workspace. No second password to manage.
• An audit trail. Every Partner API call is recorded in your workspace's audit log.

How billing works today

There is no separate reseller price list yet. You hold an ordinary Vigil plan, and each client workspace counts against that plan's client-tenant allowance:

Partners usually start on Business. When you need more clients, add the +5 client tenants pack for $20/month each, up to 40 packs (200 more clients). Each client workspace runs with your plan's limits (Business: 1000 monitors, 100 servers and 50 status pages). You set your own prices for your customers. If the API reaches your client allowance it answers 402 with the same message the dashboard shows.

Planning something bigger, or need terms we do not list here? Write to hello@puzaricloud.in.

Getting started

1. Sign up and choose the Business plan (14-day trial, no card).
2. Under Settings → API keys, create a read/write key for the whole workspace (not limited to a team). Read-only keys can only list.
3. Call the API below, or install the WHMCS module and put the key in the server's password field.

Partner API reference

Base URL https://puzaricloud.in/api/v1/partner. Send Authorization: Bearer vgk_…. Requests and responses are JSON. Calls count towards your plan's per-minute API limit and answer 429 with Retry-After when it is reached. A client object looks like this:

{"id": 42, "name": "Acme Retail", "external_id": "whmcs-1001", "contact_email": "ops@acme.example",
 "created_at": "2026-10-03T09:12:44+00:00", "suspended": false, "suspended_at": null,
 "usage": {"monitors": 4, "servers": 1, "status_pages": 1}}

curl -X POST https://puzaricloud.in/api/v1/partner/clients \
  -H "Authorization: Bearer $VIGIL_KEY" -H "Content-Type: application/json" \
  -d '{"name": "Acme Retail", "external_id": "whmcs-1001", "contact_email": "ops@acme.example"}'

curl https://puzaricloud.in/api/v1/partner/clients -H "Authorization: Bearer $VIGIL_KEY"
curl "https://puzaricloud.in/api/v1/partner/clients?external_id=whmcs-1001" -H "Authorization: Bearer $VIGIL_KEY"

curl https://puzaricloud.in/api/v1/partner/clients/42 -H "Authorization: Bearer $VIGIL_KEY"

curl -X PATCH https://puzaricloud.in/api/v1/partner/clients/42 \
  -H "Authorization: Bearer $VIGIL_KEY" -H "Content-Type: application/json" \
  -d '{"suspended": true}'

curl -X DELETE https://puzaricloud.in/api/v1/partner/clients/42 -H "Authorization: Bearer $VIGIL_KEY"

curl -X POST https://puzaricloud.in/api/v1/partner/clients/42/login-link -H "Authorization: Bearer $VIGIL_KEY"
# {"url": "https://puzaricloud.in/partner/login/…", "expires_at": "…", "as": "client", "email": "ops@acme.example"}

curl https://puzaricloud.in/api/v1/partner/usage -H "Authorization: Bearer $VIGIL_KEY"
# {"plan": "Business", "clients": {"used": 3, "cap": 25, "suspended": 0}, "totals": {"monitors": 12, ...}, ...}

WHMCS module

Unzip vigil-whmcs.zip into your WHMCS root so the files land in modules/servers/vigil/. Add a server under System Settings → Servers with module Vigil, hostname https://puzaricloud.in and your partner API key as the password, then press Test Connection. Create a product with module Vigil. The WHMCS service id is used as the external_id, so re-running Create is safe. The client area shows the workspace's usage and a "Log in to monitoring" button.