Skip to content

FreightProof

Every handover. On the record.

Cargo goes missing between systems: at the gate, the loading bay and the receiving dock. FreightProof records every handover of a road-freight trip on a tamper-evident public ledger, so when a load is hijacked or a delivery is disputed, you have the evidence.

A white articulated truck on an open highway at golden hour

Origin depot

One truck. Seven handovers. Every one on the record.

Scroll to drive a sample trip from the origin depot to the receiver. Each checkpoint seals as the truck passes, in the same order FreightProof records a real trip.

Fingerprints shown here are illustrative.

Trip FP-0418

Cape Town → Johannesburg

Anchored
Driver
Verified · company device
Vehicle
Horse + 2 trailers
Consignments
3 clients · 412 units
Precincts
Origin, 1 hub, destination

Journey lock · SHA-256

9f2c 41ab 77e0 c8d2 … 51e9 3d1a

Anchored to Hedera Consensus Service at 06:12 SAST

Sample record. Values are illustrative.
  1. The trip is locked before the truck moves

    The dispatcher commits the driver, horse, trailers, consignments, route and precincts. FreightProof fingerprints that commitment, so any later change has to be recorded as an exception.

    Recorded and anchored: Journey lock.

  2. The right driver, at the right gate

    The driver signs in on a company device at the origin precinct. Their phone position is checked against the precinct boundary, and a mismatch is recorded, not waved through.

    Recorded and anchored: Driver and location.

  3. Counted, signed and sealed

    The driver confirms the unit count from the linehaul document without ever seeing what’s inside. The seal number and the signed waybill are recorded alongside it.

    Recorded and anchored: Pickup receipt.

  4. Out of the gate with an intact seal

    Departure fixes the combination of driver, vehicle, cargo and seal. From here, anything that doesn’t match is an exception on the record.

    Recorded and anchored: Departure.

  5. The long road, still on the record

    Deviations and incidents on the road are logged against the trip with their time and position, exactly where they happened.

    Recorded and anchored: Transit log.

  6. Arrival is the proof

    At the destination, the seal is checked against the one recorded at pickup and the counts are reconciled. A broken or swapped seal is the strongest signal there is.

    Recorded and anchored: Delivery receipt.

  7. The receiver closes the chain

    The receiver confirms delivery with a one-time PIN. No app and no account are needed. The trip’s evidence chain is complete.

    Recorded and anchored: Chain closed.

Delivered, and provable.

Seven records form one unbroken chain. If anyone edits a record afterwards, its fingerprint no longer matches the one on the public ledger, and that’s visible to anyone who checks.

Every leg is tracked. The handover isn’t.

GPS knows where the truck is. The manifest knows what’s on it. The gate knows who drove in. None of them share what they know at the moment cargo changes hands. That gap is where organised theft works, and where a disputed delivery becomes one company’s word against another’s.

1,976 truck hijackings recorded by SAPS in 2023/24. That’s more than five every day, and up more than 50% in a decade.
ISS Today, Dec 2024

420 trucks hijacked in the second quarter of 2025 alone.

SAPS crime statistics, via Aon, Feb 2026

R577m in reported losses across 2,670 cargo-theft incidents in 18 months, and that counts only the incidents that were reported.

TAPA EMEA, to June 2022, via Aon

When a load is disputed, you open the record.

  • Every handover, in order

    Who did it, where, when, and against which plan. The trip’s position is worked out from what actually happened, never typed in.

  • Independent sources, side by side

    The driver’s phone and the vehicle’s tracker report separately. When they disagree, the disagreement itself is on the record.

  • A receipt anyone can check

    Each record’s fingerprint sits on a public ledger, so you can show a claims handler that nothing was edited after the fact.

Trip FP-0391

Johannesburg → Durban

  1. 05:48Trip lockedDriver, vehicle and 412 units committed
  2. 07:31Loaded and sealedSeal 0048213 · signed waybill recorded
  3. 08:02Departed originSeal intact at the gate
  4. 16:40Arrived at receiverSeal 0048213 matches pickup
  5. 17:05Count reconciled412 sent, 409 received

The seal matched at both ends, so the shortfall happened at the receiver’s dock and not on the road. That’s a different claim, with different evidence behind it.

Sample trip. Values are illustrative.

Built for how freight actually moves.

Evidence, not operations.
FreightProof doesn’t reroute trucks or replace your tracking, manifest or gate-security systems. It records the moments between them.
Your people’s data stays in South Africa.
Identities, locations and photos are stored in Cape Town (AWS af-south-1). Only a SHA-256 fingerprint goes to the public ledger, and it reveals nothing about anyone. POPIA by design.
No new logins at the gate.
Guards and warehouse staff don’t need accounts. The driver is the only hands-on user, and the receiver confirms with a one-time PIN.

Built in Cape Town, for South African roads.

FreightProof started in 2026 as an Honours project at the University of Cape Town. It was shaped by a site visit to a working distribution hub and by people who move freight on South African corridors every day.

We kept hearing the same thing: when a load disappears, everyone has a log and nobody has proof. So we built the record that sits between the systems, so that the truth about a handover doesn’t depend on who tells the story.

  • Ciaran FormbyCo-founder
  • Tim GultigCo-founder
  • Chiko KasongoCo-founder
  • Tom DavisCo-founder

Put your next trip on the record.

We set up accounts for each operator. Tell us about your fleet and we’ll be in touch to talk about your routes.

Prefer to write to us?
freightproof@gmail.com

Routes, current systems, a recent incident. Up to 600 characters.

This opens your mail app with the request filled in. We use it only to reply. See the Privacy Notice.