Handbook

Appearance

What Is Korido ​

What this chapter covers ​

Korido is a multi-tenant fleet-tracking platform built for long-haul trucking on the Douala–N'Djamena corridor between Cameroon and Chad. This chapter explains the problem Korido exists to solve, who its users are, the surfaces they work in, and the one principle that anchors everything the platform believes about a truck's location.

The picture ​

The problem Korido solves ​

The Douala–N'Djamena corridor is roughly two thousand kilometres of road that a truck crosses over several days. Along the way it climbs out of the port at Douala, threads through Cameroonian towns, waits at weighbridges and toll gates, queues at the border, clears customs, and finally reaches N'Djamena in Chad. A single mission can span two countries, multiple stops, and long stretches of thin cellular coverage.

That length is exactly what makes the work hard to see. On a corridor this long, the things a fleet owner most needs to know are the things that happen far from the depot:

  • Breakdowns. A truck that stops moving in the middle of nowhere costs money every hour, and the owner often learns about it late, by phone, after the driver has already lost time.
  • Border waits and formalities. Time spent at the frontier, at customs, or at a weighbridge is real cost, but without measurement it blends into "the trip took a while."
  • Fuel loss and tracker interference. A sudden fuel drop, a tracker cut from power, or a truck parked somewhere it should not be is invisible unless something is watching continuously.
  • Opaque trips. When did the truck actually leave? Where did it stop, and for how long? Was it on the agreed route the whole way? Without a system, the honest answer is usually a guess reconstructed after the fact.

Korido turns that opacity into a continuous, measurable record. A tracker on every truck streams position and telemetry; the platform reconstructs the journey into trips, stops, gaps, and border crossings; it watches the truck against its agreed route; and it raises alerts the moment something worth knowing happens — a fuel drop, a route departure, a truck gone dark. What was a phone call after the fact becomes a live picture and a searchable history.

Tenants and fleets ​

Korido is a SaaS platform, so it hosts many trucking businesses at once. Each business is a tenant — its own fleet, its own drivers, its own clients, its own missions. A tenant's data is theirs alone: every truck, trip, alert, and report belongs to exactly one tenant and is never visible to another. Isolation is enforced on every read, so a tenant only ever sees its own corridor.

Within a tenant, the working unit is the fleet: the vehicles the business operates, the trailers they pull, the drivers who staff them, and the clients whose cargo they carry. The platform is designed to serve a real operator's fleet — on the order of fifty to a hundred trucks — not a demo.

The four roles ​

Korido recognises four roles. Two are the working roles inside a tenant, one belongs to the platform itself, and one is held in reserve.

  • Owner — the fleet operator. Owners run the business inside Korido: they see the live map and dashboard, create and assign missions, read the diary and reports, manage vehicles, trailers, drivers, and clients, and receive the alerts that matter. The owner is the primary paying user.
  • Driver — the person behind the wheel. Drivers use the driver app to receive mission assignments, confirm loading and progress, and stay in sync with the office, including where coverage is thin.
  • Admin — Korido platform staff. Admins operate across every tenant from the Admin Portal, handling tenant support, fleet health, the shared road network, and coverage. This role belongs to the Korido platform itself.
  • Viewer — a reserved, read-only role for future use, for people who should see a fleet without changing anything.

The two roles that live inside a tenant are owner and driver. Admin is a platform-wide role, and viewer is held in reserve.

The surfaces at a glance ​

Each audience meets Korido through a surface built for how they work.

SurfaceWho it servesWhat it is for
Fleet appOwners and their office staffThe main workspace: live map, dashboard, missions, vehicle diary, fuel, clients, trailers, tracking links
Admin portalKorido platform staffCross-tenant operations: tenant support, fleet health, the shared road network and corridors, coverage
Driver appDriversA mobile app for mission assignments, loading and progress confirmation, and offline-tolerant sync
Owner appOwners on the moveA native mobile app centred on the live map and vehicle status
Customer tracking portalThe fleet's own customersA shareable link that lets a shipper follow their cargo without a login, gated by phone verification
WhatsAppOwners, drivers, and customersAlerts, one-time codes, and a bot for quick questions, in the channel people already use

The fleet app and the owner app serve the same person in different postures — one at a desk, one in a pocket. The customer tracking portal is the only surface built for people outside the fleet, and it shows a deliberately narrow, privacy-safe view.

The GPS source-of-truth principle ​

Everything Korido claims about where a truck is rests on one rule: the truck's location comes from the hardware tracker fitted to the vehicle — a VL863-class device — and reaches Korido through Flespi, the telemetry gateway that speaks to the tracker fleet. The hardware tracker is the single source of truth for position and vehicle telemetry.

The driver's phone is not. The driver app may show the driver their own location on a map for their convenience, but that phone GPS is display-only: it is never sent to the backend, never stored, and never used to decide where a truck is, whether it has deviated, or whether it has arrived. A driver could leave their phone at home and Korido would still track the truck perfectly, because the truck — not the phone — carries the tracker.

This separation is deliberate and load-bearing. It means a truck's record cannot be spoofed or accidentally distorted by a phone in the wrong pocket, that tracking survives a dead or forgotten phone, and that every downstream judgement — trips, Route Guard, fuel, arrivals — is built on one trustworthy positional signal rather than two competing ones.

How it connects ​