Written in a shop, not a boardroom.

The problem we had

A truck comes in. You read it, you fix or tune it, you read it again. The scan tool knows all of it — and then the visit ends and the knowledge ends with it. What the customer gets is a phone call and maybe a screenshot. Six months later nobody can say what the engine looked like the day it left, or who touched the calibration since.

Meanwhile the tool on the laptop has the vendor’s name on it, not yours. The shop does the work; the software takes the credit on every page the customer sees.

What we built instead

Rignos records the session at the truck, keeps every visit on one timeline, and turns it into a document your customer can read — under your shop’s name, on your domain. We stay off the page entirely.

It is deliberately narrow. Rignos does not flash calibrations and does not run bidirectional tests; it reads, records and reports. Your dealer tool keeps doing what it is good at. The full comparison is here.

How we work

• Numbers before adjectives. Every figure on a report is measured by the app and traceable to the session it came from. Where a written summary appears, it is checked against the session’s own numbers before anyone can send it.
• Read-only at the truck. The one write Rignos can do is clearing stored fault codes, and only on a button press.
• Your data stays yours. Customer lists and truck history are scoped to your shop. We do not pool them, sell them, or show them to another shop.
• We answer in person. Support is the people who wrote the code.

Where we are going

Decode coverage is deepest on Cummins today; that is where the shop’s own work is. More makes follow the same path: measured on real trucks first, published second.