I'm Pratyush Shivam, CTO of Konfidio in Berlin. I lead the technology behind TrustedTrucks, a freight platform where every company on a shipment works from one shared record. This week I was back in Ranchi, the city I'm from, speaking at an event at the Software Technology Parks of India. That's the photo above.
When I explain what we build, one bit of arithmetic does more work than any diagram. Here it is.
Five companies, ten links
A single road shipment in Europe usually involves at least five companies: the shipper, the forwarder, the carrier, the consignee, and often an insurer or a customs agent. Each of them runs its own system.
If every pair has to exchange data directly, the number of links is n(n-1)/2. For five companies that's ten integrations. For eight, it's twenty-eight. Every one of those links has to be built, mapped, tested, monitored and kept alive through upgrades on both sides.
In practice nobody builds all of them. They fall back to email, PDFs and phone calls, and every company keeps its own copy of the truth.
One record, five connections
The alternative is a shared record. Each company connects once, to the record, and reads and writes the same shipment: the order, the stops, the proof of delivery, the invoice.
Five companies, five connections. Eight companies, eight. The cost grows in a straight line instead of a curve.
Every integration we avoid is a project our customers never have to fund.
Why the record sits on a permissioned blockchain
A shared record raises an obvious question: who owns it? If one company hosts the database, the others have to trust that company's copy.
So shipment documents are fingerprinted on a permissioned blockchain run between known companies. Any party can check that a document is the version that was approved, when, and by whom, without trusting whoever hosts the screen they're looking at.
It's worth being exact about what that proves. A fingerprint shows a document hasn't changed since it was anchored. It doesn't prove the document was true in the first place. People still approve things; the record makes their approvals checkable.
What users see
None of this should show. A dispatcher should see "approved", never a wallet or a hash. The arithmetic and the fingerprints sit underneath; what people see is one shipment that everyone agrees on.
The takeaway for any multi-party system
This isn't only a freight problem. Any process where several organisations touch the same object has the same curve: claims handling, trade finance, construction, healthcare referrals. Before building the next point-to-point integration, it's worth counting the pairs.
More of my writing, films and projects are at pratyushshivam.com.
Top comments (0)