Destiny Resource Manager vs SolarWinds Web Help Desk

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 →

SolarWinds Web Help Desk

A long-serving on-premises help desk with unlimited end users and a fair per-technician price — and a rewritten 2026 release that means a migration project either way.

Where SolarWinds Web Help Desk is strong

• ● Genuinely on-premises and self-hosted, positioned by the vendor as requiring no cloud dependency — which matters to districts with data-residency or board-policy constraints.
• ● Unlimited end users at every license tier. You pay for technicians only, which is genuinely favorable for a district with thousands of staff and a handful of techs.
• ● Fully published, transparent pricing with no quote gate — competitively unusual.
• ● Integrated asset management with ticket-to-asset linking and asset service history, so a technician sees the device from the ticket.
• ● LDAP and Active Directory sync plus documented SAML 2.0 SSO against AD FS, Okta, Google, and Entra ID.
• ● A modernized 2026 release line — a redesigned interface across 120+ screens, a security-hardened rebuild, and a published forward roadmap including Teams and Slack integrations and AI ticket summaries.

What to check before you buy

• If you are still on the 12.x line, you have a forced migration ahead: SolarWinds has published End-of-Life dates for versions 12.4 through 12.8, and the replacement is a rewritten application, so it means retraining as well as an upgrade.

  Basis: SolarWinds' own release-history page publishes End-of-Engineering and End-of-Life dates for the 12.x versions and instructs customers to transition to the current release; the 2026.2 notes describe a completely redesigned interface across 120+ screens.

• No SIS or rostering integration — no OneRoster, Clever, ClassLink, or PowerSchool. Identity comes from LDAP, Active Directory, and SAML only.

  Basis: None appear on SolarWinds' Web Help Desk product pages, education use-case page, or documentation; the documented identity story is explicitly directory-based.

• No student or guardian concepts. Students appear only as ticket submitters — there is no enrollment, no grade, no guardian, and nothing that reacts to a transfer or a withdrawal.

  Basis: SolarWinds' education page describes students, faculty, and staff purely as end users submitting tickets.

• No 1:1 device circulation — no due dates on a student's device, no overdue workflow, no e-signed agreement, no loaner pool, and no lost or stolen lifecycle. Asset reservations are the nearest adjacent feature.

  Basis: Web Help Desk's asset management is framed around IT inventory such as projectors and instrumentation; no custody loop appears in the documentation.

• No student fee assessment or family balances. The parts-and-billing concepts in the product are IT cost accounting, not student charges.

  Basis: No fee, charge, or student-ledger concept appears in the product documentation.

• No funding-source or grant tracking — nothing to attribute devices to ESSER, Title, or E-Rate.

  Basis: No such concept appears anywhere in the product documentation.

• No ChromeOS or Google Admin device ingest surfaced. Discovery is network- and directory-oriented, so Chromebooks arrive by import or by hand.

  Basis: No Google Workspace or ChromeOS device-ingest integration appears in SolarWinds' Web Help Desk documentation or integration listings.

• It consumes SSO but is not an identity provider. It cannot issue SAML or OIDC outward, and cannot give students a portal identity.

  Basis: SolarWinds' authentication documentation configures Web Help Desk as a SAML 2.0 service provider against an external IdP.

How Chalk compares with SolarWinds Web Help Desk →

The third option: Chalk

If you are weighing Destiny Resource Manager against SolarWinds Web Help Desk, 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.