nyuchi — a frontier-infrastructure company
Frontier infrastructure for the way the internet actually reaches Africa and emerging markets.
A growing portfolio of apps and products — payments, identity, offline-first software, and developer tooling — built on one engineering doctrine: outdoor-readable, offline-tolerant, multi-language by default. Built in Harare by nyuchi, deployed everywhere people work.
The same standard behind every product
- Harare-built since 2018
- Offline-first · 100 KB JS per route
- English · Shona · Ndebele parity
- APCA AAA outdoor-readable
Products
One credential. One operations model. A growing portfolio.
nyuchi's own apps are the front door — the API platform, web services, medical, logistics, pay, tools, and device management. Each is a standalone surface running on the same frontier infrastructure. Run one. Run them all.
Developer
Business
Operations
Engineering doctrine
Ubuntu is not a marketing claim. It is the spec.
Every nyuchi product is built against the same six constraints. They are not aspirations — they are how we ship.
-
Outdoor-readable by default
APCA Lc 90+ contrast on body text, 56-pixel touch targets, type that holds up in midday sun. The same software has to work on a verandah at noon.
-
Built for the connectivity gradient
Offline-first writes, queued sync, and a 100KB JavaScript budget per route. We assume 3G is the floor, not the exception, so a Tecno Spark and a Macbook get the same product.
-
Multi-language parity from day one
English, Shona, and Ndebele are first-class — not after-thought translations. Every string externalised, every layout reflowable, every voice flow recordable in the user's language.
-
Shared-device aware
Account switching, family modes, and dignity defaults. We design for households and clinics where one phone serves five people, and never punish someone for the device they own.
-
Personal data lives with the person
One architecture for everyone — organisations, consumers, communities, governments. Personal data sits on your device or in your Web3 pod under your keys; the platform has no copy and cannot read it. Platform data lives in specific open regions per an open-data policy, and aggregate insights become an open commons for the continent.
-
No surveillance business model
No dark patterns. No ad-tech reselling. No upsell-by-degrading-the-free-tier. The business plan is software people pay for because it does the job — not because it traps them.
The wider ecosystem
nyuchi is the workshop. bundu is the village.
The bundu foundation is the umbrella under which our work sits — three pillars it governs: nyuchi (the frontier-infrastructure company and its products), mukoko (consumer), and shamwari ai (community). nyuchi builds the infrastructure underneath all three, and sells it direct to organisations and governments.
One identity. One design system — mzizi, open and installable. One open data commons. Different surfaces for different rooms in the house.
Frequently asked
Short, direct answers to the questions we get most.
What is nyuchi?
nyuchi is a Zimbabwean frontier-infrastructure company. It builds the payments, identity, offline-first apps, and developer tooling that emerging markets run on — a growing portfolio of its own products, from the API platform and web services to medical, logistics, pay, and device management. Founded in Harare in 2018 by Bryan Fawcett, nyuchi operates inside the bundu ecosystem.
What does "frontier infrastructure" mean?
Frontier infrastructure is the engineering layer for places where bandwidth, devices, and budgets are constrained. nyuchi designs every product to be outdoor-readable, offline-first, multilingual, and shared-device aware so the same software works on a Tecno on a verandah and a Macbook in a city office.
What is mukoko?
mukoko is nyuchi's consumer super-app — one product in the portfolio, built on the same frontier infrastructure as everything else. It shares one identity, one payments rail, and one offline-first sync model with the rest of the stack. nyuchi builds and operates the infrastructure; the bundu foundation governs it.
How does offline-first work in nyuchi products?
Writes happen locally first, queue when there is no network, and reconcile when one returns. Personal data lives on the device or in a Web3 pod under the user’s keys — never in a nyuchi-readable copy — so the experience is identical online or off.
Where can I read your engineering doctrine?
The principles — outdoor-readable defaults, connectivity-gradient design, multi-language parity, shared-device awareness, sovereign data, no surveillance — live on the homepage under "Engineering doctrine". The blog covers the same ideas in longer form.
Build with us, or buy from us.
Self-serve sign-ups for the API platform and tools. Deployed engagements for everything else. Either way, you get the same engineering doctrine.