Comparison
Freshservice 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.
Freshservice
A polished corporate ITSM suite that districts do buy — with per-agent pricing, separately metered asset units, and no idea that your users are students.
Where Freshservice is strong
- A genuinely complete ITIL process set at the upper tiers — incident, problem, change, release, and major incident management, with a service catalog and on-call scheduling.
- Strong no-code automation: a drag-and-drop workflow automator with multi-step approvals, available on every paid tier, and orchestration with published monthly transaction limits.
- Automated discovery across on-premises, cloud, and hybrid estates, plus software license management, dependency mapping, IP address management, and DCIM.
- Freddy AI for triage, summarization, and agent assistance, with a virtual agent for deflection.
- A large integration marketplace, including a Freshworks-published connector that imports ChromeOS devices from Google Admin.
- A mature, well-designed product with real enterprise operations behind it — this is not a tool that will surprise you by disappearing.
What to check before you buy
No SIS or rostering integration of any kind — no OneRoster, Clever, ClassLink, PowerSchool, Infinite Campus, or Skyward. Students and staff arrive by directory sync or CSV, not from the system of record.
Basis: None appear on Freshworks' Freshservice education page, pricing page, or integration listings. Note that PowerSchool appears on Freshworks' site as a customer, not as an integration.
No student, guardian, or family concepts. There is no enrollment, no grade, no guardian relationship, and nothing that notices a mid-year transfer or a withdrawal.
Basis: Absent from the vendor's own education page and product documentation; the data model is employees and requesters.
Per-agent pricing collides with how districts staff a help desk. A district with a handful of technicians and tens of thousands of devices pays on the axis it has least of, then pays again on the axis it has most of.
Basis: Freshworks' published pricing is per agent per month, with ITAM asset units metered separately and additional units purchasable.
No 1:1 device circulation as a product concept — no due dates on a student's device, no overdue workflow, no loaner pool, and no lost/stolen lifecycle.
Basis: Absent from the ITAM feature documentation, which is framed around corporate asset assignment and reclamation.
E-signature exists only as a generic paid add-on sold in credit packs, not as a device-agreement workflow. Credit-metered signatures are a poor fit for a rollout that signs thousands of agreements every August.
Basis: Listed as a per-pack add-on with a fixed number of signature credits on Freshworks' pricing page.
No student fee assessment, no family balances, and no funding-source or grant tracking — nothing to tie a device to ESSER, Title, or E-Rate money.
Basis: Neither concept appears anywhere in Freshservice's product documentation or education materials.
ChromeOS ingest exists but is shallow: a one-way, once-daily import from Google Admin, published years ago with a small install base. There is no write-back — no OU moves, no disable, no annotated fields.
Basis: The Freshworks marketplace Chrome OS device discovery app describes a scheduled one-way sync; a request for two-way Google Admin sync remains open in the Freshworks community.
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: Freshworks describes SSO as allowing users to access Freshservice via an internal directory — service provider only.
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 Freshservice 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.