PSPratyush Shivam

I lead the technology behind TrustedTrucks.

As CTO of Konfidio I am responsible for the whole of it: the product, the blockchain network underneath, the infrastructure it runs on and the team that builds it. It is in production today, on the web and on Android.

Role

Chief Technology Officer

Konfidio, Berlin

Product

TrustedTrucks

One shared record for European freight

In production

Web and Android

The app is live on Google Play

Network

Permissioned blockchain

Ethereum-compatible, between known companies

What I am responsible for

Four things, one system.

  1. 01

    Architecture and product

    How the shipment record is modelled, and every product surface built on it: web platform, Android app and the APIs both share.

  2. 02

    The network and contracts

    The permissioned network, its permissioning and onboarding, the smart contracts for approvals, and the service that signs transactions so applications never hold keys.

  3. 03

    Infrastructure and operations

    Cloud infrastructure, containers, build and release pipelines, monitoring and upgrades. Running it every day, not only deploying it.

  4. 04

    The engineering team

    Technical direction, planning, code review and release discipline, since 2023.

  1. 2021Senior Software EngineerJoined to build the platform that became TrustedTrucks.
  2. 2023Lead Software EngineerTook over the engineering team and the platform architecture.
  3. 2024Chief Technology OfficerResponsible for the whole of the technology: product, network, infrastructure and team.

Case studies

Six parts, told by the problem.

01 / 06

One shared record

A freight platform where shipper, forwarder, carrier and consignee work from the same shipment, from the first quote to payment.

What I built
One platform, end to end. I led the build from architecture to production: quotations and orders, live tracking, document approvals, invoicing, backhaul matching and carbon accounting, on the web and on Android.
Result
TrustedTrucks, in production. The platform runs today as TrustedTrucks. Each company connects once and works with every partner on the network, instead of maintaining an integration per partner.
  • Platform architecture
  • Product engineering
  • Web
Read the case study

02 / 06

Evidence, anchored

Shipment documents are fingerprinted on a permissioned blockchain, so every party can verify them instead of disputing them.

What I built
Approvals as contracts. Smart contracts encode who has to approve what, and in which order, following each company's own signing route. Transaction signing is handled by a dedicated service, so applications never touch keys.
Result
Verified instead of argued. Any party can confirm that a document is the one that was approved, when, and by whom. The question "is this the right version?" has a checkable answer.
  • Permissioned blockchain
  • Smart contracts
  • Document approvals
Read the case study

03 / 06

Proof of delivery to invoice

Accepted delivery evidence becomes the invoice, so carriers are paid on evidence instead of paperwork.

What I built
One flow, each company's rules. Accepted proof of delivery flows straight into the invoice. Approvals follow each company's own signing route, so the process fits how finance teams already work.
Result
Paid on evidence. The invoice arrives already backed by the delivery it refers to. There is nothing to reconcile, because both came from the same record.
  • Workflow design
  • Multi-party approvals
  • Invoicing
Read the case study

04 / 06

Carbon from the trip

Shipment emissions measured from the journey that actually happened, on a GLEC Framework and ISO 14083 basis.

What I built
From estimate to actuals. Emissions are estimated at order time and then replaced with actuals from the delivered trip, aligned with the GLEC Framework and ISO 14083.
Result
Measured, not modelled after the fact. Each shipment carries its own emissions figure with the journey behind it, available to the parties on that shipment.
  • Carbon accounting
  • GLEC Framework
  • ISO 14083
Read the case study

05 / 06

A permissioned network, in production

An Ethereum-compatible network between known companies, run with the same discipline as any other production system.

What I built
Operated, not just deployed. I designed and run the network layer: onboarding participants, permissioning, monitoring and upgrades, alongside containerised services with automated build, test and release pipelines.
Result
Invisible to the people using it. A dispatcher sees "approved". A carrier sees "paid". Nobody on the platform needs a wallet or has to think about a chain.
  • GoQuorum
  • Kubernetes
  • AWS
  • Operations
Read the case study

06 / 06

The network in a pocket

The TrustedTrucks Android app on Google Play: post loads, send quotes, approve proof of delivery and confirm invoices.

What I built
One record, two surfaces. Built with React Native on the same APIs as the web platform, so an approval made on a phone is the same approval everywhere else, immediately.
Result
Live on Google Play. Forwarders and carriers can post loads, send quotes, approve proof of delivery and confirm invoices from the app.
  • React Native
  • Android
  • Product design
Read the case study

The product, end to end

From the first quote to the final payment.

What a forwarder or a carrier can do on TrustedTrucks today. Most of it has a short film.