osTicket vs Reftab

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 →

Reftab

A well-designed asset tracker with a real free-forever tier, self-serve signup, and no sales call — and, like the rest of its class, no help desk, no roster, and no student.

Where Reftab is strong

• ● The only genuinely free-forever tier in this comparison, and a generous one — unlimited custom fields and locations, reservations with calendars, advanced reports with export, mobile apps, and barcode check-in/check-out at no cost.
• ● SSO and two-factor authentication at the lowest paid tier rather than gated to enterprise, which is unusual and district-friendly.
• ● Unlimited platform users on every tier, so the bill never grows because you added staff.
• ● Native iOS and Android apps with barcode scanning, plus a barcode designer and custom email templates.
• ● Strong MDM breadth at the top tier — Intune, Jamf Pro and Jamf School, Kandji, Mosyle, NinjaOne, FleetDM, and Apple Business Manager — plus vendor warranty sync from Dell, CDW, Lenovo, and Apple.
• ● A Google Workspace integration that imports Chromebooks and mobile devices daily, with configurable field mapping and optional auto-assignment to the Google-assigned user.

What to check before you buy

• No native help desk or ticketing with SLAs. Jira Cloud and Zendesk connectors exist to surface assets on someone else's ticket, and they are top-tier features — so a district buys a service desk separately either way.

  Basis: Reftab's integration listing offers Jira and Zendesk plugins rather than native ticketing; no SLA capability appears in any tier.

• No SIS or rostering integration — no OneRoster, Clever, ClassLink, or PowerSchool — and no student, guardian, or family concepts. Nothing reacts to a transfer, a withdrawal, or grade rollover.

  Basis: None appear in Reftab's integration catalog or documentation; the identity integrations are corporate directories.

• Signature capture is staff-side custody acknowledgement, not a parent or guardian e-signature on a device agreement, and it sits behind a mid-tier upgrade.

  Basis: Reftab lists signature capture as a Pro-tier feature; no guardian entity or agreement workflow exists in the data model.

• No student fee assessment and no family balances, so damage recovered at collection time is tracked outside the system.

  Basis: Absent from Reftab's documented feature set across all tiers.

• No funding-source or grant tracking for ESSER, Title, or E-Rate attribution.

  Basis: No funding-source dimension appears in Reftab's documentation.

• ChromeOS support is import only and syncs once daily. Nothing writes back, so OU moves and disabling a stolen Chromebook remain manual work in Google Admin.

  Basis: Reftab's Google Workspace integration guide documents a daily one-way import with field mapping; no write-back is described.

• The MDM connectors that make the inventory self-maintaining — Intune, Jamf, Kandji, Mosyle, Apple Business Manager — are all top-tier features, which is a meaningful jump from the tier where SSO lives.

  Basis: Reftab's pricing page places all MDM, vendor, and IdP integrations at the Business tier.

• It consumes SSO but is not an identity provider. Okta, Entra ID, SAML 2.0, SCIM, and LDAP are identity it reads, not identity it issues — and the IdP user-provisioning integrations are top-tier only.

  Basis: Reftab is configured as a service provider against an external IdP; provisioning integrations are listed at the Business tier.

How Chalk compares with Reftab →

The third option: Chalk

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