Keep the tool you diagnose and flash with. Rignos is the layer above it: the record that survives the visit, the report your customer reads, and the portal with your name on it.
| JPRO / INSITE / DDDL | Rignos | |
|---|---|---|
| Live engine data | ✓Yes, deep per make | ✓50+ parameters over J1939 |
| Active fault codes | ✓Yes, with OEM text | ✓DM1, in plain language |
| Bidirectional tests | ✓Yes | ×Not supported |
| Flashing / calibration writes The one exception is clearing stored codes, on a button press |
✓Yes (INSITE) | ×Read-only by design |
| Works offline in the bay | ✓Yes | ✓Yes — uploads later |
| Dyno-style power & torque sheet | ×Not as a customer document | ✓Built from the session itself |
| Before / after tune comparison | ×Manual, if at all | ✓Two sessions, one delta column |
| Truck history across visits Visits, tunes and faults on the same line |
×Session at a time | ✓One timeline per truck |
| Detects a re-flash by another shop Reads the calibration’s shop mark each visit |
×No | ✓Tune-mark change is dated |
| Report carries your shop’s brand White-label on Pro and up |
×Vendor branding | ✓Your logo, name and domain |
| Portal for the fleet owner | ×No | ✓Each owner sees their trucks only |
| Per-tech accounts & permissions | ×Per laptop licence | ✓Four permission levels |
| Revoke a stolen laptop from the office | ×No | ✓Revoke its machine token |
| Priced by | ✓Seat / subscription | ✓Machine, yearly |
Performance and tune shops that already diagnose well, and want the paperwork, the customer copy and the truck history to look like a product instead of a screenshot in an email.
A shop looking for its first and only diagnostic tool, or one that needs bidirectional tests and flashing. Buy the dealer tool first; Rignos makes sense on top of it, not instead of it.