Why Existing Tools Can't Do This
S.O.S. competitive analysis · one page
Every incumbent either manages school-owned hardware, surveils to enforce, or removes the device entirely. None delivers school-hours control on a student's personal device with a hard privacy boundary after the bell. That combination is the product.
One system — iPhone and Android
S.O.S. is a single platform with a native client for each — one backend, one dashboard, one integrity engine. Android holds tamper-proof control even on a student's personal phone; iPhone delivers the same school-hours app and web governance through Apple's consent-based Family Controls, with full parity on school-owned devices. No student is excluded by the phone in their pocket.
Why not Microsoft Intune (for Education)?
Intune is enterprise MDM: it manages devices that are enrolled into district IT, with persistent control and broad visibility. Enrolling a child's personal phone into district MDM is exactly what families refuse — and rightly so. Intune has no concept of bell-schedule control that switches off after hours, and off-network web filtering requires routing traffic through additional agents and infrastructure. S.O.S. is the inverse: scoped, time-boxed authority on a personal device, with zero traffic proxying.
Why not Google Workspace for Education / Chromebook management?
Google's management is excellent — for school-owned Chromebooks and school Google accounts. It does nothing about the device actually causing the problem: the student's personal phone in their pocket. It also presumes districts buy, image, repair, and replace a fleet of hardware. S.O.S. requires no school hardware at all.
Why not Apple School Manager / Jamf?
Apple's education stack requires supervised devices — practically, devices the school owns and enrolled before first use. Supervision of a family-owned iPhone is not a realistic deployment path, and like all MDM it is always-on management, not a school-hours mode with a hard privacy boundary. S.O.S.'s iOS client takes the opposite route: for a student's personal iPhone it uses Apple's consent-based Family Controls — no supervision required — and reserves supervised MDM for school-owned devices, so families are never forced into always-on management.
Why not GoGuardian, Securly, Lightspeed, Bark?
Classroom-filtering tools monitor school accounts and school devices, and most enforce by proxying or inspecting browsing traffic — which is why several have drawn national privacy criticism for surveilling students. They don't govern personal devices, and their architecture is the opposite of data minimization. S.O.S. never sees browsing traffic in either mode; enforcement happens on the device and only the blocked domain name is ever logged.
Why not phone pouches (Yondr) or collection caddies?
Physical lockup removes the distraction and the educational value. It costs per-student per-year, creates daily friction and loss/damage disputes, and gives teachers no instructional control. S.O.S. turns the same phone into the lesson device instead of confiscating it.
Can't a student just turn on a VPN to escape School Mode?
This is the question that sinks naive filters — and it's exactly what S.O.S. is built to defeat. S.O.S. is a Network Integrity and Gateway Enforcement System: every device is scored 0–100 across five layers — IP reputation (VPN/proxy/TOR/datacenter via a commercial feed, with a confidence score, not a binary flag), device attestation (Android Play Integrity; root/emulator/tamper), network-behavior analysis (rapid IP changes, impossible transitions, repeated bypass attempts), and school-gateway verification. A device that hides behind a VPN or fails attestation drops into Suspicious or Restricted and is held, restricted, or blocked per the school's policy. Enforcement is also on-device, so dropping school Wi-Fi for cellular changes nothing.
At a glance
| Capability | S.O.S. | Intune EDU | Google EDU | Jamf / ASM | Filter tools | Pouches |
|---|---|---|---|---|---|---|
| Works on student-owned devices | ✓ | △ | ✗ | ✗ | △ | ✓ |
| No school hardware to buy | ✓ | △ | ✗ | ✗ | △ | ✗ |
| Time-boxed control — auto-returns to personal | ✓ | ✗ | ✗ | ✗ | ✗ | △ |
| Hard privacy boundary outside school hours | ✓ | ✗ | ✗ | ✗ | ✗ | ✓ |
| Off-network enforcement without proxying traffic | ✓ | ✗ | ✗ | ✗ | ✗ | — |
| Domain-only logging, no browsing history | ✓ | ✗ | △ | △ | ✗ | — |
| Teacher-level classroom session control | ✓ | ✗ | △ | △ | ✓ | ✗ |
| Device stays usable for instruction | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
△ = partial / only with significant caveats (e.g., BYOD enrollment families resist, or school-account-only coverage).