The problem
Most Sub-Saharan African health systems rely on data infrastructure hosted outside the continent. A country's supply chain data, patient records, or facility performance metrics live on US or European servers, subject to foreign data residency laws, pricing tiers set in USD, and terms of service written by vendors thousands of miles away. This dependency creates three concrete problems: First, sovereignty. A ministry wants to own and control its data. If a vendor shuts down or changes terms, the government has limited recourse. Data might be held hostage, deleted, or transferred to competitors. Second, cost. Cloud services priced in USD are expensive for African health ministries with limited budgets. A $1,000/month SaaS tool becomes ETB 60,000/month when exchange rates are unfavorable. Budgets that could fund a team are spent on software subscriptions. Third, connectivity. Sub-Saharan infrastructure is improving but remains fragmented. A health system in rural Ethiopia or DRC can't reliably depend on internet-connected cloud services. They need software that works offline and syncs when connectivity returns. Ethiopia's Ministry of Health was explicit: "We need our data in Ethiopia. We need a system that works offline. We need to own the infrastructure, not rent it." Other African health ministries have expressed similar requirements.
What we built
Opian designed ForLab+ from the ground up for data sovereignty and offline-first operation. The platform runs on infrastructure owned and controlled by the government—in Ethiopia's case, EPSS's own servers in Addis Ababa. The system is fully modular. A country can deploy the forecasting module, the reporting module, the analytics module, or all three, depending on need and budget. Each module is containerized and can run on standard server hardware (no expensive licensing). If a country wants to run Opian offline across 5,000 facilities with one central hub that syncs when possible, that's the deployment model—and it works. We also built an offline-capable client layer. A facility manager in an area with unreliable internet can work offline, submit their forecast, then sync when they have connectivity. The platform handles conflict resolution if two facilities edit the same data. No internet means no delay. The data stays in-country. We don't pull aggregate dashboards to Opian's servers for analysis. The country's own data analysts can run queries, build reports, and discover insights on their own infrastructure. If Opian's team ever leaves a country, the government owns the full system and can maintain it independently or hand it to another vendor—no data loss, no lock-in.
What changed
For Ethiopia: ForLab+ has been running on EPSS infrastructure for 4+ years. The Ministry of Health has complete ownership and visibility into the system. No data leaves the country. The system is maintained by both EPSS's technical team and Opian's engineers. Total cost of ownership is significantly lower than a comparable SaaS subscription. For the pipeline: This model has become a proof point. When Opian pitches to other African ministries (Nigeria, DRC, Kenya, Tanzania), the conversation starts with "Ethiopia built this on their own servers." That credibility has accelerated conversations with 8 countries now interested in similar deployments. One Ministry of Health leader said: "We saw what Ethiopia did. We want the same. We want our health system's data in our country." The sovereign infrastructure approach also enabled something unexpected: government data governance. Ethiopia's Ministry can now audit who accessed what data, when, and for what purpose. They can apply their own encryption standards and security protocols. They're not dependent on a vendor's security roadmap or data privacy policies written in English that they can't negotiate. Regional health bureaus in Ethiopia have begun requesting direct access to facility-level data for their own planning and monitoring. Before ForLab+, that access would have required a vendor to grant it. Now it's a native feature because the government owns the infrastructure. One consequence: other African governments are asking Opian, "Can we start planning for this kind of deployment?" The answer is yes, and we're now working with Nigeria's Ministry of Health and Tanzania's PEPFAR team on sovereign deployment models.
""We don't have to ask permission to see our own data. That changes everything about how we can govern health systems.""