InvGate Asset Management vs Jira Service Management

InvGate Asset Management

A serious corporate ITAM platform with real discovery, a CMDB, and an on-premises option — priced per networked device, which is the worst possible meter for a 1:1 district.

Where InvGate Asset Management is strong

• ● Genuinely strong automated discovery — a lightweight agent, agentless network scanning, integrations, and bulk import covering hardware, servers, containers, databases, and cloud services.
• ● A real CMDB with automatic relationship discovery and assisted dependency mapping.
• ● A deep integration catalog: Intune, Jamf, SCCM, Active Directory, Entra ID, Okta, AWS, Azure, VMware, ServiceNow CMDB, Jira Service Management, Zendesk, Slack, Teams, and remote-access tools, plus a documented REST API.
• ● A genuine on-premises option on Windows Server or RHEL with your choice of database, including support for air-gapped operation — unusual in this category.
• ● Google Workspace integration that imports ChromeOS devices and users, so Chromebooks do land in the inventory automatically.
• ● Software asset management with license optimization, metering, deployment, and compliance.

What to check before you buy

• Pricing is per networked device per year, so cost scales directly with fleet size. A district with one Chromebook per student is quoted on the single number it has most of, which is the opposite of a per-technician model.

  Basis: InvGate's published pricing page prices Pro per IP device per year and defines an IP device as any asset connected to a network with an IP address.

• Ticketing is a different product. InvGate Asset Management is ITAM only; a help desk means separately licensing InvGate Service Management, which is a second contract and a second bill.

  Basis: InvGate sells Asset Management and Service Management as two separately licensed products and describes the ITAM platform as functioning standalone.

• No SIS or rostering integration — no OneRoster, Clever, ClassLink, or PowerSchool. The identity sources in the integration catalog are corporate directories only.

  Basis: InvGate's full published integration list names Active Directory, Entra ID, Okta, Google Workspace, and cloud platforms; no education system appears.

• No student or guardian concepts. Asset owners are users and employees, with no enrollment, grade, guardian relationship, or reaction to a mid-year transfer.

  Basis: The product's lifecycle and ownership model is employee framed; the vendor's named customers are manufacturing, utilities, aerospace, retail, and insurance.

• No 1:1 device circulation loop — no due dates on a student's device, no overdue workflow, no e-signed parent agreement, no loaner pool, and no lost or stolen lifecycle. The lifecycle modelled is procurement, assignment, and disposal.

  Basis: Absent from InvGate's asset lifecycle documentation, which is corporate IT framed.

• No funding-source or grant tracking — no way to attribute devices to ESSER, Title, or E-Rate money for reporting.

  Basis: No grant or funding-source dimension appears in the product documentation.

• ChromeOS support is import only. Chromebooks and users come in from Google Workspace; nothing writes back — no OU moves, no disable, no annotated fields.

  Basis: InvGate documents the Google Workspace integration as importing users, ChromeOS devices, and organizational data; no write-back is claimed.

• It consumes SSO but is not an identity provider — Okta and Entra ID appear as identity sources it reads, not identity it issues.

  Basis: InvGate is configured as a service provider against an external IdP; it is not listed as issuing SAML or OIDC.

How Chalk compares with InvGate Asset Management →

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 →

The third option: Chalk

If you are weighing InvGate Asset Management against Jira Service Management, 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.