Comparison
Freshdesk 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.
Freshdesk
Freshworks' customer-support help desk — the half of the catalog with no asset management at all, often bought by districts who meant to buy Freshservice.
Where Freshdesk is strong
- Very fast to stand up. A district can go from a shared inbox to a real queue with SLAs, automations, and a branded portal in an afternoon, with no server and no consultant.
- Genuinely good ticketing fundamentals: email-to-ticket, self-service portal, knowledge base with versioning and multilingual articles, SLA policies with escalation, time- and event-triggered automations, and custom dashboards.
- The omnichannel track is broad for the money — WhatsApp, Facebook Messenger, Instagram, LINE, Microsoft Teams, and Slack alongside email and chat.
- Freddy AI Copilot and AI Agent are real, shipping capabilities for deflection and agent assistance, with 500 agent sessions included on paid plans before metering starts.
- A well-documented REST API covering tickets, contacts, agents, knowledge base articles, satisfaction ratings, custom objects, and time entries, plus a marketplace of prebuilt apps.
- Day passes let an occasional agent — a building tech who works two tickets a week — be covered for $2 to $12 instead of a full seat.
What to check before you buy
Freshdesk has no asset management, no CMDB, no change management, and no ITIL process at all. That is not an oversight — it is a customer-support product, and Freshworks sells IT asset management in a different product entirely.
Basis: Freshworks' own Freshdesk-versus-Freshservice comparison page positions Freshdesk for 'customer service' and Freshservice for 'ITSM, ITOM, and ITAM.' No asset or CMDB feature appears on any Freshdesk page.
Getting tickets and Chromebook inventory from Freshworks means buying two products. Freshservice is a separate per-agent subscription with its own asset-unit metering, so the district ends up with two bills and two systems that do not share a record.
Basis: Freshworks sells and prices Freshdesk and Freshservice separately; Freshservice's own pricing meters ITAM asset units apart from agent seats.
No SIS or rostering integration — no OneRoster, Clever, ClassLink, PowerSchool, Infinite Campus, or Skyward — and no student, guardian, or family concepts. The end-user primitive is a CRM-style contact.
Basis: None are advertised in the Freshworks app marketplace for Freshdesk, whose listed apps are general business tools. Treat as 'none published' rather than proven absent — the marketplace search is client-side and not fully crawlable.
No 1:1 device custody anywhere in the product: no check-out to a student, no due dates, no overdue handling, no parent-signed agreement, no loaner pool, no lost or stolen lifecycle, and no damage fees.
Basis: All absent from the Freshdesk feature pages, which cover channels, ticketing, knowledge, and reporting only.
The free plan is no longer a durable option. It is capped at two agents, expires after six months, and is excluded from the omnichannel track — so a district that starts free has a clock running.
Basis: Freshworks' own support article on the Freshdesk free program states the two-agent limit, the six-month duration, and the exclusion from the omnichannel product.
Getting chat and social costs roughly $10 to $30 more per agent per month than the headline, because they live on a separate product track rather than a higher tier of the same one.
Basis: Freshworks publishes two pricing pages: the Freshdesk track at $19/$55/$89 and the omnichannel track at $29/$79/$119.
End-user portal SSO is gated to the Pro and Enterprise tiers. A district on the entry plan cannot sign staff or students into the self-service portal with district credentials at all.
Basis: Freshworks' documentation on custom portal SSO policies lists the capability as available on Pro and Enterprise on both tracks.
It consumes SSO but is not an identity provider. It accepts SAML, OAuth 2.0, OIDC, and JWT from your IdP; it cannot issue identity to your other vendors or give students a portal identity of their own.
Basis: Freshworks' SSO documentation describes Freshdesk as a service provider configured against an external IdP such as Entra, Okta, or Google.
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 Freshdesk 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.