Live — Running in Production

Prove every
handoff.

Proof-of-handover infrastructure for logistics operators. Every custody transfer — recorded, verified, and auditable across company lines.

WB-20260601-5WBC11 · GIG Logistics → Fastline Hub01 Jun · 14:33
23c5ec789f8ac45f2a91b3d7e6f01c4a88d2e7b3...
WB-20260601-5WBC11 · Fastline Hub → Courier01 Jun · 14:35
fcf2747c46eed873a12f09c4b81e3d5a70928f6c...
WB-20260601-5WBC11 · Courier → Receiver (OTP confirmed)01 Jun · 14:40
139947c271ac3f1cb04d8e2a5f6b9c01d743e82a...

166+

Commits

MIT

Open Source License

Self-hosted

You own your data

OLI Network

Cross-operator protocol

The Problem

The most expensive moment in logistics is the one nobody records.

A package from Lagos to Abuja changes hands five or six times before it reaches the customer. Each transfer is a handover — and in most African logistics operations today, none of them produce a receipt that would survive a dispute.

Not because operators are careless. Because the infrastructure for shared custody records between independent companies has never been built. Every logistics platform is designed to solve one company's problem. None of them cover the gap between companies — and that gap is precisely where packages disappear.

The result: disputes that take days to reconstruct from WhatsApp threads, riders who carry blame for things that happened after they left, and cross-operator partnerships that quietly erode because nobody can trust a shared record that doesn't exist.

Between companies

Your system stops having visibility the moment custody crosses to a partner operator.

At scale

Informal processes — WhatsApp, counter signatures — collapse under volume.

At the last mile

"Delivered" is an assertion from the person whose job depends on it, with no independent verification.

How It Works

Three steps. One immutable record. Zero dispute.

01

Dispatcher generates the handover

The dispatcher taps hand over in their dashboard. A QR code appears — a one-time token tied to the specific waybills in the run, expiring in 15 minutes.

02

Rider authenticates and scans

The rider opens Trackam, verifies with their phone number, and scans the QR. Their identity — verified once at onboarding against a government ID — flows automatically from their session. No form. No typed name.

03

Proof hash is recorded

A SHA-256 hash of the waybill ID, both actors, GPS coordinates, and timestamp is written to the shipment's custody chain. Both dashboards update in real time. The record belongs to neither party. It belongs to the shipment.

Features

Every detail built for how logistics actually works.

Cryptographic proof

Every handover produces a SHA-256 hash of the waybill ID, both actors, GPS coordinates, and timestamp. Immutable. Auditable. Belongs to the shipment.

Verified identity

Riders verify their government ID once at onboarding. From that point identity flows automatically from their authenticated session — never collected at handover.

Cross-operator chain

When custody crosses company lines, both operators record the same event through OLI Switch. The chain follows the package, not the platform.

GPS-stamped events

Location is captured silently at the moment of transfer. Every proof hash carries coordinates — no button tap required from the rider.

Public tracking, private PII

The custody chain is public. Sender and receiver details are revealed only after OTP verification — protecting privacy without hiding accountability.

Batch handovers

Dispatch runs hand off multiple shipments in one event. Every waybill in the batch gets its own proof hash, simultaneously, in a single scan.

Who It's For

Every actor in the chain feels the handover problem differently.

Dispatcher

Before

You send 20 runs. You have no confirmation any of them actually transferred.

With Trackam

Know the moment a rider accepts custody. Open any dispute in seconds with a timestamped, GPS-stamped proof chain.

Hub Operator

Before

Packages arrive from partners whose systems don't speak to yours. Accountability stops at your door.

With Trackam

Every incoming transfer from any operator on the OLI network records against your instance. The chain doesn't break at company boundaries.

Logistics CEO

Before

A customer calls at 6pm. A package is missing. Nobody can agree on who had it last.

With Trackam

Open the waybill. See every hand it passed through — names, timestamps, locations. Disputes resolve in 30 seconds instead of 3 days.

The Network

The chain follows the package — not the platform.

Each operator runs their own private Trackam instance. Their data stays on their server. Nobody else sees their business.

But when custody crosses from one operator to another, both instances connect through the Open Logistics Interconnect — OLI Switch. Both record the same handover event simultaneously. The proof hash is identical on both sides.

A package moving through four companies has one auditable custody chain that no single company controls and no single company can edit.

OLI Switch
GIG Logistics
connected
Fastline Hub (Onitsha)
connected
Your Company
connected
New Operator...
join the network
Each operator owns their data.
The chain is shared. Nobody controls it.

The Technology

Open source. Self-hosted. Nothing hidden.

Trackam is MIT-licensed and fully open source. You can read the handover logic, the hash generation, the OTP flow, the custody chain. Every line.

Operators own their infrastructure. Your riders, your waybills, your database — on your server. One-command Railway deployment for managed hosting, or a full self-hosted path for complete control.

Stack

Node.js · React · PostgreSQL

License

MIT — fork and deploy freely

Deployment

Railway one-click or self-hosted

Protocol

OLI Switch — open spec

Built by Backyard Studios

Deploy Trackam for your operation.

If you run a logistics business and want to explore deploying Trackam, or want to discuss a commercial conversation, reach out directly.