Incident IQ vs Lansweeper

Incident IQ

A K-12-only operations platform that combines IT ticketing, asset management, facilities work orders, event management, instructional resources, and HR service delivery in a single hosted suite.

Where Incident IQ is strong

• ● The broadest suite in K-12 operations: IT ticketing, assets, facilities, events, resources, and HR service delivery under one portal — the 'one platform, one portal' consolidation story is its most-cited win.
• ● Smart Audits can verify a device's presence automatically from MDM and sign-in activity, so a chunk of an inventory audit completes without anyone physically touching the device.
• ● Mature bulk-deployment tooling built for scale: rapid scan sessions, spare-pool allotments per building, and rollout accuracy checks aimed at large 1:1 distributions.
• ● Native iOS and Android apps with camera barcode scanning and voice lookup for technicians working in hallways and classrooms.
• ● AI ticket assistance for classification, suggested knowledge-base articles at submission time, and ticket summaries.
• ● Warranty status is a first-class field on the asset record and visible inside a ticket, with warranty claim submission through hardware partners.

What to check before you buy

• Hosted SaaS only — there is no self-hosted or on-premises option, so district data lives in the vendor's cloud and the software cannot be run or inspected independently.

  Basis: vendor site offers only a hosted product; no self-host or source distribution is published

• No public pricing. Every cost conversation starts with a sales demo, and pricing scales with student enrollment.

  Basis: vendor pricing page directs all buyers to schedule a demo for a tailored quote

• Price relative to value for smaller districts is the most frequently cited drawback in buyer reviews.

  Basis: recurring theme in public review-site feedback

• Limited customization is the second most cited drawback — districts report workflows and fields being harder to bend to local process than expected.

  Basis: recurring theme in public review-site feedback

• Online fee payment is not native. Collecting money means integrating a third-party processor such as InTouch, MySchoolBucks, Square, Stripe, or Vanco.

  Basis: vendor documents payments as partner integrations rather than a first-party module

• Warranty claim handling depends on hardware reseller partnerships rather than a vendor-neutral claims workflow.

  Basis: vendor documents claims through named hardware partners

• MDM integration is ingest-oriented: iiQ reads device state from Google, Jamf, and Intune rather than pushing a reviewed set of changes back into them.

  Basis: vendor asset documentation describes sync into iiQ, with no diff-preview write-back workflow

• Incident IQ is not an identity provider and does not serve a OneRoster API — it consumes rostering data rather than publishing it to other systems.

  Basis: vendor documents SIS connectors as inbound integrations only

How Chalk compares with Incident IQ →

Lansweeper

The strongest network discovery engine in this comparison — it will find every device on your wire, including the ones nobody told it about, and it will not know that any of them belongs to a seventh grader.

Where Lansweeper is strong

• ● Genuine network discovery, which almost nothing else in this category has: agentless scanning of Windows over WMI, Linux and macOS over SSH, and printers, switches, routers, firewalls and NAS over SNMP, so the inventory includes devices no one ever entered.
• ● A passive traffic sensor that discovers assets from network communications, catching devices that active scanning misses entirely — the closest thing to a real answer for shadow IT and unmanaged OT gear.
• ● An IT Agent for Windows, Linux and macOS endpoints that rarely touch the LAN, and Cloud Discovery across Azure, Intune, Microsoft 365 and Entra ID, AWS and GCP — with a reconciliation engine that merges the same device seen through several sources into one asset record instead of three.
• ● Vulnerability detection built on CPE correlation and VulnCheck, with CVSS severity and patch status against the software and OS actually in your inventory, alongside hardware and software lifecycle tracking for end-of-sale and end-of-support dates.
• ● Deployment packages in Lansweeper Classic — install software, run scripts and make remote changes on Windows machines from the same console that inventoried them.
• ● A full built-in help desk in Classic: tickets from the web console, email, API or import, dispatching rules, SLAs, teams, internal notes and a knowledge base.

What to check before you buy

• Lansweeper is two products with a documented feature gap between them — Lansweeper Platform in the cloud and Lansweeper Classic on-premises — and which capabilities you get depends on which one you deploy.

  Basis: Vendor's own 'Comparing Lansweeper Platform and Lansweeper Classic' documentation page, which lists discovery targets and features per product.

• ChromeOS discovery is a Lansweeper Classic capability. In the newer Lansweeper Platform the vendor's comparison table marks Chrome OS as 'Planned (Cloud Discovery)'. For a district whose fleet is Chromebooks, that is the whole fleet sitting on the older product.

  Basis: Vendor comparison table lists Chrome OS as supported in Classic scanning and Planned for Lansweeper Platform.

• Even in Classic, ChromeOS scanning is work you do yourself: your license must support Chrome OS scanning, and you build a Google Cloud project, enable the Admin SDK, create a service account and grant it scopes before a single Chromebook appears.

  Basis: Vendor's 'Chrome OS scanning requirements' documentation page.

• The help desk is licensed per agent. Unlimited users can file tickets, but exactly one agent license is included, and every additional technician who answers tickets is a paid seat at $120 per year.

  Basis: Vendor's 'Manage helpdesk agents' documentation plus the listed price in Lansweeper's own online store.

• That help desk belongs to Classic. The cloud Platform documentation covers no ticketing module of its own — service management appears as connectors to Jira Service Management, ConnectWise, Zendesk and Freshservice, meaning a second vendor.

  Basis: Lansweeper's documentation index places every help-desk article under Classic, and lists ITSM tools as integrations under Platform.

• The asset meter has teeth: reaching your licensed asset limit can stop scanning of new and existing assets until you delete assets or upgrade.

  Basis: Vendor's 'Manage your licensed asset limit' documentation page.

• No student, guardian or enrollment concepts, and no SIS or rostering connectors — the identity sources documented are Active Directory, Entra ID, Intune and Microsoft 365. Students arrive by CSV, if at all.

  Basis: Absent from Lansweeper's documentation index, which covers directory and cloud identity sources only.

• Nothing models the 1:1 program itself: no device agreement, no parent signature, no fee for a cracked screen, no family balance, and no funding-source dimension for ESSER, Title or E-Rate reporting.

  Basis: Absent from the vendor's documented feature set, which is discovery, inventory, risk and deployment.

How Chalk compares with Lansweeper →

The third option: Chalk

If you are weighing Incident IQ against Lansweeper, Chalk belongs on the same shortlist. It is the open-source K-12 IT stack: device inventory that fills itself in from Google Admin, Intune, and Jamf against a roster synced from your SIS, a 1:1 circulation desk with agreements and fees, repairs with parts and costs, a help desk that already knows who is asking, and a built-in SAML/OIDC identity provider.

• ✓ Self-host it free forever under AGPL-3.0 — the entire feature set, one binary, your infrastructure — or use the hosted version, priced by fleet size with no per-seat or per-student fees and the price ladder published.
• ✓ Built only for K-12: students, buildings, custody, funding sources, and ChromeOS auto-update expiration are native concepts, not custom fields.
• ✓ Writes back to Google Admin as a reviewed diff — every OU move, disable, and deprovision previewed before it executes — and serves a OneRoster 1.1 API so other district systems can pull the roster from Chalk.
• ✓ Fees are assessed and tracked without touching payment cards, keeping the asset system out of your PCI scope.