Reftab vs Snipe-IT

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 →

Snipe-IT

A mature, genuinely free open-source IT asset manager — it tracks the Chromebook well, but it has no help desk, no roster, and no idea which student is holding it.

Where Snipe-IT is strong

• ●Genuinely free to self-host, AGPL-3.0, with no crippled community edition and no per-asset or per-seat meter at any tier.
• ●Publishes every hosted price openly with no 'contact sales' gate — rare enough in K-12 procurement that it deserves saying out loud.
• ●Over a decade of production asset tracking behind it, with releases every few weeks and a very large install base.
• ●Real identity plumbing for an asset tracker: SAML login, LDAP and Google Secure LDAP user sync, and SCIM auto-provisioning.
• ●Genuine asset-lifecycle depth — checkout/checkin with optional acceptance, asset history, audits, custom fields, requestable assets, and three documented depreciation methods.
• ●Tracks more than hardware: components, consumables, accessories, and software licenses with expiring-license and expiring-warranty email alerts.

What to check before you buy

• No help desk or ticketing of any kind. A district running Snipe-IT still buys a service desk somewhere else, and the two systems never see each other.

  Basis: Absent from the vendor's product page; the feature request on the project's issue tracker has been open since 2015, and the documented answer is to integrate an external tool such as osTicket or Zendesk.

• No SIS or rostering integration — no OneRoster, Clever, ClassLink, PowerSchool, Infinite Campus, or Skyward. Students arrive by CSV, usually exported by hand each August.

  Basis: None of these appear anywhere in Snipe-IT's product page or documentation.

• No student, guardian, or family concepts. Everyone is a 'user' with a free-text field, so a device cannot know the student's school, grade, or enrollment, and a transfer or withdrawal is invisible to the system.

  Basis: Snipe-IT's data model has users, not students; no guardian or enrollment entity exists in the documentation.

• It consumes SSO but is not itself an identity provider. It cannot issue SAML or OIDC to your other vendors, and cannot give students a portal login.

  Basis: Snipe-IT's SAML documentation describes it exclusively as a service provider consuming Entra ID, Google Workspace, Okta, OneLogin, or JumpCloud.

• No purchase orders, and no funding-source or grant tracking. There is a purchase-order-number text field, but nothing that would let you answer which devices ESSER, Title, or E-Rate paid for.

  Basis: Only an order-number field appears in the docs; purchase orders are a long-standing open feature request, and no funding-source concept exists.

• Consumables and components exist, and maintenance records exist, but they are not linked — you cannot consume a part out of stock against a specific repair.

  Basis: No documented linkage between the consumables and asset-maintenance features.

• No native mobile app and no camera scanning from the vendor. The web UI is mobile-friendly and works with handheld scanners; every native scanning app is a third-party API client the project explicitly does not support.

  Basis: Vendor documentation states third-party projects are unsupported and to use them at your own risk.

• No MDM ingest at all — nothing pulls from Google Admin, Intune, or Jamf, and nothing writes back. The vendor confirms there is no network agent and points at the REST API instead.

  Basis: Snipe-IT's FAQ: 'We don't currently provide a network agent, however we do have a robust REST API that can be integrated with agents if you know a little programming.'

How Chalk compares with Snipe-IT →

The third option: Chalk

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