Lansweeper asset counting is the set of rules by which Lansweeper measures consumption of its primary license metric, the Asset. The Terms of Use define an Asset broadly. The definition covers any device, including IT, OT and IoT devices, scanned or discovered on the customer’s systems; any resource or object discovered in the customer’s cloud environment; and any asset the customer creates in or adds to the Product.[2] The pricing FAQ gives the practical version: all IT, OT and cloud assets count toward the asset limit, including computers, servers, PLCs, network devices and manually created assets, along with monitors that have extended display data.[3] The count is visible to the customer in the Site under Site settings > Subscription plan.[1] It is also visible to Lansweeper, because the Product Metadata it collects includes the Asset count.[2]
Editions
The same counting rules apply to all paid plans. Only the asset limit differs: 2,000 assets on Starter, 2,000 to 9,000 on Pro and 10,000 or more on Enterprise.[3] The Free plan has a separate model of licensed and unlicensed assets, described below.[5] Lansweeper Classic and Lansweeper Sites use the same list of counted asset types.[4]
Metrics
The only counting unit is the Asset. The Lansweeper SAM add-on is priced per asset, one SAM asset per Lansweeper asset (SAM asset), so the same count also drives that add-on.
Counting / floors
Asset types that count
Lansweeper’s documentation lists computers, servers, network devices, OT devices, OT cards, Public Cloud workloads and manually created assets as counting toward the limit.[1] Catalog proof: Asset covers IT, OT, IoT, cloud and manually added assets; Computers, servers, network, OT, cloud workloads and manual assets count.
- OT assets. Lansweeper OT is a standalone scanner for PLCs and other industrial assets. It is available from the Starter license, and OT assets count towards the total number of licensed assets.[8] The asset limit example treats OT cards as separate assets from OT devices.[1] Catalog proof: OT assets count toward the licensed assets.
- Manually created assets. Assets added by hand count, including OT assets created in a Site that are never scanned.[1][10] This follows limb (iii) of the Terms’ definition.[2]
- Agent-reported assets. Computers, servers and other assets found by IT Agent Discovery count toward the limit. There is no limit on the number of IT Agents linked to a Site.[7]
Monitors
Monitors are assets, but they count only if they have extended display data associated with them.[1] Lansweeper gives a worked example. An installation licensed for 500 assets shows 450 assets, 60 of them monitors, and 24 of those monitors have no extended display data. Its licensed count is 426, which leaves room for 74 more assets.[1] Catalog proof: Monitors count only with extended display data.
| Step | Count |
|---|---|
| Assets in the installation | 450 |
| Less monitors without extended display data | minus 24 |
| Licensed asset count | 426 |
| Licensed limit | 500 |
| Headroom before the limit | 74 |
Public Cloud resources
Cloud Discovery inventories AWS, Azure and GCP resources, but not every resource is billable. A cloud resource counts when it is an independent workload with its own data plane, endpoint or attack surface. Virtual machines, managed databases, storage buckets, serverless functions and key vaults all qualify.[1] Resources that exist only as part of another asset do not count separately. Their data is kept on the parent asset or counted under a different meter.[1] Every resource type falls into one of five categories, and only the first is billable.[1]
| Category | Lansweeper description (abridged) | Examples given | Counts |
|---|---|---|---|
| Billable | Independent workload with its own data plane, endpoint or attack surface | VMs, managed databases, storage buckets, serverless functions, key vaults, API gateways, public IP prefixes | Yes[1] |
| Component | Auto-created sub-resource bound to a parent workload | EBS volume, network interface, managed disk, private endpoint | No[1] |
| Rule or metadata | Rule, policy, plan, commitment or execution record | Security groups, network ACLs, route tables, backup plans, reserved instances, App Service plans | No[1] |
| Group or container | Logical container whose contents are already counted | VPC, subnet, resource group, CloudFormation stack, auto scaling group | No[1] |
| User or account | Principal that can be granted permissions | IAM users and roles, Entra ID users, service principals, service accounts | No[1] |
The full list classifies individual services. On AWS, EC2 instances, Lambda functions, S3 buckets, RDS databases, DynamoDB tables, EKS clusters and WorkSpaces are billable, while EBS volumes, AMIs and security groups are not. On Azure, virtual machines, App Services, SQL servers, storage accounts, Key Vaults, AKS and Arc machines are billable, while managed disks, App Service plans, reservations and Virtual Machine Scale Sets are not. On GCP, VM instances, Cloud Run services, Cloud SQL databases, Cloud Storage buckets and GKE are billable, while instance groups and VPC networks are not.[1] Temporary resources follow the same rules. An EC2 instance that runs for one day and is discovered is stored and counted.[1] Catalog proof: Only independent cloud workloads are billable assets; Cloud components, rules, containers and identities do not count; Short-lived cloud resources count once discovered.
Commentary: because a scale set is a non-billable container but each VM instance in it is billable, the cloud asset count of an auto-scaling estate depends on how many instances existed when discovery ran, including short-lived ones.
Behaviour at the limit
Most Lansweeper subscriptions limit the number of assets that can be scanned. Once the licensed asset limit is reached, scanning of new and existing assets may stop until some assets are deleted or the subscription is upgraded.[1] The IT Agent documentation gives the same warning for agent-discovered assets.[7] Deleting an asset removes it permanently, but it reappears if Lansweeper scans it again. Cleanup rules can remove assets automatically based on conditions.[9] Catalog proof: Scanning may stop when the asset limit is reached; Deleted assets reappear if scanned again.
The Terms prohibit use designed to avoid charges or exceed license metrics, and forbid working around technical limitations in the Product.[2] Asset count is part of the Product Metadata that Lansweeper retrieves. Lansweeper may invoice prior unlicensed use when non-compliance is apparent from that metadata.[2] Catalog proof: No use designed to avoid charges or exceed metrics; Product Metadata, including Asset count, is collected for compliance; Non-compliance found in Product Metadata can be invoiced.
Licensed, unlicensed and non-billable assets (Free plan)
On the Lansweeper Platform, the Free plan scans the full environment with no asset cap. It includes 100 licensed assets: the first 100 scanned assets show full scan details, and everything beyond is unlicensed and shows only basic details such as name, type and IP address.[5] Non-billable assets are discovered assets of limited value, such as assets whose only known attribute is their type, metadata records, and infrastructure objects such as VPCs and containers. They never count toward the 100-asset limit.[5] Views can be filtered on a Licensed field with the values Licensed, Unlicensed or Non-billable.[5] Lansweeper states that the licensed and unlicensed model currently applies to the Free plan only and will extend to all plans in the future.[5] Catalog proof: Free plan licenses the first 100 scanned assets.
Lansweeper Classic works differently. When a trial or purchased license expires, the installation reverts to Free mode. The 100 assets with the most recent scan attempts keep receiving updated scan data. Other assets remain in the inventory but are no longer updated.[6] Catalog proof: Classic Free mode keeps updating only 100 assets.
Where the count is shown
In the Lansweeper Platform, the count and the limit appear under Site settings > Subscription plan.[1] In Lansweeper Sites, they appear under Configuration > License status. In Lansweeper On-premises, they appear under Configuration > Your Lansweeper License, or in the built-in report “Assets: All licensed assets in Lansweeper”.[4] With a digital license, each installation’s licensed count rolls up into the Site, and the limits apply there.[4]
Virtualization & partitioning
Lansweeper does not count hosts, processors or cores, and the retrieved documents publish no partitioning policy. Each virtual machine that Lansweeper discovers is an Asset. Cloud virtual machines are billable workloads, while scale sets and instance groups are non-billable containers.[1] On premises, the IT Agent reports Hyper-V virtual guests running on a device, and external monitors connected to it, so these can appear in the inventory as separate assets.[7] The reconciliation engine merges duplicates when the same physical device is found by several discovery methods in one Site.[7] Catalog proof: IT Agent reports Hyper-V guests and monitors as separate assets. See virtualization and partitioning for the cross-vendor background.
Cloud / BYOL
Public Cloud resources are counted by the classification above, whatever the provider. No separate cloud metric or bring-your-own-license rule applies.[1] Identities discovered in cloud accounts, such as IAM users or Entra ID users, appear in the user inventory rather than as assets and do not count.[1]
Programs
Beta Releases, Preview Features and Free Tools are subject to the same license metrics, as Lansweeper determines.[2] Catalog proof: Beta, Preview and Free Tools follow the same license metrics.
Out of scope
This page does not cover counting of Help Desk Agents or installations (see Lansweeper plans and add-ons and Lansweeper deployment types and license management). It also does not cover how to reconcile Lansweeper inventory against other vendors’ licenses. The retrieved documents do not say whether retired or archived assets count, or how assets that exceeded the limit before a renewal are treated.