Evidence Core
Standard codes, readiness, freeze frames, supported live readings, responder identity, immutable scan history, and device-signed ProofScan records.
View plansScanWrench connects vehicle evidence, diagnostic reasoning, exact-part research, compatibility truth, fleet custody, and professional handoff into one repeatable workflow. The software shows what it observed, how it ranked the next test, and where the evidence stops.
Each layer adds context without turning incomplete data into a promise. Everyday vehicles, hybrids, EVs, premium cars, exotics, fleets, and professional hardware all use the same evidence contract.
Standard codes, readiness, freeze frames, supported live readings, responder identity, immutable scan history, and device-signed ProofScan records.
Ranks test paths from captured signals, cross-signal correlations, repeat scans, exact licensed definitions, and documented external measurements—never from a generic code alone.
Starts with the user-confirmed RockAuto brand and manufacturer part number, then compares exact-MPN offers, delivered cost, seller quality, returns, and written dealer quotes.
Pins every result to exact hardware, firmware, driver, platform, vehicle, module, read function, and profile. Signed success and failure evidence keeps support current.
Combines consented custody windows, signed checkout/return scans, before-and-after differences, bounded telemetry summaries, retention, and accountable fleet handoff.
Packages privacy-reduced evidence for shops, fleets, reviewers, and authorized specialists through private workspaces, durable status history, and revocable provider authority.
A signed, versioned runtime policy lets ScanWrench release or stop bounded cloud workflows without shipping unsafe authority. Every operator change requires strong authentication, a named role, a reason, and an audit event.
Remote control can disable, observe, or release a bounded feature already present in the app.
Vehicle commands, security functions, licensed definitions, billing entitlements, and unsupported hardware capabilities.
Optional reliability counters with explicit consent—no account, stable device ID, VIN, vehicle identity, DTC, reading, location, route, or free text.
Failures, unavailable channels, provenance, application scope, timestamps, and signed proof references.
Standard OBD-II works through supported consumer adapters. Deeper read-only diagnostics use approved professional VCI families, pinned drivers, exact vehicle profiles, licensed semantics, and current signed support grants. No proprietary ScanWrench box is required.
Explore exact compatibility ↗Drivers get clearer decisions. Shops get cleaner preflight. Fleets get evidence over time. Hardware and profile creators get an independent path to exact support.
Compare access ↗