The shared record
that keeps freight
moving.
Pamoja OS is the operating system for African freight corridors — live across six Botswana border posts handling 1,700 trucks a day. One timestamped record shared across operators, brokers, terminals, and border agencies. Dira, Pamoja's AI layer, runs 68 agents across every active shipment: catching border holds, dispatching WhatsApp alerts in under 2 seconds, and resolving 80% of exceptions before your team opens the dashboard.
Dira resolves exceptions
before your team opens
the dashboard.
Dira is Pamoja OS's autonomous operations layer — 68 agents running continuously across every active shipment. It catches exceptions before they become delays, routes escalations to the right person, dispatches WhatsApp alerts in under 2 seconds, and writes an immutable audit entry for every action taken. Your team supervises. Dira handles the volume.
80% of exceptions resolved without a human decision — and you set the trust level. Dira can suggest, alert, seek approval, or act independently, based on the authority you define per exception type.
One WhatsApp number. Drivers, traders, operators, border officers, fleet owners, revenue authorities — everyone in the freight chain, in their own language. Every message logged, every handoff tracked, every dispute resolvable.
Freight has no
shared record.
Every border crossing generates a dispute. Every delay generates a conversation. Nothing is timestamped. Nothing is attributed. Nothing is irrevocable.
Delays without proof.
A shipment sits at a border post for 48 hours. No one knows why. The operator calls the driver. The driver calls the agent. The agent says it was customs. Customs says it was the broker. No record. No timestamp. No accountability.
Disputes without evidence.
A client disputes a delay charge. The operator has a WhatsApp message and a scanned paper manifest. The client has a different story. There is no shared record both parties can point to. Legal costs more than the charge.
Billing without a clean event chain.
Invoice construction takes 3–5 days per corridor cycle. Someone must manually reconcile the manifest, the border log, the fuel receipt, and the customs clearance. One mismatch delays payment for weeks.
Your operators are
already on WhatsApp.
So is Dira.
The problem was never WhatsApp — it was that WhatsApp messages disappeared. Pamoja turns every message into a timestamped, immutable corridor record. Drivers reply to acknowledge holds. Agents upload compliance certificates directly from the chat. Dira verifies, links the attachment to the shipment, and releases the hold — no app install, no training, no dashboard required.
Every reply is auditable evidence. Every upload is part of the chain. Your field team works in the tool they already use — in their language — and every exchange lands in the permanent record automatically.
Built for the continent,
not imported into it.
Pamoja exists because freight across African corridors still runs on fragmented records. Status lives in calls, paper, spreadsheets, WhatsApp threads, and disconnected finance workflows. When cargo changes hands, crosses a border, or reaches invoicing and settlement, the truth gets lost.
We built Pamoja to fix that. One operating record. One event chain. One system for road, rail, port, terminal, border, and finance workflows. The result is faster movement, cleaner compliance, stronger auditability, cleaner billing support, and less time spent rebuilding what happened.
Designed for real adoption, Pamoja starts with CSV and WhatsApp, works across institutions, and creates a defensible record from intake to settlement.
Pamoja's real competitor is not another software company. It is phone calls, WhatsApp messages, spreadsheets, and tolerated delay. We are not asking operators to replace working systems — we are building the shared record that sits above them.
What Pamoja delivers.
Not dashboards. Not alerts. Structured outputs that resolve disputes, support invoices, and give every party a clean record they can act on.
Evidence Packs
A complete timestamped dossier for every shipment — border log, documents, custody chain, and exceptions in one exportable record.
Weekly Corridor Reports
Per-corridor performance summaries: average clearance time, exception rates, delay trends, and top hold reasons.
Shipment Dossiers
Full lifecycle view of any shipment from origin dispatch to final delivery — every event, every document, every actor.
Auto-Generated Invoicing
Invoice generated automatically from the shipment event chain — no manual entry, no missing line items, no reconstruction from calls. Every line item is traceable back to a timestamped corridor event.
Exception Timelines
Every exception with its full context: when it was detected, what caused it, how Dira resolved it, and what it cost.
Performance Analytics
Aggregated views across corridors, operators, and border posts — built from the same event record your team already creates.
How the record
is built.
Every event, every document, every exception — captured as it happens. No retrospective data entry. No reconciliation at month end.
Shipment created
Operator creates a shipment record. Route, cargo, parties, and expected timeline are attached.
Events posted
Each handoff generates a timestamped event — dispatch, border arrival, inspection, clearance.
Documents attached
Manifests, permits, HS codes, and customs forms are linked to the record as they're issued.
Exceptions detected
Dira AI monitors the event stream and flags missing documents, SLA breaches, and holds in real time.
Holds resolved
Dira reaches out over WhatsApp, routes exceptions to the right person, and logs the resolution.
Billing and reporting
Once delivered, Pamoja auto-generates billing summaries, evidence packs, and corridor performance data.
Built for every party
in the corridor.
Every role touches the same shipment. Each one needs a different record, a different workflow, and a different reason to trust the system.
You are expected to answer for delays, missing documents, border holds, and delivery timing, but the record is scattered across calls, emails, paper, and WhatsApp.
Pamoja gives you one shipment record from dispatch to delivery, with every document, custody event, border update, and exception tied to the same timeline.
Request an evaluation as a shipperWhen a client, insurer, or customs officer asks what happened, you answer with proof, not reconstruction.
One record.
The full journey.
From origin dispatch to billing closeout — every stage is captured, timestamped, and attributed to the actor who logged it.
Built for
government buyers.
Auditable by design.
Pamoja OS doesn't just report what happened — it proves it. Every event is attributable, irrevocable, and independently verifiable.
WCO-aligned structure
Every document type, HS code, and event classification follows World Customs Organization data standards — compatible with any SADC border system.
Immutable event log
Every action is timestamped, attributed, and permanent. No deletion. No amendment. No one can rewrite history after a dispute begins.
Role-based permissions
245+ granular permissions. Regulators see what regulators need. Operators see what operators need. No cross-party data leakage.
Reason-coded overrides
Every manual override requires a reason code and creates a permanent audit record. Queue transparency eliminates the informal economy of border administration.
Multi-party auditability
Any party with a legitimate role in a shipment can access the relevant record slice. Independent verification without system access negotiation.
Data sovereignty
Deployable on-country. Corridor data stays within your jurisdiction. No cross-border data transfer without explicit policy agreement.
ASYCUDA-aligned data structure
Designed for direct integration with ASYCUDA — the customs management system used across 30+ African countries. No translation layer. Every declaration in Pamoja maps to the same data structure ASYCUDA expects.
Corridor reliability index
Every party in the corridor earns a verified reliability score built from actual event history — not self-reported. Operators, brokers, carriers, and agencies build reputations based on real performance, not references.
Not a black box. Every decision traceable. Every override permanent.
Request a compliance briefing →Illustrative returns.
Adjust the inputs to see a rough estimate based on typical corridor operator data. Figures are illustrative — not a guarantee.
ILLUSTRATIVE ONLY · BASED ON TYPICAL CORRIDOR DATA · NOT A GUARANTEE
Start small.
Prove value fast.
No integration project. No procurement committee. You can have your first corridor record live within 14 days using a spreadsheet and WhatsApp.
Request a 14-day evaluationFrom evaluation
to rollout.
The first engagement is designed to show how Pamoja would work in your environment using your workflows, records, and operational realities. From there, rollout is scoped based on the corridors, teams, and event types that matter most.
Designed to land at the border,
expand across the corridor.
Free to start. Paid at scale.
Border agencies receive free access to Pamoja OS during the land-and-expand phase. Prove value first. Commercial terms activate when you expand to additional crossings.
Corridor bundle. Proven in 14 days.
One monthly fee per active corridor. Covers your operators, your documents, your Dira AI tier, and your evidence pack generation — no per-seat pricing.
Corridor data. For governments and DFIs.
Development finance institutions, trade bodies, and governments access the Corridor Intelligence API — live movement data, emissions records, and performance analytics across active corridors.
Questions.
Ready to run your
first corridor
on real data?
Tell us which corridor and role you're in. We'll run a live demo on your data within 48 hours.
Start with a CSV upload or manual entry. No IT involvement required to begin your evaluation.
You will have a working shipment record and your first exception flagged within two weeks of setup.
The first 90 days carry no contract obligation. You pay only after the evaluation proves value.