Jira Service Management vs Lansweeper

Jira Service Management

The most capable ITSM platform a district can actually afford — Atlassian gives K-12 a 50% academic discount — but self-hosting has closed to new customers, and its CMDB is an empty box you have to model yourself.

Where Jira Service Management is strong

• ● The deepest ITIL process set of anything on this page: incident, problem, change, and request management, service catalog, approvals, SLAs, on-call schedules and alert routing, and deployment gating tied to CI/CD.
• ● A real academic discount that names K-12 districts and boards of education — 50% off Jira Service Management on Cloud, 75% off Confluence, and Atlassian Guard free.
• ● The Free plan is genuinely usable for a small shop: three agents, unlimited customers, and an embedded knowledge base included, with no trial clock.
• ● Assets is included from Standard upward with 5,000 objects, rising to 50,000 on Premium, plus basic network discovery on Premium and 30-plus import adapters.
• ● An enormous marketplace and an excellent API, so almost any workflow you can describe can be built — by you, by a partner, or by an app someone already wrote.
• ● Atlassian is not going anywhere, and if your district already runs Jira for other departments the service desk shares the same platform, permissions, and automation engine.

What to check before you buy

• You can no longer buy self-hosted. Atlassian closed Data Center to new customers on 30 March 2026, stops selling expansions to existing customers in 2028, and takes Data Center read-only at end of life on 28 March 2029.

  Basis: Atlassian's own Data Center end-of-life page states each of those dates and defines new customers as organizations that never owned paid Data Center seats before 30 March 2026.

• Assets is a flexible CMDB, not an ITAM product. It ships empty — you author the object schemas, types, and attributes yourself before it holds a single Chromebook, and Atlassian's own copy jokes that it can model 'people records? Fish?'

  Basis: Atlassian's asset and configuration management feature page describes it in exactly those terms; discovery is IP-network scanning, listed as a Premium addition.

• No device custody as a product concept — no check-out to a named student, no due date, no overdue list, no parent-signed agreement, no loaner pool, no lost or stolen lifecycle, and no damage fees. You would model all of it yourself in objects and workflows.

  Basis: None of those terms appear on the Assets feature page; ownership is an attribute you define, not a transaction the product understands.

• No SIS or rostering integration exists. Marketplace searches for ClassLink and Skyward return zero results, and searches for OneRoster, PowerSchool, and Infinite Campus return only unrelated token matches.

  Basis: Queried directly against the Atlassian Marketplace REST API. Atlassian also publishes no education vertical page — /solutions/education and /industries/education both 404.

• No student, guardian, or family concepts. The only end-user primitive is 'customer,' an unlicensed requester. There is no enrollment, no grade, no guardian relationship, and nothing that notices a mid-year transfer.

  Basis: Atlassian's pricing and feature documentation define customers as unlicensed users who can raise requests; no education-specific data model exists.

• Change management — the single capability districts most often cite as the reason to choose JSM — sits on Premium, at roughly two and a half times the Standard rate.

  Basis: Atlassian's plan comparison lists change management, advanced incident and problem management, the virtual service agent, and asset discovery as Premium additions.

• SAML SSO is a separate purchase. Enforced SSO, SCIM provisioning, and password policies come from Atlassian Guard, priced per user across your whole Atlassian estate — not per agent.

  Basis: Atlassian's JSM pricing FAQ states SAML SSO is enabled 'with a subscription to Atlassian Guard.' Guard Standard is $4.20 per user per month, bundled into Enterprise, and free under the academic program — so for a qualifying district the cost is nil, but it is still a second product to apply for and administer.

• Two metered dimensions make the bill non-deterministic: Assets objects past the plan allowance and virtual-agent conversations past 1,000 a month. A district that models every Chromebook, charger, and hotspot as an object should count objects before signing.

  Basis: Atlassian's pricing page publishes $0.02 per object per month and $0.30 per conversation over allowance.

How Chalk compares with Jira Service Management →

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 Jira Service Management 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.