MantisOps
MANTISOPS Managed IT Operations
Home Legal

Usage & Overage Policy

Effective: October 11, 2026 · Last updated: October 11, 2026
This policy is incorporated by reference into the Terms of Service and, where applicable, your Master Service Agreement. If it conflicts with a signed Order Form or MSA, that document controls.
Contents
  1. 1. Purpose
  2. 2. Usage Units by Product
  3. 3. How MantisNMS Sensors Are Counted
  4. 4. Mantis360 Accidental-Discovery Grace
  5. 5. When Usage Decreases
  6. 6. Overage Handling
  7. 7. Usage Telemetry
  8. 8. Changes
  9. 9. Contact

1. Purpose

Each MantisOps product is priced on a usage unit. This policy explains how usage is counted for each product, what happens when your usage exceeds the quantity in your plan, and how to increase or decrease your subscribed quantity. It exists so there are no billing surprises: the counting rules are stated up front, overage is handled predictably, and you keep control of your quantity.

2. Usage Units by Product

ProductBillable unitWhat countsWhat does not count
MantisRMMPer active agent (managed endpoint)Each endpoint with an installed agent that has checked in during the billing cycleUninstalled agents (once they stop checking in, per Section 5)
Mantis360Per monitored asset (device)Each discovered/monitored asset that is live during the cycle, plus assets deleted during the cycle after the accidental-discovery grace window (Section 4)Assets deleted within the grace window; transient scan artifacts
MantisNMSPer sensorSee Section 3 (PRTG-style sensor model)SNMP/host devices themselves (a device is a free container)

Your plan includes a quantity of the applicable unit. Usage above that quantity is "overage" and is handled per Section 6.

3. How MantisNMS Sensors Are Counted

MantisNMS uses a "device = free container" model. Adding a device costs nothing on its own; you are billed for the sensors you actively monitor on it:

  • Each non-SNMP leaf monitor (for example: ping/ICMP, HTTP, TCP, SSH, TLS, DNS, Redfish, vCenter) = 1 sensor.
  • Each monitored network interface you select on an SNMP device = 1 sensor. Interfaces you do not select are not billed.
  • Each host-resource aspect a monitored device reports — System Uptime, CPU, Memory, and each fixed disk — = 1 sensor. You may pause individual host aspects so they do not bill.
  • An SNMP or host device itself counts as 0 — it is a free container for the sensors above.

Your current billable sensor count and its breakdown are shown in the MantisNMS interface (sidebar and plan-usage view). Trial accounts are capped at a fixed sensor limit; exceeding it requires a paid plan.

4. Mantis360 Accidental-Discovery Grace

Network discovery can surface assets you did not intend to monitor long-term (for example, a one-time broad scan). To avoid billing for these, Mantis360 applies a 7-day accidental-discovery grace window: an asset discovered and then deleted within 7 days is not billed. An asset that remains past the grace window, or that is deleted after it, counts toward usage for the cycle in which it was live.

5. When Usage Decreases

Usage counts follow real activity, but subscribed quantity is never decreased automatically (see Section 6.2):

  • MantisRMM — an uninstalled or permanently offline agent stops contributing to the usage count once it has stopped checking in. Your billed quantity, however, does not drop until you request a decrease.
  • Mantis360 — deleting an asset removes it from future usage counts (subject to the grace rule in Section 4).
  • MantisNMS — deselecting an interface, pausing a host aspect, or deleting a sensor removes it from the billable count immediately; your billed quantity changes at the next cycle per Section 6.2.

6. Overage Handling

6.1 Automatic quantity increase

You authorize MantisOps to automatically increase your subscribed quantity as your actual usage grows past your current paid step. Prorated charges for the increase apply immediately and appear on your next invoice. This keeps the Services running without interruption as you scale. You can review current usage at any time in the Customer Portal at https://portal.mantisops.net/billing.

6.2 Quantity is never automatically decreased

Uninstalled agents, deleted assets, or removed sensors do not automatically reduce your billed quantity. To decrease your quantity, email support@mantisops.net. The decrease takes effect at the start of the next billing cycle, with no proration credit for the unused portion of the current cycle. This confirms intent and prevents gaming the proration window.

6.3 Trial and capped plans

Some plans (including trials) enforce a hard cap rather than automatic overage. When you reach the cap, additional agents, assets, or sensors above the limit may be blocked until you upgrade. Where a cap applies, it is shown in the product interface.

6.4 Enforcement of unpaid overage

If overage charges are not paid when due, the payment and suspension terms of the Terms of Service or MSA apply (currently, suspension may occur when payment is more than 15 days past due).

7. Usage Telemetry

To count usage accurately, our agents, probes, and collectors report operational usage data (for example, agent check-ins, monitored asset counts, and sensor counts) to the MantisOps platform. This data is described in our Privacy Policy. If usage telemetry is blocked, we may estimate usage from the most recent available data or from your configured quantity.

8. Changes

We may update this policy with notice as described in the Terms of Service. Material changes affecting how usage is counted or billed will be communicated by email before they take effect.

9. Contact

Billing questions: support@mantisops.net · Customer Portal: https://portal.mantisops.net/billing

MantisOps, LLC · 6650 Rivers Ave., Suite 100 · Charleston, SC 29406

← All legal documents