mkato · mobility data infrastructure · africa

Building the data backbone
for how Africa's cities move.

Development Status: Mkato and Dira are both in active development. The Dar es Salaam pilot is underway. The platform is not yet publicly available. If you are an operator, institution, or developer interested in early access, data partnerships, or pilot participation — register your interest below or reach out directly.

Mkato is a mobility data infrastructure system that captures, structures, and distributes ground-truth transit data across Africa's informal urban networks. Informal transit systems carry the majority of people across African cities — but they operate entirely outside conventional data systems. Mkato is building the underlying layer that makes this network legible, queryable, and operationally useful. Starting in Dar es Salaam. Built for the continent.

80%
Of trips on unmapped informal transit
0
Informal routes digitised on any platform
$5B+
Lost annually to urban congestion across Africa
3h+
Average daily commute in Dar es Salaam

The Problem
01

Informal transit networks carry the majority of urban passengers across Africa's cities. In Dar es Salaam, daladalas account for over 80% of all motorised trips. These systems are dynamic and demand-driven, shaped in real time by road conditions and operator behaviour rather than fixed routes or scheduled timetables. They work — but they are invisible to every digital platform in existence.

While partial maps and isolated datasets exist, the underlying system remains fragmented, inconsistently updated, and largely disconnected from formal planning and digital infrastructure. No operator has route performance data. No city has a live transit network map. No developer has a reliable data layer to build on. The gap is not technological — it is infrastructural.

Conventional mapping systems capture less than 10% of Dar es Salaam's transit reality. The remaining 90%, where most people actually move, remains structurally invisible — not because it cannot be mapped, but because no one has built the infrastructure to capture it.
City planners, logistics operators, and development institutions make billion-dollar decisions without access to basic transit network data. Infrastructure investment, last-mile delivery, and urban policy are all operating on incomplete information.
African cities lose over $5 billion annually to traffic congestion — in wasted fuel, lost productivity, and supply chain delays. The absence of structured mobility data makes every dollar of that loss structurally impossible to address.

The Platform
02

Mkato Technologies is a mobility data infrastructure company building the foundational layer for how Africa's cities move. The system operates across three integrated layers: data capture, intelligence processing, and operations delivery.

Layer 01 · Data
Ground-Truth Data Capture The Mkato navigation app collects verified route, stop, and flow data from daily commuter usage across Dar es Salaam's informal transit network. Offline-first, Swahili-first, passively generating structured mobility signals at street level.
Layer 02 · Intelligence
Dira — Mobility Intelligence Processing Raw mobility signals are processed by Dira, Mkato's internal routing and intelligence layer. Dira structures, validates, and continuously updates the dataset — converting fragmented movement data into machine-readable infrastructure.
Layer 03 · Operations
Structured Data Delivery Processed mobility data is delivered to enterprise clients, city agencies, logistics operators, and development institutions through structured API access — enabling operational decisions grounded in how cities actually function.
The Mkato system is designed to replicate. The methodology that captures and structures Dar es Salaam's transit network applies directly to every subsequent city. Each city entered adds to the dataset. Each dataset strengthens the platform. The compounding data advantage is structural, not incremental.
01 · collect
Route Network Capture
Every daladala route, boarding point, and informal corridor mapped and continuously updated from ground-level usage. Not inferred. Not estimated. Documented from actual movement.
02 · structure
Stop Verification
Real-world boarding and alighting locations captured with GPS coordinates, route associations, connection data, and daily usage averages. Verified against ground conditions.
03 · analyse
Corridor Flow Intelligence
Peak period analysis, passenger density by corridor, and transit frequency data. Updated continuously as live usage flows through the system.
04 · deliver
Structured API Access
GeoJSON, Shapefile, CSV, and GTFS-compatible data delivery for enterprise clients. RESTful API with city-scoped endpoints, geographic filtering, and authentication.

