← How ProTankr Works

How the self-correcting network works

Every driver is fighting the same invisible enemy: a new shipment or a tank change with a different product weight and/or density reading. Everyone pays for that uncertainty at the scale without any means to communicate the change with each other. As a consequence, many drivers get many overweight tickets before ultimately resolving to load light, all the time, just to cover the worst case.

ProTankr turns that around. The first driver to observe a shift corrects it for every driver who loads there next, across every company, in real time, instead of everyone independently re-discovering the same surprise.

  What actually gets shared
Just the observed API gravity, tied to a specific product at a specific terminal, plus the time it was recorded. Nothing about your route, your company, or your identity travels with it. It's a density reading, not a tracking system.
  How fast it propagates
The moment you enter the actual API from the BOL at the loading rack, the correction is live. The very next driver who plans a load for that same product at that same terminal sees your fresh number, not one from four days ago. There's no batch job or delay, the update happens the instant you submit it.
  Shared industry-wide, not just your fleet
The network isn't scoped to your company. A driver from a completely different fleet, loading the same product at the same terminal, benefits from your observation, and you benefit from theirs. The more drivers loading there, the fresher the reading stays for everyone, regardless of who they drive for.
Runs quietly in the background. There's no alert, no notification, no extra step. You just open the app next time you load at that terminal, and the number waiting for you is already current.
Request Early Access