Administration Guide

About Licensing

This topic set describes the Billing area of App Management together with the per-Site caps that partition instance entitlement across tenant Sites.

AlloyScan licensing is enforced at two layers: the instance layer (the license file uploaded to the AlloyScan instance) and the Site layer (per-Site Max caps that delegate consumption to individual tenants). Together they let an instance owner set an upper bound for the whole deployment and partition it across Sites.

Note: This page covers instance-level administration in App Management. It is used by Global Administrators.

How licensing works

Instance-level license

The license file establishes the entitlements of the entire AlloyScan instance. It carries:

  • Serial No. — the license identifier.
  • Expiration — the date the license becomes invalid.
  • Organization — the licensee name.
  • User — the license contact.

The instance license also defines the Discovery quotas — Nodes (audited devices), Users, Audits per month, and API transactions per month. Each quota is either a finite number or Unlimited (∞).

A Global Administrator uploads the license file at Admin Center > App management > Billing > License Information.

Per-Site quotas

Each Site has its own per-Site Max caps for Users, audited Nodes, Audits per month, and API transactions per month. These are configured at Admin Center > Site Settings > Organization profile and reviewed at Admin Center > Site Settings > Limits and usage.

A Max value of 0 on a per-Site quota means "no per-Site cap — inherit from the instance license". This is how a Global Administrator delegates the whole instance entitlement to a single Site, or how tenants without contractual sub-limits are configured.

Recharge day

Two of the four quotas are time-bounded: Audits per month and API transactions per month. Their counters reset on the recharge day — a fixed day-of-month that applies instance-wide. For example, if the recharge day is the 27th, both monthly counters reset at the start of the 27th of each month.

The recharge day is shown at Admin Center > Site Settings > Limits and usage > Subscription information and at Admin Center > App management > Billing > Limits and usage > Subscription information. Per-Site usage history is preserved month-by-month in the Usage History table on each page, so prior periods remain visible after a reset.

Tiering

AlloyScan licensing supports tiering (for example, small office, enterprise, MSP). The observable mechanism is the combination of the instance-level license (which can be Unlimited on each Discovery quota) and per-Site Max caps (which the Global Administrator uses to enforce per-tenant limits). Public pricing is described at a high level on the Alloy Software website ("per Technician + per audited computer, annual").

Note: Details may vary by deployment.

Why this design

A two-layer model — instance license plus per-Site caps — supports both a single-organization deployment (one Site, all instance entitlement) and a multi-tenant MSP deployment (many Sites, each with contractually limited consumption). The recharge day gives every Site a predictable monthly reset for time-bounded quotas without coupling resets to creation date.

Key distinctions

  • Instance-level vs Site-level quotas — the instance license sets the upper bound; per-Site caps partition it. Per-Site Max = 0 means "inherit instance".
  • Hard vs soft caps — Nodes and Users are hard caps (the instance enforces them outright). Audits per month and API transactions per month are soft caps with a monthly recharge.
  • Audit log entries vs license usage — every audit consumes one Audits-per-month unit; that unit is restored on the next recharge day.

Limitations

  • License upload happens through the Upload license action on the License Information page; the upload action is Global-Administrator-only.
  • The exact per-second / per-minute API rate ceiling is enforced server-side but is not surfaced in the UI; only the per-month counter is visible.
  • License tiers are not exposed as named SKUs in the UI; entitlement is expressed through Unlimited / numeric values on the Discovery quotas.