osTicket vs SysAid

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 →

SysAid

A capable ITSM suite with real asset discovery and a working Chromebook sync — priced at $89 per agent, positioned at universities rather than districts, and quietly steering its on-premises line toward the exit.

Where SysAid is strong

• ● A full ITSM process set for the price: incident, request, problem, and change management, SLAs, a self-service portal, knowledge base, workflow automation, dashboards, and a developer API.
• ● Genuine IT asset management, not a bolt-on — automatic network discovery, hardware and software inventory, a CMDB with configuration-item relationship mapping, software license management with renewal reminders, patch deployment, and remote control through Splashtop.
• ● A real Chromebook integration that pulls from Google Workspace: model, serial, Chrome version, enrollment time, warranty expiry, asset ID, organizational unit, policy sync status, and CPU, memory, and disk. Most general-purpose help desks have nothing like it.
• ● SysAid Copilot is included in the published tier rather than sold as a per-agent add-on, covering both agent assistance and an end-user chatbot grounded on your tickets, knowledge base, and documents.
• ● Strong independent review standing — 4.5 out of 5 across 522 Capterra reviews, with automation, integrated asset management, and responsive support named repeatedly as strengths.
• ● SysAid handled its 2023 zero-day well: it learned of the issue on 2 November, published an advisory with indicators of compromise on 8 November, and shipped a fixed release. That is the behavior you want from a vendor.

What to check before you buy

• 250 managed assets are included at $89 per agent. A 1:1 district counts devices in the thousands, so the fleet becomes a negotiated line item immediately — the one axis a district has most of.

  Basis: SysAid's pricing page lists 'Managed assets (250 included)' under the Professional plan, with no published rate for additional assets.

• The education positioning is higher education, not K-12. The customer logos on both education pages are universities, and the claims are framed around students, faculty, and campus asset variety.

  Basis: SysAid's higher-education and service-desk-for-education pages name University of Michigan, University of Toronto, Queen's University, and University of West London. Neither page mentions school districts.

• No SIS or rostering integration — no OneRoster, Clever, ClassLink, PowerSchool, Infinite Campus, or Skyward — and no student or guardian data model. Identity sync is enterprise-shaped: Entra, Google Workspace, Okta, ADFS, CAS, Shibboleth, OneLogin.

  Basis: None appear on either education page or in SysAid's integration catalog; the user repositories SysAid documents are corporate directories.

• The Chromebook integration reads, it does not write, and its user handling is shallow — it maps the most recent recent-user into an Owner field. There is no OU move, no disable, no deprovision, and no annotated-field write-back.

  Basis: SysAid's own Chromebook documentation describes a one-way pull from Google Workspace inventory and the recent-user-to-Owner mapping; the catalog entry is titled Chromebook (Beta).

• No device check-out to a person as a transaction. Ownership is a synced field, not a custody event, so there are no due dates, no overdue list, no parent-signed agreement, no loaner pool, no lost or stolen lifecycle, and no damage fees.

  Basis: None of those concepts appear anywhere in SysAid's asset management documentation or marketing.

• On-premises is no longer marketed, and its feature set is visibly thinner. SysAid's own cloud-versus-on-premises comparison documents no Teams integration, no Power BI extract, no Zapier, no SSO connector, no sandbox, and mobile at extra cost — with releases two to three times a year against fortnightly on cloud.

  Basis: SysAid's published cloud-vs-on-prem comparison PDF; its on-premises plan URL now redirects to cloud pricing. We could not verify whether a new on-premises license can still be purchased — treat it as unmarketed rather than proven discontinued.

• That matters because the security history sits on the self-hosted line, where SysAid's own document says security updates are manual and performed by the customer. CVE-2023-47246 was a critical remote-code-execution flaw in SysAid On-Premise, exploited in the wild and added to CISA's Known Exploited Vulnerabilities catalog; three XXE flaws in 2025 followed, two of which also reached that catalog.

  Basis: NVD entries for CVE-2023-47246 and CVE-2025-2775, CISA KEV listings, SysAid's own advisory, and Rapid7's analysis. Fair reading: SysAid patched each promptly, and security press reports no public exploitation of the 2025 XXE issues — the durable point is patch cadence and who is responsible for applying it, not that the product is insecure.

• Recurring review themes are consistent: an interface described as dated and not very intuitive, configuration of advanced automation that is time-consuming for new administrators, and built-in reporting that most reviewers end up customizing.

  Basis: Capterra's aggregated review themes across 522 SysAid reviews. G2, TrustRadius, and Gartner Peer Insights block automated reading, so no rating from those sites is cited here.

How Chalk compares with SysAid →

The third option: Chalk

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