Lansweeper supports both cloud-hosted and on-premises deployment. The cloud version uses a lightweight Discovery Hub installed on-premises that bridges the local network to Lansweeper's cloud console — no inbound firewall rules required. The on-premises version runs on a local Windows server with a SQL Server database.
Most organizations are scanning their first assets within hours of starting deployment. The agentless approach means there is no agent rollout phase — Lansweeper scans using existing network protocols, which dramatically reduces initial deployment effort compared to agent-based tools.
Scanning method flexibility is one of Lansweeper's architectural strengths. It supports active scanning via SNMP, SSH, WMI, and WinRM; passive network monitoring; agent-based collection for remote or off-network devices; and cloud API integration for Azure, AWS, and GCP. The practical benefit is that a single Lansweeper deployment can cover the full asset estate — data center servers, remote laptops, factory floor OT equipment, and cloud infrastructure — without requiring separate tools or modules per environment type.
The integration ecosystem covers the ITSM and security tools that matter most for asset-aware workflows: ServiceNow, Jira Service Management, HaloITSM, Freshservice for ITSM; Axonius, Qualys, and Tenable for security; and Microsoft Intune and SCCM for endpoint management. Lansweeper's value in the integration context is as a source of truth for asset data — it feeds accurate, normalized inventory into downstream tools rather than replacing them. Validate the specific integrations for your ITSM and security stack during the trial.