Comparison
Chalk vs 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.
What both do well
- Both do real write-back to MDM rather than read-only ingest — Destiny and Chalk are two of the very few K-12 asset systems that can change device state in Google, Jamf, or Intune from the asset record.
- Both offer granular, composable permissions with site-level scoping. Destiny's model is deeper than Chalk's, and its resource-tree scoping is a second axis Chalk does not have.
- Both block or gate a device handoff on a signed agreement, and both handle physical inventory audits with barcode scanning.
- Both go beyond serialized devices — Destiny through textbooks and curriculum, Chalk through quantity-tracked item classes — so unserialized stock does not need a second system.
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 Destiny Resource Manager
-
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
Where Chalk pulls ahead
- Chalk is AGPL open source and self-hosts as a single binary with every feature included. There is no Chalk configuration where running it yourself costs you e-signature or the help desk — with Destiny, an on-premises install cannot have Digital Signature Agreements or Destiny AI, and Help Desk is a paid add-on with a version floor.
- Chalk tracks warranty as a first-class field on the device, inside the ticket, and in the fleet runway report, with expiry alerting. Destiny's documented item fields contain no warranty field at all.
- Chalk's repair records carry cost and consume parts from tracked stock with low-stock alerts, so the money and materials sit on the same record as the work. Destiny's native tickets carry neither.
- Chalk syncs rosters directly from PowerSchool, Infinite Campus, Skyward, and OneRoster CSV or API, imports Clever and ClassLink, and serves a full OneRoster 1.1 API back out. Destiny's documented rostering is a nightly CSV import with XSLT transforms, and ClassLink appears only as an SSO provider.
- Chalk is an identity provider in its own right — SAML, OIDC, a portal, and QR badge sign-in — so it can be the district's SSO rather than a system that consumes one.
- Chalk's write-back to Google is a diff preview you approve item by item, with typed confirmation on destructive actions. Destiny's write-back is rule-driven and automatic, which is faster but gives you no review step before a device state changes in production.
- Chalk has purchase orders with vendors and managed funding sources as real objects rather than a PO number typed into a text field.
Common questions
Does Destiny Resource Manager track warranties?
No warranty field appears anywhere in Follett's documented item field list. The closest analogues are Date Acquired plus a Projected Life value, which model asset life and depreciation rather than warranty expiry, so districts fall back on the free-text Notes field. Chalk tracks warranty on the device, surfaces it in the ticket a technician has open, and includes it in the AUE runway report, with expiry alerts.
Can Destiny push changes back to Google Admin or Jamf?
Yes, and it is one of the better implementations in the category — rule-driven bidirectional sync across Google Workspace, Intune, and Jamf Pro, where an action in Destiny can change device state or organizational unit in the MDM. Chalk also writes back, but stages the changes as a diff you review and approve first, with typed confirmation on deprovision. That is a genuine trade: Destiny is more automatic, Chalk is more auditable.
Do we get everything if we run Destiny on-premises?
No. Follett describes Digital Signature Agreements as a hosted cloud app requiring an external internet connection, and Destiny AI is available only to hosted customers. Destiny Help Desk is a paid add-on that also requires Resource Manager 22.5 or later with Unified Navigation. Chalk's self-hosted build is the complete product — e-signature, attestation, help desk, identity, and dashboards all included under AGPL.
How does Destiny handle rostering?
Through nightly patron imports via CSV with XSLT transform files. No native OneRoster, Clever, or ClassLink rostering connector is documented; ClassLink and Okta show up only as SSO providers for Destiny Help Desk, which is a different thing. Chalk connects directly to PowerSchool, Infinite Campus, and Skyward, reads OneRoster CSV and API, imports Clever and ClassLink, and serves a OneRoster 1.1 API to other systems.
Can families pay device fines through Destiny?
Not in Resource Manager itself — its fee permission records a payment rather than processing one. Online collection requires Destiny Fee Manager, a separate Stripe-powered product, and its best parent-portal experience depends on Follett's own Aspen SIS. Chalk assesses fees, tracks per-student balances, and emails families, but deliberately never processes payments or touches card data.
Is Destiny's permission model better than Chalk's?
In depth, yes — roughly 69 composable permissions with district-to-site push and a separate Resource Groups scoping axis is the high-water mark in this category. Chalk has granular permissions with building-level scoping and two-factor authentication, which covers the common case of limiting a building tech to their own campus, but it has no equivalent of Destiny's second scoping axis.
Sources
Claims about Destiny Resource Manager above are drawn from these pages, checked when this comparison was written. If something has changed, tell us and we will correct it.
Trying Chalk beside Destiny Resource Manager?
Chalk installs to a populated inventory from your SIS and Google Admin in about 30 minutes. Self-host it free forever under AGPL-3.0, or let us run it — priced by fleet size, never per seat or per student.