MOMatatuOS
Kenyan matatu corridor and stage activity

Transport operations infrastructure for Kenya

The Operating System for Kenya's Matatu Economy

MatatuOS gives SACCO offices, fleet owners, conductors, dispatch teams, and commuters a shared digital layer for trips, manifests, vehicle records, routes, bookings, payments visibility, and compliance work.

It is not a taxi app. It is operations infrastructure for the transport system Kenya already depends on.

Built for SACCO records
Supports field workflows
Corridor-first rollout

The operating gap

The matatu sector moves millions. But operations are still hard to see.

SACCOs manage vehicles, drivers, conductors, collections, stages, bookings, manifests, and compliance across WhatsApp, paper records, phone calls, Excel sheets, and manual reconciliation. The system works, but it is fragmented. That fragmentation creates blind spots in dispatch, records, revenue visibility, passenger experience, and corridor planning.

Platform layers

One operating platform. Multiple transport layers.

Logistics for Matatus

Vehicle, crew, route, stage, dispatch, manifest, and trip visibility for daily SACCO operations.

Operator Business Layer

Publish routes, manage seat inventory, accept digital payments, and keep operator records in one workspace.

Compliance Workspace

Organize records for NTSA, insurance, permits, audits, crew files, and operating documentation.

Intercity Booking Layer

Help commuters compare operators, book seats, pay, and follow trip details with clear route context.

Spot My Next Ride

Give short-route commuters visibility into nearby vehicles, stages, route options, and likely availability.

Product modules

Built for the whole transport chain.

SACCO Portal

A practical office workspace for vehicles, crews, trips, stages, routes, documents, and reports.

Konda Mode

Fast field tools for manifests, boarding, collections notes, passenger updates, and trip status.

Gari Mode

Vehicle-level trip history, route assignment, maintenance notes, documents, and operating records.

Passenger App

Intercity booking and short-route visibility that respects how commuters already move.

Admin & Compliance Layer

Clean records, exportable manifests, document reminders, user permissions, and audit trails.

Analytics Layer

Route, fleet, demand, collections, and operating patterns made visible for better decisions.

Operating principle

Not built to replace the matatu system. Built to organize it.

Many transport apps fail because they try to force informal transport into a rigid digital model. MatatuOS starts with the existing workflows: cash, M-Pesa, conductors, stages, SACCO offices, dispatchers, WhatsApp coordination, and paper records.

The platform then adds a digital layer for records, manifests, route publishing, bookings, and reports so operators can improve visibility without breaking what already works.

SACCO Operations

Nairobi - Nakuru Corridor

Live pilot view

Vehicles active

42

Trips manifested

118

Records due

7

Dispatch queue
Stage release confirmed
Manifest check in progress
Vehicle document updated
Stage map
Records export ready

SACCO realities

Designed for how transport actually works.

Cash + M-Pesa coexistence
Offline-first field use
Stage-based operations
Multi-SACCO isolation
Gradual adoption
Exportable reports and manifests

For SACCO managers and partners

Credibility starts with the operating details.

SACCO-first permissions

Each SACCO keeps its own users, vehicles, routes, documents, and reports separated from other operators.

Records before automation

The first value is clean operating records: manifests, crew files, vehicle documents, trips, and exports.

Field tools for conductors

Konda workflows are designed for pressure at the stage, not for office-only software demos.

Partner-ready data discipline

Payments, insurance, fleet service, and planning partners need structured records before deeper integrations.

Pilot approach

Starting corridor-first.

The first goal is not to digitize the whole country overnight. MatatuOS is designed to prove value on one structured corridor, work closely with SACCOs and field teams, refine the operating model, and scale from real adoption.

Ideal early pilots involve a clear route or corridor, active SACCO participation, assigned office users, field conductors, and a practical reporting need.

Users and partners

Built for the people who keep Kenya moving.

SACCO Managers
Fleet Owners
Dispatch Teams
Conductors
Drivers
Passengers
Partners

Next step

Bring structure and visibility to your transport operations.

Start with records, manifests, routes, and field workflows. Then build toward deeper commuter access and partner integrations.