Frutos Kamanzi
New 5G Hands-on Weekend · 7 + 14 Nov Book a seat

Independent engineer · Kigali, Rwanda · since 2007

From your own export to the root cause, with the evidence attached.

Eighteen years inside Rwanda's mobile cores: MTN, Tigo, Airtel and Ericsson Managed Services, with platform depth in Ericsson and ZTE. Since March 2026 I build what I always needed on shift: Isaano, an evidence-locked root-cause engine, and 28 self-serve diagnostic tools for operators, banks, insurers, utilities, transport and government.

Full version of every tool: RWF 300,000 a month per organisation, USD 200 outside Rwanda, cancel any month.

  • 99.95% CS core availability, sustained
  • 4 h → 15 min diagnosis and RCA
  • 72,430 verified counters
  • EN · FR · SW · RW
  • 30 tools live
  • Isaano in daily use
  • 5G SA lab running

Building now

What I am building, and what it already proves

Every piece below started as a problem I met in production. Each one ends with something you can check: a number, a test count or a public thread.

In daily use

Isaano · root-cause engine

Named after the Kinyarwanda isano, the link. It reads alarms, counters, traces and the vendor manual for the exact release, then writes the root-cause report, the evidence pack and the change procedure with rollback. When evidence is missing it asks for exactly what is needed instead of guessing.

4 h → 15 min diagnosis and RCA time in production operations, with automation I built.

Version 2 · 2026

Manual-to-evidence pipeline

Turns a vendor documentation library into a verified dictionary that the engine is allowed to quote. Every counter and alarm passes the vendor's exact ID grammar before use; full-text plus semantic search; nothing answered from memory.

72,430 verified counters and 1,255 alarm codes, up from 18,131 counters in version 1 (2023–2025).

Live · 26 tools

Self-serve diagnostic toolkit

Each tool reads one CSV export in your browser (nothing is uploaded) and returns a verdict, the evidence behind it and a summary for management: payment failures, reconciliation, OTP delivery, USSD journeys, call failure causes, power reliability, water losses, portfolio at risk, motor loss ratio, bus headways and more.

Every number is computed from your file. Sample runs are free; your own file opens with a 3-day code.

Open the catalogue →
Running

5G SA reference lab

A standalone 5G core from AMF to SCP with gNB and UE simulators. I break it on purpose and record the recovery, so every 5G claim I make comes with a baseline, a fault and a measured recovery.

6/6 baseline · UPF failure injected · recovery in about 12 s.

Proposals out

Site energy baselines and MRV

A measured energy and emissions baseline method for shared tower estates, built so that efficiency projects can be financed and their savings verified.

Method sized for a 1,467-site shared estate; climate-finance briefs prepared for a lender, a development finance institution and a national green fund.

Built

Field and RAN tooling

SectorMap, a cell-sector KPI map for radio teams; an RF drive-test toolchain with 3GPP validity ranges and PCI conflict checks; a read-only network-element access and evidence tool; signalling log triage.

Drive-test toolchain 27 tests · NE evidence tool 21/21 tests · cause values across 17 protocol families.

AI skills, applied where answers must be right

Automation that refuses to guess

Network answers are judged by the next outage, not by how fluent they sound. My AI work is built around that: retrieval that can only quote the manual, gates that reject what cannot be proved, and a human hand on every send.

 Isaano · run log, abridged
Ask
UPF restart: sessions drop. How fast do they recover?
Source
Gateway counters resolved to the manual for the exact release · ID gate passed
Lab
UPF fault injected in the 5G SA lab · recovery in about 12 s
Cause
First deviation → cause value → counterfactual checked
Open
DNS check at container level only: stated as open, not assumed
Out
Root-cause report · evidence pack · change procedure with rollback and checks at T+30 min, 24 h and 7 days
Every claim traceable to a manual page, a trace line or a lab run · Prepared by Frutos Kamanzi, CEO & Founder, SAANO AI NETWORKS
  • Retrieval that can only quote the sourceHybrid full-text and semantic search over vendor libraries; answers come from the manual for the named release, and counter or alarm IDs are checked against the vendor's grammar before they are used.
  • Fail-closed outputsWith evidence missing, the system returns the exact request (what, from which node, for which window) rather than a plausible answer. Confidence is labelled: proven, supported or unproven.
  • Guardrail verification for telecom agentsI test an agent's core-network answers against release documentation with adversarial cases locked to ground truth, and return a pass/fail report and a gate design. Ten working days, remote.
  • Agentic operations with a human on sendScheduled runs scan regulators, tenders and news, and prepare drafts and evidence packs into one approval queue. Nothing leaves without my send.
  • Evaluation of the engine itselfAcceptance tests for injected instructions, citation traps, closed questions and computations, re-run after every revision.
  • Teaching itAI for Telecom Core Operations, a five-volume handbook (184 pages); 18 incident playbooks with fix paths and verification gates.

Your story, your tools

Pick your world. Here is what I would do first.

Same method everywhere: your own export, the first deviation, the cause with its evidence, the fix order and the money at stake.

Mobile operators

The 3G switch-off is set for 30 June 2027, and it goes ahead only once VoLTE, emergency calls included, works reliably.MINICT, 27 Jul 2026

What I bring

VoLTE, IMS and core root-cause work across Ericsson and ZTE, device readiness by segment, and the site power that keeps it all up when the grid drops.

Try first

Proof

CS core lead on a 54-node Ericsson estate carrying 665,000 Erlang at 99.95%; xGW, uMAC and DSC on cloud-native ZTE platforms in production; SRVCC and VoLTE cases solved in public.

First step: send one day of SIP, Diameter and Q.850 cause codes; I return the failure tree and the fix order in 10 working days.

Get a 3-day code

Proof

Numbers from production, threads you can read

99.95%CS core network availability, sustained on a 1+1 estate
−35%recurring P2/P3 incidents after a process redesign
665,000Erlang of traffic on a 54-node Ericsson CS core
25,000+words of public diagnosis: 135 answers in 56 threads

Career

Radio to core, operator to vendor, since 2007

  1. 2007–2013Switch engineer, core and RFMTN Rwanda · Tigo Rwanda
  2. 2013–2015Standards and international roaming engineerEricsson Rwanda
  3. 2015–2023Core network engineer, acting operations managerAirtel Rwanda
  4. 2023–2025CS core SME lead, acting operations managerEricsson Managed Services · MTN Rwanda
  5. 2025–2026Senior core network expert (L6)ZTE core · Airtel Rwanda
  6. 2026 →Independent engineer and builderKigali · worldwide

Work with me

Small first step, fixed scope, then keep the tool

Trial

Three days, free. Ask for a code on WhatsApp and run any tool on your own export; the file never leaves your browser.

Read

Your full records, read with evidence: the cause, the fix order and the money at stake. Fixed scope and price, 10 working days.

Licence

Keep the tool for your team, set to your thresholds, with a monthly read-out for management.

Train

Hands-on 5G core and VoLTE training with my own lab and tooling; days and hours set with each team.

Send one export. Get one answer.

WhatsApp +250 788 312 423 · call +250 731 000 163 · fkamanzi@gmail.com

Prepared by Frutos · Kigali, Rwanda · Trial tools · Upwork · GitHub · © 2026 Frutos Kamanzi