About Mkondo

We are the current the whole sector rides.

Mkondo is Swahili for current — the moving water that carries whatever travels in it. A current belongs to no one, and everything in the water rides it. That is exactly the role we set out to play.

Rwanda's electric-motorcycle sector runs on battery swap, and the mandate asks operators to share a network under one standard. But interoperability can't be owned by one of the racers. The operator that holds the switch — the layer that identifies every pack and clears every rider between competitors — has the wrong incentives, and the regulator can't trust it.

Mkondo is that layer, built to be structurally neutral. We own no vehicles, no stations, and no batteries. We reduce friction for the whole ecosystem, and value accrues to the rail rather than to any competitor inside it. That is the thesis, and the architecture is built to keep us honest to it — neutrality that depends on our good intentions isn't neutrality, it's a promise.

We built in regulatory order — compliance reporting first, then the battery registry, then rider-transition clearing — so every layer earned trust before the next one stood on it. All three are now in the console. The sequencing wasn't a roadmap for its own sake: clearing settles against the registry's custody chain, and the registry inherits reporting's audit trail and isolation. Built in the other order, each layer would have had to invent what the one below it already guarantees.

Positioning

“The neutral interoperability and clearing layer for electric two-wheeler battery swap — the current that carries the whole sector forward, without competing with the players inside it.”


Under RURA Regulations N° 011/ENERGY/RURA/2026 · Kigali, Rwanda
What we hold to

Three commitments the architecture enforces.

01

Neutral by construction

We own nothing on the network. Neutrality isn't a promise in our terms of service — it's the reason we can hold the switch at all.

02

Auditable by default

Every action is append-only with actor and timestamp; clearing and custody are cryptographically signed with a published key. If it happened on the rail, anyone entitled to check can prove it — without asking us.

03

Sovereign and portable

Self-hosted identity, contract-first APIs, container + Terraform deployment. The regulated core isn't hostage to any single vendor or cloud.

Who we are

The team behind Mkondo.

A small team building Rwanda's neutral battery-swap rail — engineering, regulatory, and product working to one standard. Profiles below are placeholders; real names, bios and photos follow.

Founder & CEO
Name to be confirmed

One-line bio — background and what they lead at Mkondo.

CTO · Engineering
Name to be confirmed

One-line bio — the platform, architecture, and the regulated core.

Regulatory & Partnerships
Name to be confirmed

One-line bio — RURA, RSB, and operator onboarding.

Product & Design
Name to be confirmed

One-line bio — the console, the API contract, and the developer experience.

Placeholder profiles — final team details are being prepared (NIP-PLT-UXS-003).

Where we are

Built in the order the mandate is enforced.

Built
Platform Foundation & Mkondo Report
Tenant onboarding, 8-role RBAC, immutable audit, RLS isolation — and licensee compliance reporting to RURA with maker-checker submission.
Built
Mkondo Registry
Battery identity, state-of-health, and a gapless custody chain — re-keyable to the final RSB standard.
Built
Mkondo Clearing
Append-only rider- and battery-transition clearing with Ed25519-signed custody artifacts and settlement.
Open now
Sandbox connectivity & conformance
An operator can connect against the published contract, push canonical swap records, and earn a conformance certificate — before any production data moves.
Next
The first production pilot
Gated on the per-operator field mapping and data-sharing agreements, not on the software. No operator is in production yet.
Note — Mkondo is pre-trademark-clearance. The name, wordmark, and any figures shown across this site are working material and not final brand or commercial commitments.

Building on the same rail?

Operators, OEMs, and RURA teams — we'd like to hear how you work today.