We study how
Cameroon works.
Then we build.
Ubora Labs is a technology research and development studio. We identify gaps in digital infrastructure, and build systems to fill them, from the ground up.
Most software built for African markets is adapted from products designed elsewhere. We work the other way.
We spend time understanding how things already work: how schools collect fees, how landlords and tenants negotiate trust, how skilled tradespeople find clients, how creators get compensated. Then we build infrastructure around those realities, not against them.
The result is a portfolio of interconnected systems sharing a common payment and identity layer underneath. Each product starts as a research question. Each one is an answer we're still refining.
We study what already works before proposing what's new. Local behaviour is the design spec.
Ship to production early. Harden fast. Build for 2G. No assumptions about connectivity or device.
Shared infrastructure across products. Solve mobile money once. Solve identity once. Then build everything on top.
Transactions processed. Trust built. Problems that no longer need workarounds. Not vanity metrics.
Four questions.
Four products in production.
Every product in the lab starts as a problem observed in the field, sharpened into a question precise enough to build around.
-
How do schools manage fees, records, and report cards without disrupting how they already work?
Ubora ÉcolesSchool infrastructure · EdTechDigital fee collection, student records, parent communication, and report cards, built around how Cameroonian schools actually operate. Not a replacement. An amplifier.
-
How does a skilled provider's reputation travel beyond the two neighborhoods they've already worked in?
Ezra ServiceHome services on demandA home-services marketplace across Cameroon. Providers are rated by their clients and paid when the job is done. The network does what word-of-mouth used to, at national scale.
-
How does a tenant prove they pay on time when there's no credit bureau and no formal lease history?
Ubora LivingRental infrastructure · PropTechEvery on-time Mobile Money payment builds a Rental Score. Tenants accumulate a verifiable history. Landlords get signal beyond gut instinct. A trust layer built on local payment behaviour.
-
How do creators in Cameroon get compensated without routing through platforms built for other markets?
KreastarLocal influencer marketingA marketplace connecting Cameroon's micro-influencers with local brands. Creators get discovered, book campaigns, and receive payment directly. No international routing, no percentage lost to platforms built for other markets.
The layer underneath
everything
The four products above share a common foundation. We built the payment and identity layers once, so every product built on top of them inherits the solution, not the problem.
Ubora Pay
A unified payment API connecting MTN Mobile Money, Orange Money, and more. When operators update their APIs, only Ubora Pay updates, so every product built on it stays working. We're opening this infrastructure to other builders in Cameroon. Integrate once, go live fast.
Ubora ID
A digital identity layer for the ecosystem. It will power KYC for Ubora Pay, tie Rental Scores to verified individuals in Living, anchor patient records in Health, and verify providers on Ezra. One identity. Every platform. Available as an API for any builder who needs it.
From the lab,
in long form
We publish what we learn. The problems, the tradeoffs, the reasoning, written for other builders, not for press releases.
Why African Tenants Need a Rental Score
Millions of renters across Africa have no credit trail, no formal lease history, and no way to prove they pay on time. We built Rental Score to change that.
Read article FinTech · PaymentsThe Mobile Money Fragmentation Problem in West Africa
MTN. Orange. Moov. Every operator runs its own API. Every developer integrates each one separately. We think there is a better way.
Read article Engineering · DesignDesigning Software for Low-Data Realities
Most software is built assuming fast Wi-Fi and unlimited data. We build in the opposite direction. Here is what that actually looks like in practice.
Read articleQuestions we're
still studying
These are open problems. We don't have the products yet. Just the questions.
How does a patient's medical history follow them across clinics when there's no shared record system?
The carnet de santé gets lost. The clinic changes. The patient starts over. We're studying what a patient-owned medical record looks like in the Cameroonian context.
How do you verify identity for financial and healthcare services when formal ID is inconsistent?
The infrastructure layer for the questions above. Identity that works across the whole ecosystem, not another silo.