Dira · Mobility Intelligence Layer
03
Internal System · Embedded in Mkato
In Development

Dira is Mkato's internal routing and mobility intelligence layer. It is not a separate product. It is the processing engine that converts raw mobility signals captured by the Mkato App into structured, queryable infrastructure that the rest of the system depends on.

Every route geometry, stop record, flow pattern, and coverage layer that Mkato delivers to enterprise clients passes through Dira. It is the intelligence between data collection and data delivery.

📡
function 01 · ingest
Signal Ingestion and Validation
Dira receives raw mobility signals from the Mkato App — GPS traces, stop confirmations, route reports, and frequency observations. Each signal is validated against existing records and flagged for review where anomalies are detected.
⚙️
function 02 · process
Route and Stop Structuring
Validated signals are processed into standardised data structures — route geometries with GeoJSON coordinates, stop records with relationship maps, and flow pattern time-series. The dataset is continuously refined as new usage data flows in.
🔁
function 03 · update
Continuous Dataset Maintenance
Informal networks shift. Dira maintains a living dataset by detecting route changes, stop relocations, and frequency shifts from ongoing usage patterns. Unlike static maps, the Mkato data layer reflects current network conditions.
🗃️
function 04 · expose
API Endpoint Delivery
Processed data is exposed through versioned, city-scoped API endpoints — routes, stops, flow patterns, coverage layers, and historical datasets — accessible to enterprise clients under authenticated access agreements.
Dira is not marketed separately. It is the intelligence layer inside Mkato. Enterprise clients who access mobility data through Mkato are accessing data that Dira has structured, validated, and maintained. The brand distinction exists for technical clarity, not commercial separation.
Dira handles what no off-the-shelf system can: continuous validation of informal transit data that has no fixed schedule, no standardised reporting, and no existing digital reference. Every record Dira produces is net new to the world's data supply.
The intelligence layer is what separates a navigation app from infrastructure. Mkato is infrastructure. Dira is why.

System Architecture
04

Three wireframe-level diagrams showing how Mkato is structured, where Dira sits inside the system, and how data flows from street-level movement to enterprise intelligence output.

Diagram 01 · Mkato System Architecture
Mkato Technologies
│
Mkato App
Consumer · Data Capture
Dira
Intelligence Layer
API Output
Enterprise Delivery
↓ ↕ ↑
Mobility Dataset · Ground-Truth Layer
Single integrated system. Three functional layers. One unified data backbone.
Diagram 02 · Dira Inside Mkato
Mkato System Boundary
Mkato App · Signal Collection
↓
Dira Intelligence Engine
Validate
Structure
Update
Expose
↓
Enterprise API · Data Delivery
Dira is not a separate product. It is the processing layer inside Mkato.
Diagram 03 · Data Flow · Movement to Intelligence
Urban Movement
Commuters · Operators
→
Mkato App
Signal Capture · Offline
→
Dira Processing
Validate · Structure · Update
→
Mkato Intelligence
Routes · Stops · Flow
→
Operator Action
Planning · Logistics · Policy
Every commuter journey generates data. Dira processes it. Mkato delivers it as infrastructure.

Mkato App · Screens
05

Nine wireframe screens show how the Mkato app captures movement and turns informal transport into clear journeys. The app is in development and these screens are design previews.

