One standard for every swap — owned by no operator.
Mkondo is the interoperability and clearing rail for Rwanda's electric-motorcycle battery swap. Reporting, battery registry, and rider-transition clearing are built and running in one console — under RURA Regulations N° 011/ENERGY/RURA/2026.
Interoperability can't be owned by a competitor in the race.
The mandate asks operators to share a swap network under one standard. The question is who holds the switch that clears everyone's riders and batteries between operators — and that layer only works if it has no stake in who wins.
Interoperability held by one of the racers
When a swap operator opens its own network, rivals must route their custody data and rider transitions through a direct competitor, priced by that competitor. It can aggregate vehicle-makers — but competing operators won't clear through it, and a regulator can't lean on it as neutral shared infrastructure.
Owned by no operator, trusted by all
Mkondo owns no vehicles, no stations, and no batteries, so it can clear every operator's riders and batteries without competing inside the network. Neutrality here isn't a promise in the terms of service — it's the architecture.
Each product is the rail for the next.
We built in the order the regulation is enforced — compliance first, then the registry that identifies every pack, then the clearing that settles riders and batteries moving between operators. All three are now in the console, and each still stands on the one below it.
Mkondo Report
The regulated intake for licensee returns to RURA — maker-checker submission, immutable audit, and deadline tracking. The foundation the rest of the rail stands on.
Explore Report →Mkondo Registry
A neutral registry of battery identity, state-of-health and custody chain — re-keyable to the final RSB standard, so adopting the national identifiers is a migration, not a rewrite.
Explore Registry →Mkondo Clearing
Append-only clearing for riders and batteries moving between operators — Ed25519-signed custody artifacts and settlement, closer to a national payments switch than a CRUD app.
Explore Clearing →Contract-first, auditable, and portable by design.
Operators connect once, under one contract
Every licensee files returns and pushes swap records through the same published OpenAPI contract. Maker-checker means a preparer files and an approver releases — no single hand touches the regulator's copy.
A swap becomes a record, not a spreadsheet
One canonical swap record carries a pack's custody, a station's uptime, and a rider's transition. Capture it once and the registry, quality-of-service, and clearing all read the same object — nobody re-keys it.
The regulator reads across the rail
RURA sees every licensee even-handedly, read-only, isolated by row-level security. The regulator reads cross-tenant but never writes.
Every action is provable later
Submissions, releases, and handovers are written append-only with actor and timestamp. Clearing and custody artifacts are Ed25519-signed, so the record holds up under audit.
The infrastructure choices are the product.
Mkondo is engineered like a payments switch, not a SaaS demo. The neutrality is structural, and so is the security posture — both are commitments you can inspect rather than take on trust.
See the rail your operators will actually file on.
A 30-minute walkthrough of the console — reporting, registry, and clearing — mapped to your licence class and reporting deadlines.