OAN Kenya
Date: 2026-08-10 People and teams:
Infrastructure & implementation — SAFIC: Led by Prof. Simon Wagura Ndiritu, SAFIC drove the hands-on implementation that turned the Sprint-1 vision into a working deployment. Joseph Gitonga provided technical leadership and coordination; Michael Gichure led infrastructure and deployment readiness; Peter Gicharu drove ONIX deployment and provider onboarding; Isaac Masinde and Braico Mwangi led Seeker implementation and validation; and Charles Mwaniki supported onboarding, integrations, payload mapping, telemetry, and observability. Together, the team deployed the network, onboarded providers, validated the first live transaction, and demonstrated the first end-to-end use case on the OAN Kenya network.
Program leadership — COSS: Jagadish Babu, COO of Ek Step, set the founding vision. Anand Varada, Thejaswini Anand, and Nirant coordinated the broader OAN ecosystem, aligning scope, priorities, and success criteria while enabling the delivery team to move quickly and make decisions on the ground.
Technical enablement & architecture — Deloitte: Tejash, Kanak Kaushik, and Rupal Singla provided architecture guidance, provider onboarding, payload mapping, integration support, troubleshooting, and implementation artifacts that enabled rapid deployment and validation of the Seeker and Provider components.
Program delivery & governance — Deloitte: Nanda Kishore led sprint execution through a clear day-by-day delivery plan, proactively managing dependencies, risks, and blockers. Meenakshi Rampati provided program-level support throughout the engagement.
This milestone was the result of the entire OAN Kenya team working together—combining ecosystem leadership, program governance, technical enablement, and hands-on implementation to move from vision to a live end-to-end transaction.
The win
OAN Kenya Goes Live with Its First End-to-End Transaction
On 3 August 2026, OAN Kenya successfully completed its first live, end-to-end transaction—marking a major milestone in the journey from network setup to a fully functioning ecosystem.
A live search request successfully travelled across the entire network—Seeker (BAP) → Adapter → Gateway → Provider (BPP)—and returned a real-time weather advisory response. For the first time, all layers of the OAN Kenya network worked together seamlessly in a single continuous transaction.
In just five working days, OAN Kenya moved from initial network setup to its first live transaction. Within the first week of Sprint 1, both Seeker and Provider sides were brought online, integrated, and validated through a real network exchange.
This milestone demonstrates more than technical integration—it validates the OpenAgriNet model’s ability to rapidly bring ecosystem participants onto a shared, interoperable network architecture and translate individual components into a functioning digital ecosystem.
From components to connectivity. From setup to live exchange. OAN Kenya is now a working network.

The path of a single search request through the OAN Kenya network: from the Seeker application to the Weather Provider and back
Why it matters
This win validates the foundational architecture of the OAN Kenya network and demonstrates that its core components are operational and interoperable. The Seeker application, network infrastructure, and Weather Provider successfully exchanged information in real time, confirming the viability of the network and its onboarding approach.
The successful transaction establishes a working foundation for scaling the ecosystem, enabling future Advisory, Market Information, and other provider services to connect and deliver value through the same interoperable network.
SAFIC’s Sprint-1 Reflections
The first week of Sprint 1 was marked by rapid learning, strong ownership, and accelerated execution.
From unfamiliar to confident: The team moved quickly through the initial learning curve, using hands-on implementation, onboarding documentation, and architecture walkthroughs to build practical confidence.
Rapid execution and ownership: Within the first week, SAFIC deployed the core network components, onboarded both the Seeker and Provider applications, and completed the first live end-to-end transaction.
The result: The planned Sprint-1 demonstration was scheduled for Day 10, but the team achieved a live end-to-end transaction on Day 6—four working days ahead of plan.
Planned: Day 10 | Actual: Day 6 | 4 days ahead of plan
Key Outcomes
Registry and Gateway deployed and operational
Seeker application connected
Weather Provider successfully onboarded
First live end-to-end Weather use case demonstrated
First live OAN Kenya transaction completed
Sprint-1 Win 1 achieved, establishing a validated foundation for onboarding additional providers
Notes
While this milestone focused on a single Weather use case, it validated the architecture, onboarding approach, and operational model that future providers will build upon. The next phase will focus on Agricultural Advisory services, telemetry, and onboarding additional providers using the same repeatable framework.
Key lessons carried forward as follow-up practice:
Lesson
Applied as
Keep the scope deliberately narrow for a first milestone -- proving one use case end-to-end made it possible to find and fix problems quickly instead of debugging several moving parts at once.
Continue onboarding additional providers one at a time using the same repeatable framework, rather than in parallel.
Resolve blockers the moment they surface -- the team used the working WhatsApp group to flag and close issues in real time rather than waiting for the next scheduled call.
Keep same-day blocker resolution as the standing practice for the next milestone, not just this one.
Good documentation is a force multiplier for a new team -- clear, step-by-step build documentation and an upfront architecture walkthrough meant the team didn't have to learn by trial and error.
Invest in documentation and a walkthrough ahead of every new milestone, not just this one.
Give the team closest to the work the autonomy to make decisions and execute -- clear goals from program leadership, paired with trust in the delivery team's day-to-day judgment, kept decisions moving.
Preserve the same light-touch governance model as onboarding scales.
Celebrate the first one properly -- taking time for a team photo and writing this entry is how a program builds a record it can look back on.
Keep documenting each milestone this way going forward.
Last updated