Comparison
Destiny Resource Manager vs Sortly
Two tools districts shortlist for device tracking and IT operations, compared the way a buying committee actually reads them: what each is, what each does well, and what to check before signing. We build Chalk, a third option in this space — that context is worth knowing as you read, and it is why every claim below carries its basis.
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
Sortly
The friendliest inventory app in this comparison and the easiest to actually start using — built for supply closets and job sites, priced by how many items you have, which is exactly the wrong meter for a 1:1 fleet.
Where Sortly is strong
- Every price is on the page, including a genuinely free tier, with no demo gate anywhere in the funnel.
- The lowest adoption cost in this comparison by a distance: folders, tags, photos and custom fields, usable by a building secretary in an afternoon without an IT project behind it.
- Strong mobile — iOS and Android with offline access, barcode and QR scanning, and label generation from inside the same app, so counting is a phone job rather than a scanner-hardware purchase.
- Alerting that fits consumables well: low stock alerts for reordering and date-based alerts for maintenance and repair schedules, with in-app and email notification.
- More reporting than the price suggests — activity history, inventory summaries, user activity, low stock and item-flow reports, saved custom reports, and report subscriptions delivered on a schedule.
- Real integration surface for a product this simple: webhooks, an API, QuickBooks Online, and Slack and Microsoft Teams notifications, plus purchase orders, pick lists, and check-in and check-out.
What to check before you buy
-
Pricing meters unique items, and a 1:1 district's item count is its student count. At 5,000 items the published tier is $299 per month, and anything past 10,000 items is Enterprise quote-only — a mid-sized district is off the published ladder on device count alone.
Basis: Vendor pricing page item limits: 100 free, 500 Advanced, 2,000 Ultra, 5,000 Premium, 10,000+ Enterprise.
-
User licenses are metered too, and tightly: 1 user free, 2 on Advanced, 5 on Ultra, 8 on Premium. A technician team plus building staff crosses into Enterprise quickly.
Basis: Vendor pricing page user-license limits per tier.
-
No help desk or ticketing of any kind. A district running Sortly still buys a service desk somewhere else, and the two never see each other.
Basis: Absent from the vendor's published feature list, which covers inventory, alerts, reporting and integrations.
-
No MDM or device integrations at all. The published integration list is QuickBooks Online, Slack, Microsoft Teams, webhooks and an API — so ChromeOS, Intune and Jamf data is typed or imported, and serials go stale between imports.
Basis: Vendor features page lists no device-management or directory connectors.
-
No SIS or rostering integration and no student, guardian or enrollment concepts — nothing notices a transfer, a withdrawal or grade rollover.
Basis: Absent from the vendor's feature list and from its industry positioning, which addresses inventory rather than student records.
-
Check-in and check-out is item custody, not a school-year loan: no due dates on a student device agreement, no e-signature, no damage fee, no family balance and no loaner pool workflow.
Basis: Vendor documents check-in/check-out alongside pick lists and stock tracking, with no agreement or fee concepts published.
-
It is an inventory product rather than an IT asset lifecycle product — warranty expiry, depreciation, ChromeOS auto-update expiration and refresh planning are not in the published feature set, though generic date-based alerts can approximate some of it.
Basis: Vendor features page covers custom fields, alerts and reports; no warranty, depreciation or lifecycle module is published.
-
Hosted SaaS only, with no self-hosted option, and no SSO or SAML in the published feature list — so it sits outside your single sign-on estate in both directions.
Basis: No self-host or source distribution is offered on the vendor site, and SSO does not appear on the features or pricing pages.
The third option: Chalk
If you are weighing Destiny Resource Manager against Sortly, 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.
See all three on your own roster.
Chalk installs to a populated inventory in about 30 minutes. Self-host free under AGPL-3.0, or let us run it — priced by fleet size, never per seat.