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 health ministries whose budgets are set in local currency — and exchange-rate volatility makes recurring foreign subscriptions harder to plan every year. Budgets that could fund a local team end up 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. These requirements — in-country data, offline capability, government-owned infrastructure — are not edge cases in Sub-Saharan health systems. They are the baseline.
What we built
Opian designed its platforms for data sovereignty and low-connectivity operation from the start. Deployments run on infrastructure the government controls — on-premise, in-country, or on the ministry's preferred hosting — rather than on a foreign vendor's cloud. The systems are modular and containerized, running on standard server hardware without expensive licensing. Data collection is offline-capable for facilities with unreliable connectivity, syncing when a connection is available. The data stays in-country. Opian does not pull country data to its own servers for analysis; the country's own analysts work on their own infrastructure. And because the government owns the deployment, it could maintain the system independently — or hand it to another vendor — without data loss or lock-in.
What changed
For Ethiopia: ForLab+ has run in-country, at national scale, since 2022. The ministry side owns its data and infrastructure; Opian does not extract facility data to its own servers, monetize user activity, or create private data lakes. Deployments are modular, containerized, and can run on-premise or on the government's preferred infrastructure — with no SaaS lock-in and no foreign cloud dependency. For the pipeline: this deployment model is central to how Opian approaches expansion. Our active Phase 1 pipeline — Nigeria, Tanzania, Uganda, and Mozambique — is built on the same premise: donor-funded entry transitioning to government licensing, on infrastructure the country controls. Sovereignty here is not a slogan; it is a set of design constraints we accept on purpose: no foreign data extraction, in-country deployment options, and systems a government could continue operating if Opian walked away tomorrow.
"Country data stays in-country. Platforms are licensed to ministries, not rented from foreign clouds."