Oversight of the whole network, from one neutral seat.
Mkondo gives the regulator a cross-tenant, read-only view of every licensee on the rail — with the isolation, auditability, and neutrality guarantees a supervisory role requires. The rail reports to you; it never competes with the operators on it.
One read-only seat over every licensee.
The regulator sees each operator on the rail even-handedly — 48-hour incident filings, quality-of-service, and open queries — in one cross-tenant view it can read but never write to.
Illustrative preview — no operator is in production yet.
Supervision built into the rail, not bolted on.
Every return, one place
Licensee returns arrive through a single published OpenAPI contract with deadlines tracked. No chasing spreadsheets across operators.
Sector-wide visibility
Aggregate quality-of-service, complaints, and defect trends across licensees — read-only, scoped to the oversight roles that may see them.
Trace any pack
Follow a battery's identity, state-of-health, and custody chain across operators — the basis for safety and recall action.
Connections are earned
An operator proves its feed against the canonical standard in a sandbox before it reaches production. Certification is a gate, not a formality — an uncertified connection cannot move the custody chain.
Answer "who, when, what"
Reconstruct any event after the fact. The trail is append-only, so the record can't be quietly revised.
Signatures you can check
Clearing and custody artifacts are Ed25519-signed and the public key is published. Your team can verify a record independently — the platform is not the only witness to its own history.
Why a regulator can trust the switch.
A clearing layer works only if it has no stake in who wins. Mkondo's neutrality is structural, not contractual — it owns no vehicles, stations, or batteries, so there is nothing for it to favour.
We'll walk your team through the oversight console.
A briefing for RURA / RSB on intake, analytics, registry oversight, and the audit trail.