# What changed in Lansweeper and why it matters
Lansweeper historically offered an on‑premises IT asset management (ITAM) and network discovery product. Starting with version 10.4, the default installation links to Lansweeper Cloud. The local installation you used to run on your own server is now called Lansweeper Classic. That shift has pushed some organizations to look for alternatives that match their preferred deployment model or discovery approach.
# What Lansweeper still does
Lansweeper builds a centralized inventory of devices and services connected to a network. Its published capabilities include:
- Agentless discovery with credential‑free recognition. Machine learning fingerprinting compares devices to a library of more than 175 million device fingerprints to identify hardware even when you don't have credentials. Credentialed scans are available for deeper profiling.
- Discovery across IT, OT, cloud and IoT categories: workstations, servers, network devices, segmented industrial systems, virtual machines, containers and cloud services via provider APIs.
- Optional agent for remote endpoints while the platform focuses on agentless methods.
- Two distribution models: Lansweeper Platform (cloud) and Lansweeper Classic (on‑premises, Windows servers with Microsoft SQL Server database and a local web console).
These features explain why many teams initially chose Lansweeper: broad device recognition, multiple discovery modes, and support for cloud resources alongside on‑premises equipment.
# Why teams look for alternatives
The default installer's cloud linkage in v10.4 changes how new Lansweeper deployments behave out of the box. Organizations that require strict data locality, have policies against cloud hosting, or simply prefer maintaining the entire stack themselves may be uncomfortable with a cloud‑first default. That has prompted a re‑evaluation of tools that offer different deployment defaults, discovery techniques, pricing structures, or review profiles.
# What the comparison covers
The guide behind this brief evaluates 11 Lansweeper competitors for ITAM with a consistent checklist, verified against vendor documentation in September 2026. The comparison focuses on:
- Deployment model (cloud, on‑premise, hybrid)
- Discovery methods (agentless, agent‑based, credentialed scans, API integrations for cloud providers)
- Pricing (vendor‑published pricing where available)
# How to use this information
If you manage an inventory that must remain behind your firewall, prioritize tools with a clearly supported on‑premises option and documented data residency. If you value minimal maintenance and automatic updates, cloud platforms may reduce upkeep. For discovery coverage, confirm whether a vendor emphasizes agentless credential‑free recognition, credentialed active scanning, or relies primarily on agents.
# Next steps
Refer to the detailed 11‑vendor comparison (dated September 2026) to match your requirements against each vendor's deployment options, discovery capabilities, pricing, and review scores. Keep Lansweeper's split between Platform and Classic in mind when comparing features and operational assumptions.