InvGate Asset Management vs osTicket

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 →

osTicket

The open-source ticketing system a lot of school districts already quietly run — GPL2, free, self-hosted on a LAMP stack, and very good at tickets. The comparison with Chalk is about scope, not cost.

Where osTicket is strong

• ● Genuinely free and genuinely open source under GPL2 — no seat cap, no ticket cap, no trial clock, and the source is yours to read, patch, and keep running.
• ● One of the longest-running and most widely deployed ticketing systems anywhere, which means a large body of community documentation, forum answers, and people who have solved your problem already.
• ● A deep, well-worn ticketing core: custom fields and forms, custom columns and queues, ticket filters and routing, help topics, SLA plans, agent collision avoidance, assign/transfer/referral, auto-responders, internal tasks, and advanced search with CSV export.
• ● A customer portal and knowledge base for self-service, so end users can check status and find answers without opening a ticket.
• ● An official OAuth2 plugin covering Microsoft, Google, and Okta sign-in for both agents and end users, plus modern OAuth email authentication for system mailboxes — which matters now that basic auth is gone from Microsoft and Google mail.
• ● A working plugin surface and developer documentation: S3 attachment storage, audit logging, two-factor authentication, password policies, an API, and published database ERDs.

What to check before you buy

• No asset or inventory management at all. osTicket is a ticketing system — there is no device record, so a ticket cannot tell you which machine the student is holding, what its serial is, or whether it is under warranty.

  Basis: Asset and inventory management appear nowhere in osTicket's feature list or documentation index.

• No 1:1 device circulation: no check-out to a student with a due date, no overdue workflow, no parent-signed agreement, no loaner pool, and no lost or stolen lifecycle — and no native mobile app or barcode scanning to run a rollout or an audit with.

  Basis: There is no asset model in the product for these workflows to attach to, and the documentation has no mobile application section.

• No SIS or rostering integration — no OneRoster, Clever, ClassLink, PowerSchool, Infinite Campus, or Skyward — and no student, guardian, or enrollment concepts. Users are created by sign-in or import, not sourced from the system of record.

  Basis: No SIS connector exists in osTicket's plugin set or documentation.

• No ChromeOS, Google Admin, Intune, or Jamf ingest, so nothing reconciles anything against what the fleet actually reports.

  Basis: No MDM connector appears in the plugin listing or documentation.

• No repairs with parts stock, no student fee assessment or family balances, no purchase orders, no warranty tracking, and no funding-source reporting for ESSER, Title, or E-Rate money.

  Basis: All absent from the published feature list and documentation.

• SSO is consumed, not issued, and SAML is not covered by an official plugin — the supported providers are Microsoft, Google, and Okta over OAuth2, with SAML available only through an unofficial community plugin on GitHub.

  Basis: osTicket's OAuth2 documentation names Microsoft, Google, and Okta; the SAML plugin in circulation is a third-party repository, not a vendor-maintained one.

• Reporting is thin. There is a dashboard tab, but no reporting or analytics section in the documentation, so trend reporting past ticket exports usually means querying MySQL yourself.

  Basis: The documentation index has no dedicated reporting or analytics section.

• You operate a LAMP stack, not an application. PHP 8.2–8.4 plus MySQL plus a web server means patching three moving parts, and a PHP major-version bump is a real upgrade project rather than replacing one file.

  Basis: Requirements published on osTicket's download page and repository.

How Chalk compares with osTicket →

The third option: Chalk

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