osTicket vs Spiceworks Cloud Help Desk

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 →

Spiceworks Cloud Help Desk

A free, ad-supported help desk that many small district IT shops start on — capped at five technician seats, with no student roster and the device inventory in a separate product.

Where Spiceworks Cloud Help Desk is strong

• ● Genuinely free to start for a small IT shop, with unlimited end users and unlimited ticket volume — real value for a district that is currently running the help desk out of a shared inbox.
• ● Zero infrastructure: no server to procure, set up, or maintain.
• ● Email-to-ticket plus a customizable end-user web portal, automatic assignment and routing by priority and category, custom ticket queues, and custom attributes.
• ● Knowledge base and reporting dashboards on ticket volume and response time.
• ● Native iOS and Android apps for technicians with push notifications.
• ● A very large IT community behind it, which is genuine support value when you are a one-person department.

What to check before you buy

• The free plan caps technician and admin seats. Districts that grow past a handful of techs land on the paid plan, and the paid plan's fine print scales to total active employees — the opposite of what a district wants.

  Basis: Spiceworks' pricing page states the Core plan's seat range and footnotes that Premium pricing is 'based on the total number of active employees,' not on seats.

• No device or asset management inside the help desk. Inventory is a separate product built on network scanning — discovery of what is on your LAN, not a record of which student has which Chromebook.

  Basis: Spiceworks sells Inventory Online as a separate tool; the help desk feature list contains no asset module.

• No 1:1 device custody: no check-out to a student, no due dates, no overdue handling, no parent-signed agreement, no loaner pool, and no lost or stolen lifecycle.

  Basis: Absent from both the Cloud Help Desk and Inventory Online product pages; Inventory is network-discovery based rather than assignment based.

• No SIS or rostering integration — no OneRoster, Clever, or ClassLink — and no student, guardian, or family concepts. The vendor's own pricing language calls end users employees.

  Basis: None appear anywhere on the Spiceworks site; the Premium pricing footnote is written in terms of active employees.

• No repair records, no parts inventory, no student fees, no purchase orders, no funding-source tracking, and no asset warranty tracking. Contracts Tracker covers vendor contract expiry, which is adjacent but not the same thing.

  Basis: All absent from the published feature lists of the help desk and its companion tools.

• No ChromeOS, Google Admin, Intune, or Jamf ingest. Inventory Online scans your local network for Windows machines, Macs, and printers, which is the wrong shape for a Chromebook fleet that mostly is not on your network.

  Basis: No MDM connector is named anywhere on the Spiceworks site; Inventory Online is agent and IP-scan based.

• The product's history includes a discontinuation that left customers with nowhere to go: the self-hosted Spiceworks Desktop edition, which combined help desk and inventory, reached end of life and was removed, pushing everyone onto the ad-supported cloud. There is no self-hosted option today.

  Basis: Widely documented across independent sources; the vendor has removed the product pages entirely. The current tool set is cloud-only.

• The business model is advertising — the vendor states plainly that tech vendors reach its audience through targeted advertising, and going ad-free requires the paid plan. Some districts have procurement or privacy policies that make an ad-funded tool a hard conversation.

  Basis: Stated on Spiceworks' own Inventory product page; ad-free is listed as a Premium-only feature.

How Chalk compares with Spiceworks Cloud Help Desk →

The third option: Chalk

If you are weighing osTicket against Spiceworks Cloud Help Desk, 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.