One to One Plus vs Reftab

One to One Plus

A K-12 asset management and help desk platform focused on 1:1 device programs, sold as a single subscription with all core features included and an actively developed native mobile app on both iOS and Android.

Where One to One Plus is strong

• ● A genuinely strong native mobile app on both iOS and Android, using the phone camera as the scanner with no hardware sled — assignment and collection, full ticket create/update/close, photo and video damage capture, and adding or removing parts with a live availability check. It is actively developed, with Face ID login, in-ticket attachments, and mobile-only ticket forms all shipping within the last year or so.
• ● The only product in this comparison with native insurance program management: coverage applied to eligible incidents, claim status and coverage limits tracked, and approved claims offsetting invoice balances. Premiums are a charge type and insurance forms are an e-signature document type.
• ● Simple, honest packaging — one subscription, all core features, no module upsells. Among K-12 asset vendors that is genuinely uncommon and removes a whole category of procurement surprise.
• ● More than a dozen named integrations covering SIS (Infinite Campus, PowerSchool, Skyward, Ascender), MDM (Google Admin, Microsoft Intune, Mosyle, Jamf Pro, PDQ Deploy), identity (Active Directory plus Google and Microsoft SSO), and payments (MySchoolBucks, Rycor).
• ● Purpose-built end-of-year tooling: bulk turn-in for large-scale collection, cart, room, and inventory-area location granularity, and building-level audit reconciliation sheets.
• ● Funding source works as both a field and an audit dimension, with Title I and E-Rate named, plus e-signatures for agreements, AUPs, handbooks, and insurance forms, and scheduled report email delivery.

What to check before you buy

• No purchase order or receiving workflow. The asset record carries passive procurement metadata such as vendor details and purchase dates, but there is no PO object, approval routing, or receive-against-PO step.

  Basis: verified three ways — no PO page, no site search hit, and absent from the vendor's own module overview

• No parent-facing portal. Families are reached by email — invoices are delivered with view tracking — and when a family pays, that happens on the third-party processor's site rather than in One to One Plus. A staff and student self-service ticket portal does exist; the gap is specifically family-facing.

  Basis: vendor invoices and payments documentation describes email delivery plus third-party payment

• No Clever, ClassLink, or OneRoster support is listed among their published integrations — rostering runs through direct per-vendor SIS connectors instead.

  Basis: vendor integrations page, which names no rostering standard or roster broker

• Payment collection is entirely third-party — MySchoolBucks and Rycor are the named processors — so the fee record and the money live in different systems.

  Basis: vendor integrations and payments pages name MySchoolBucks and Rycor

• Warranty data is stored on the asset record, but no claim workflow, expiration alerting, or vendor RMA process is documented.

  Basis: vendor asset management documentation treats warranty as an asset attribute

• Reporting depth is a recurring theme in reviewer feedback despite the product shipping a report builder — buyers appear to judge this area harshly.

  Basis: recurring theme in public review-site feedback

• Hosted SaaS only — there is no self-hosted or on-premises option and no source availability.

  Basis: vendor sells a hosted subscription with no self-host offering published

• MDM integration is ingest-oriented: device data is imported and kept in sync, with no documented reviewed write-back of OU moves, disables, or deprovisions into Google Admin.

  Basis: vendor integrations page describes device data being imported, updated, and synced into the platform

How Chalk compares with One to One Plus →

Reftab

A well-designed asset tracker with a real free-forever tier, self-serve signup, and no sales call — and, like the rest of its class, no help desk, no roster, and no student.

Where Reftab is strong

• ● The only genuinely free-forever tier in this comparison, and a generous one — unlimited custom fields and locations, reservations with calendars, advanced reports with export, mobile apps, and barcode check-in/check-out at no cost.
• ● SSO and two-factor authentication at the lowest paid tier rather than gated to enterprise, which is unusual and district-friendly.
• ● Unlimited platform users on every tier, so the bill never grows because you added staff.
• ● Native iOS and Android apps with barcode scanning, plus a barcode designer and custom email templates.
• ● Strong MDM breadth at the top tier — Intune, Jamf Pro and Jamf School, Kandji, Mosyle, NinjaOne, FleetDM, and Apple Business Manager — plus vendor warranty sync from Dell, CDW, Lenovo, and Apple.
• ● A Google Workspace integration that imports Chromebooks and mobile devices daily, with configurable field mapping and optional auto-assignment to the Google-assigned user.

What to check before you buy

• No native help desk or ticketing with SLAs. Jira Cloud and Zendesk connectors exist to surface assets on someone else's ticket, and they are top-tier features — so a district buys a service desk separately either way.

  Basis: Reftab's integration listing offers Jira and Zendesk plugins rather than native ticketing; no SLA capability appears in any tier.

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

  Basis: None appear in Reftab's integration catalog or documentation; the identity integrations are corporate directories.

• Signature capture is staff-side custody acknowledgement, not a parent or guardian e-signature on a device agreement, and it sits behind a mid-tier upgrade.

  Basis: Reftab lists signature capture as a Pro-tier feature; no guardian entity or agreement workflow exists in the data model.

• No student fee assessment and no family balances, so damage recovered at collection time is tracked outside the system.

  Basis: Absent from Reftab's documented feature set across all tiers.

• No funding-source or grant tracking for ESSER, Title, or E-Rate attribution.

  Basis: No funding-source dimension appears in Reftab's documentation.

• ChromeOS support is import only and syncs once daily. Nothing writes back, so OU moves and disabling a stolen Chromebook remain manual work in Google Admin.

  Basis: Reftab's Google Workspace integration guide documents a daily one-way import with field mapping; no write-back is described.

• The MDM connectors that make the inventory self-maintaining — Intune, Jamf, Kandji, Mosyle, Apple Business Manager — are all top-tier features, which is a meaningful jump from the tier where SSO lives.

  Basis: Reftab's pricing page places all MDM, vendor, and IdP integrations at the Business tier.

• It consumes SSO but is not an identity provider. Okta, Entra ID, SAML 2.0, SCIM, and LDAP are identity it reads, not identity it issues — and the IdP user-provisioning integrations are top-tier only.

  Basis: Reftab is configured as a service provider against an external IdP; provisioning integrations are listed at the Business tier.

How Chalk compares with Reftab →

The third option: Chalk

If you are weighing One to One Plus against Reftab, 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.