Plans and billing
Billing is per organisation and handled under Billing by the owner. What follows applies when the installation sells plans; the administrator may run everything on one plan without billing at all.
Plans
Every limit lives in the plan: number of monitors, servers, alert channels, team members, status pages and API tokens, the fastest check interval, the number of monitoring locations, how many days of raw history are kept, the API rate per minute, AI summaries per month, the number of client organisations an agency may have, and switches for white-label, reseller billing, reports, SMS/WhatsApp alerts and e-mail alerts. -1 (shown as unlimited) lifts a limit. The public plans and their prices are on /pricing and in GET /api/v1/plans.
A new organisation starts on the installation's default plan (normally Free). Plans with a trial give you the paid limits for the trial days.
Cycles and prices
Plans are priced per month; a yearly price is either set by the administrator or computed with the yearly discount (default 15 %). Prices are in the installation's currency (USD by default; a separate USD price can exist for BDT installations). Tax, when the administrator sets a rate, is added to the invoice.
Coupons
Enter a coupon code at checkout. A coupon gives a percentage or a fixed amount off, may be limited to certain plans, to a number of uses and to an expiry date.
Paying
- On Billing choose a plan and a cycle. An invoice (numbered, with subtotal, discount, tax and total) is created.
- Pay it with one of the payment methods the administrator has enabled:
- Manual methods (bank transfer, mobile wallets such as bKash/Nagad, cash): the page shows the account details and instructions; you enter the transaction ID and can upload a proof (screenshot). The payment waits as pending until an administrator approves it; you receive a payment received e-mail (or payment rejected with a note).
- Stripe, PayPal and Paddle, when the administrator has configured them: you are taken to the gateway and the plan is activated as soon as the payment is confirmed. With Paddle, Paddle is the merchant of record and adds the sales tax itself; it refuses currencies it does not support (for example BDT) before anything is charged.
- The subscription is granted for the paid months; renewing before the end adds to what is left.
Buying from your agency
When your organisation is a client of an agency or reseller (see Agencies and resellers), you buy from the agency, not from the platform:
- Billing → Plans shows the plans the agency offers, at its prices and in its currency. Choosing one creates an invoice from the agency (number
RS-…); an open invoice for the same plan and cycle is reused. - The invoice shows the agency's payment method, account and instructions. Pay as described, then enter the Transaction / reference id, optionally upload a Proof of payment (screenshot or PDF, up to 5 MB) and press I have paid.
- The agency approves or rejects the payment. On approval you get the payment received e-mail and the plan runs for the paid months.
When the agency has not switched reseller billing on, the Plans page says that your plan is managed by the agency.
Paddle setup (administrator)
Add the method on Admin → Payment methods → New payment method:
- Type: Gateway; Gateway: Paddle; a Name customers will see.
- Publishable key / client id: the Paddle client-side token (used by Paddle.js on the checkout page).
- Secret key: the Paddle API key (stored encrypted).
- In Paddle, under Developer tools → Notifications, add a notification destination for the event
transaction.completedwith the Paddle webhook URL shown on the form:
https://your-monitor.example/app/billing/webhook-paddle
- Copy the destination's secret key (
pdl_ntfset_…) into Webhook signing secret (stored encrypted). - In Paddle, set Checkout → Default payment link to:
https://your-monitor.example/app/billing/paddle-checkout
- Tick Sandbox mode (test payments) to use Paddle's sandbox, set Currencies if the method should only be offered for some, and make it Active.
How a payment runs: the platform creates a Paddle transaction for the invoice total and sends the customer to its checkout (or to the platform's own checkout page, which opens Paddle.js). When Paddle reports transaction.completed, or the customer returns and the platform asks Paddle about the transaction, the invoice is marked paid and the plan granted.
The webhook checks the Paddle-Signature header (ts=…;h1=…, an HMAC-SHA256 of ts:body with the signing secret) and refuses timestamps older than 5 minutes. Every event id is handled once; a replay is answered and ignored. Without a signing secret the webhook trusts nothing in the body and confirms the transaction with the Paddle API first. A transaction that belongs to a different invoice is ignored.
Invoices
All invoices are listed on the Billing page with their status (unpaid, paid, cancelled, refunded), the method and a printable view. The administrator can see and change every invoice and payment under Admin → Payments & invoices.
Invoices from an agency carry the agency's name and address and are handled by the agency. If your organisation is an agency with reseller billing, the invoices you send to your clients, the payments to approve and your revenue are on Agency → Billing & revenue (see Agencies and resellers). That money goes to the agency directly; the platform records no payment for it.
Expiry, grace and reminders
Reminder e-mails go out 7, 3 and 1 day before a subscription ends. After the end date the subscription is past due for the grace period (3 days by default) and keeps its limits; after the grace period the organisation falls back to the default plan. Monitors above the new limit are not deleted, but you cannot add more until you are within the limit again, and features the plan lacks (extra locations, SMS, white-label, API) stop working.
Cancelling keeps the plan until the paid period ends.
One click helps us improve these docs.

