Comparison
HappyFox Help Desk vs osTicket
Two tools districts shortlist for device tracking and IT operations, compared the way a buying committee actually reads them: what each is, what each does well, and what to check before signing. We build Chalk, a third option in this space — that context is worth knowing as you read, and it is why every claim below carries its basis.
HappyFox Help Desk
A polished multi-channel help desk sold per agent, with a genuine education landing page and Google Endpoint and Jamf integrations — but the vendor says plainly it is the service layer, not an SIS or an MDM.
Where HappyFox Help Desk is strong
- A mature, well-designed ticketing product with the full table stakes done properly: email-to-ticket, self-service portal, knowledge base, SLAs, canned responses, automation rules, and reporting.
- Real multi-department structure — IT, Facilities, HR, and Student Services can hold separate queues with routing by campus and issue type while leadership keeps one view across them.
- Integrations with Google Endpoint Management and Jamf that attach device data to a ticket, so a technician sees the machine alongside the request.
- An unlimited-agent pricing model as an alternative to per-seat, which is unusual and genuinely useful for a district where lots of people touch tickets occasionally.
- Named K-12 and higher-ed deployments on the vendor's education page, including a district handling 25,000+ tickets a year — this is not a corporate tool with an education stock photo bolted on.
- Asset management exists in the HappyFox product family, tracking assets across IT, facilities, and HR from procurement to retirement.
What to check before you buy
-
Hosted SaaS only. There is no self-hosted or on-premises edition, so the software cannot be run on district infrastructure or inspected independently.
Basis: HappyFox publishes only cloud plans; no self-host or source distribution appears anywhere on the vendor site.
-
Asset management is documented as a HappyFox Service Desk feature, and on the help desk side asset tracking lands on the higher-priced tier rather than the entry plan — so the districts most likely to be price-sensitive are the ones who do not get it.
Basis: HappyFox's asset management feature page is published under Service Desk; the vendor's pricing announcement puts the top per-agent tier at $99 per agent.
-
Per-agent pricing is the wrong axis for a district. A K-12 IT shop has a handful of technicians and tens of thousands of devices, so the bill is set by the number you have least of while the number you have most of goes untracked.
Basis: Vendor pricing is stated as a monthly price per support agent actively managing tickets.
-
The vendor states directly that HappyFox is the service layer and not an SIS or MDM replacement. Device and roster truth has to live somewhere else, and you maintain the seam between the two systems.
Basis: Stated in those terms on HappyFox's education solutions page.
-
No SIS or rostering integration — no OneRoster, Clever, ClassLink, PowerSchool, Infinite Campus, or Skyward. Users arrive from a directory, not from the system of record, so a mid-year transfer or withdrawal is invisible.
Basis: None appear on HappyFox's education page, integrations listing, or pricing page.
-
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.
Basis: Absent from the published asset management feature page, which is framed around lifecycle from procurement to retirement rather than custody.
-
No student fee assessment, no family balances, no purchase orders, no repair records consuming parts stock, and no funding-source tracking for ESSER, Title, or E-Rate money.
Basis: None of these concepts appear in HappyFox's published product documentation.
-
It consumes SSO but is not an identity provider — it cannot issue SAML or OIDC to your other vendors, and it cannot give students a portal identity.
Basis: SSO is described as sign-in into HappyFox; no IdP capability is published.
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.
The third option: Chalk
If you are weighing HappyFox Help Desk 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.
See all three on your own roster.
Chalk installs to a populated inventory in about 30 minutes. Self-host free under AGPL-3.0, or let us run it — priced by fleet size, never per seat.