9:41▲▲ ▮
HomeWorkSaved
Kariakoo MarketRecent
9 min
Mwenge TerminalRecent
31 min
Home and search
Find any informal route in the city with one search.
9:41▲▲ ▮
Posta → Mwenge
Daladala D-13Direct · every 6 min
42 min
D-22 + Bodaboda1 transfer · Ubungo
38 min
Daladala D-07 + walkCheapest · 350 m walk
51 min
Fares and times from rider reports on this corridor.
Route options
Compare daladala, bodaboda and walking legs side by side.
9:41▲▲ ▮
D-13 · Posta to Mwenge
PostaBoarding
0
KariakooStop 4
9
UbungoTransfer point
22
MwengeTerminal
42
Route detail
Every stop on the line, with the transfer points marked.
9:41▲▲ ▮
Posta Stop120 m
D-13, D-22
Kariakoo Corner260 m
D-07
Samora Stop340 m
D-13
Nearby stops
Verified stops within walking distance, updated by riders.
9:41▲▲ ▮
Fare estimate
TZS 600
Posta to Mwenge · D-13
Base fareDaladala
600
TransferNone
0
Confirmed byRiders this week
214
Save this route
Fare estimate
See the likely fare before boarding, confirmed by riders.
9:41▲▲ ▮
On board · D-13
Next stopUbungo
4 min
ArrivalMwenge
18 min
Live trip
Follow the ride, next stop and arrival time in real time.
9:41▲▲ ▮
Record a trip
Recording · GPS trace
DistanceSo far
6.4 km
Stops taggedTap to add
3
TimeElapsed
00:21
Add a stop
Traces are anonymised and validated before use.
Contribute a route
Riders record trips and stops that build the dataset.
9:41▲▲ ▮
Offline maps
Dar es SalaamRoutes and stops
48 MB
ArushaNot downloaded
Get
MwanzaNot downloaded
Get
Storage used
Offline maps
Download a city once and navigate without data.
9:41▲▲ ▮
Saved and history
Saved
Home to WorkD-13 · 42 min
Go
Work to KariakooD-07 · 19 min
Go
Recent trips
Posta to MwengeYesterday
TZS 600
Ubungo to PostaMon
TZS 700
Saved and history
Return to frequent trips and past journeys quickly.
Solutions
06

Mkato's mobility data infrastructure serves three institutional segments. Each accesses the same ground-truth dataset — structured differently for the decisions each segment needs to make.

Segment 01 · Government
City Agencies and Urban Authorities
Municipal transport departments, planning ministries, and urban development agencies that require accurate, current transit network data to make evidence-based decisions.
Transit route gap analysis and planning
BRT corridor feasibility and design
Equity access and underserved zone mapping
Infrastructure investment evidence base
Development finance project monitoring
Segment 02 · Operators
Transit Operators and Logistics Platforms
Daladala operator cooperatives, last-mile logistics companies, ride-hailing platforms, and supply chain operators requiring network visibility to reduce cost and improve coverage.
Route optimisation and corridor analysis
Demand forecasting by corridor and time period
Depot placement and fleet allocation
Last-mile delivery network design
SaaS dashboard for operator management
Segment 03 · Developers
Platform Developers and Data Partners
Development institutions, research organisations, insurers, and enterprise platforms building mobility-dependent systems that require a structured transit data layer as their foundation.
REST API access — routes, stops, flow data
GeoJSON and GTFS-compatible data exports
Longitudinal datasets for trend analysis
Risk scoring and accessibility modelling
Research and policy dataset licences
All three segments access the same ground-truth dataset. The difference is delivery format, access tier, and agreement structure. Government clients receive procurement-compatible bulk exports. Operators access SaaS dashboards and route performance tools. Developers access versioned REST API endpoints with full technical documentation.

Early Access & Waitlist
07

Mkato and Dira are both in active development. The Dar es Salaam pilot is underway. Register below to join the waitlist — for the navigation app, Dira data access, or a pilot partnership. We will respond to every submission directly.

In Active Development · Registrations Open

Register your interest. We will contact you directly when access opens, or to discuss a pilot or data partnership now.

No spam. No data selling. We will only contact you about Mkato and Dira access and pilot opportunities.

Email
All enquiries · partnerships, press, data access, and government
Partnerships
Institutional partnerships, DFIs, and government agencies
Data Access
Early API access, pilot participation, developer enquiries
Location
Dar es Salaam, Tanzania
Mkato Technologies Limited · BRELA Registered
Phone
Call us directly