Destiny Resource Manager vs Snipe-IT

Destiny Resource Manager

Follett's district resource-tracking system, part of the Destiny suite, used to manage technology devices alongside textbooks, curriculum materials, and other non-library resources, with bidirectional MDM sync and an optional help desk.

Where Destiny Resource Manager is strong

• ● The strongest permission model in the K-12 asset field: roughly 69 discrete Resource Manager permissions spanning search, resource management, circulation, fines, fees, and administration, with add, edit, delete, and duplicate as separate grants.
• ● Two-tier district and site administration — access levels definable by the district administrator, a site administrator, or both, with district settings pushed out and enforced district-wide or selectively.
• ● Resource Groups provide a second, orthogonal scoping axis, so access is bounded both by permission and by branch of the district's shared resource tree.
• ● Offline-capable mobile scanning through the Destiny Back Office app on iOS and Android, plus Follett's own VersaScan handheld and PocketScan Bluetooth scanner. Both inventory and circulation work offline, with SSO and multi-site switching without re-authenticating — the only offline-capable option in this comparison.
• ● Genuine bidirectional MDM sync across Google Workspace, Intune, and Jamf Pro, with rule-driven write-back that can change device state or organizational unit based on actions taken in Destiny.
• ● Digital Signature Agreements that hard-block checkout when unsigned, map agreements to resource type, patron persona, and site, can require a signature on every checkout, and ship Block Overrides and Needs Signature compliance reports.

What to check before you buy

• No warranty field is documented. The Add/Edit Item field list runs from Status and Condition through Purchase Price, Purchase Order, Funding Source, and Projected Life without a warranty field anywhere in it; Date Acquired plus Projected Life models asset life and depreciation, not warranty end.

  Basis: the complete documented item field list in Follett's own help docs

• Purchase order support is a plain text field on the item record — the docs describe it as the PO number used for the items. There is no approval routing, no line items, and no vendor records. The separate Resource Orders module is internal district-warehouse fulfillment with pick lists and shipments, not external procurement.

  Basis: Follett help documentation for item fields and the Resource Orders module

• No native OneRoster, Clever, or ClassLink rostering is documented. Rostering is a nightly patron import via CSV with XSLT transform files. ClassLink and Okta appear only as SSO providers for Destiny Help Desk, never as roster sources.

  Basis: Follett patron import documentation; absence of any documented rostering connector in public docs

• No parts inventory and no repair-cost tracking in native help tickets — tickets carry priority, status, expected completion date, notes, assignment, and reopen, and nothing about the money or materials a repair consumed.

  Basis: Follett help desk ticket documentation

• No insurance or protection-plan object. Insurance is modeled as a generic fee, with no coverage terms, claims workflow, deductibles, per-incident tracking, or renewals.

  Basis: Follett documents insurance as an intended use of the generic fee type

• Digital Signature Agreements is described by Follett as a hosted cloud app requiring an external internet connection, and Destiny AI is available only to hosted customers. A district running Destiny on-premises or air-gapped cannot have either at any price.

  Basis: Follett product documentation stating the hosted-cloud requirement

• Destiny Help Desk is a paid subscription add-on that additionally requires Resource Manager 22.5 or later with Unified Navigation enabled, so older on-premises installs cannot adopt it without upgrading first.

  Basis: Follett add-on packaging and stated version floor

• The native fee 'Pay' permission records a payment rather than processing one. Actual online collection requires Destiny Fee Manager, a separate Stripe-powered product whose best parent-portal experience additionally depends on Follett's own Aspen SIS.

  Basis: Follett Fee Manager product documentation

How Chalk compares with Destiny Resource Manager →

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 Destiny Resource Manager 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.