AssetTiger vs Destiny Resource Manager

AssetTiger

The cheapest per-asset tracker a district will find, with no feature gating and unlimited users — and no ticketing, no roster, and no way to see a Chromebook that did not arrive on a spreadsheet.

Where AssetTiger is strong

• ● The lowest per-asset cost in this comparison by a wide margin, on a clean single meter.
• ● No feature gating between paid tiers — the vendor states explicitly that you upgrade to track more assets, not to unlock capabilities. That is unusually honest packaging and worth conceding.
• ● Unlimited users on every paid plan, so every building secretary and tech can have an account for free.
• ● Native iOS and Android apps with barcode and QR scanning, plus label printing from any printer — from a company whose main business is asset tags.
• ● Check-in and check-out with due dates and overdue alerts, which is more custody machinery than most trackers at this price.
• ● Deep reporting for the category — a large library of report types and a very granular permission model.

What to check before you buy

• No ticketing or help desk of any kind, and no connectors to one. A district running AssetTiger buys or keeps a separate service desk, and the two never see each other.

  Basis: No ticketing capability or integration appears anywhere in AssetTiger's feature list.

• No MDM or device-management ingest at all — nothing pulls from Google Admin, Intune, or Jamf. Every Chromebook enters by CSV import or by hand, and nothing detects a device you did not know about.

  Basis: AssetTiger publishes no MDM connectors; this is the largest functional gap for a Chromebook district.

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

  Basis: None appear in AssetTiger's features or integration documentation.

• No parent e-signature on a device agreement and no student fee assessment or family balances, so damage at collection time is handled outside the system.

  Basis: Absent from AssetTiger's documented feature set.

• Fund tracking exists, but it is generic budget allocation rather than grant-program aware — it will not produce the ESSER, Title, or E-Rate attribution an audit asks for without you building the structure by hand.

  Basis: AssetTiger lists a fund-tracking feature with a per-plan cap; no grant-program or funding-source-restriction concepts are documented.

• The weakest identity story in this comparison: two-factor plus Google SSO only, with no evidence of SAML support, and certainly no ability to act as an identity provider itself.

  Basis: AssetTiger's feature list names 2FA and Google SSO; no SAML or OIDC support is documented.

• The free plan is a 30-day trial, not a free tier. After it lapses the account is view-only, and it is limited to two users during the trial.

  Basis: AssetTiger's pricing table labels that column a free 30-day trial; third-party review sites still repeat a legacy free-forever claim that the vendor's page contradicts.

• Stock inventory is a separate paid add-on, and there is no documented link between it and repair records, so consuming a part against a specific repair is not a supported workflow.

  Basis: Inventory is listed and priced as an add-on; no repair-to-parts linkage appears in the documentation.

How Chalk compares with AssetTiger →

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 →

The third option: Chalk

If you are weighing AssetTiger against Destiny Resource Manager, 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.