Play with the real backend

The Network Integrity Engine: scoring live.

Change the signals and watch the real engine score the device. This calls the live S.O.S. backend, the same five-layer math and band to action mapping the production system uses. (Stateless: your inputs are simulated rather than server-observed, so nothing is stored.)

Engine

Quick scenarios:

IP reputation Layer 1

Play Integrity verdict Layer 2 · device attestation

Tamper signals Layer 2

Rooted

Emulator

Tampered app binary

Network & session Layers 3-4

On school network

Claims School Mode

School-Mode bypass attempts 0

Device type Device identity

Network identity Provider Registry

Play Integrity verdict Device attestation

Verification signals device & session

Fingerprint verified

On school Wi-Fi

Session continuity

Historical trust 80

Bypass attempts 0

100

/ 100

Verified

Monitored silently

Full access. The device operates normally and is scored in the background.

Live signal breakdown (size of each effect, not the exact weight)

Session Visor: from signal to release

The same score, carried through the whole governance lifecycle.

The score above feeds the S.O.S. Session Visor, the governance orchestrator. Change the relationship, the enforcement path, and the release condition, then watch each step answer honestly. Every step carries a label: LIVE is running code, SIMULATED is a demo stand-in, SUPPORTED / CONFIGURABLE is what the platform can do once wired, PLANNED is designed but not built. Nothing here seizes, virtualizes, or radio-captures a phone. (Stateless: nothing is stored and no adapter is contacted.)

Relationship what S.O.S. knows about this endpoint

Enforcement path the adapter that would receive the request

Mid-session transport change the session must survive this

Release condition what ends school governance

Like what the engine does? See it running on your own students' devices.

📅 Book a demo