Skip to content

nyuchi — infrastructure, and the products built on it

The infrastructure Mukoko runs on. And the products we build with it.

Nyuchi builds and runs the Nyuchi API, the console, and the Mzizi design system — the platform underneath Mukoko and every Nyuchi product. On top of it we ship our own products: Mukoko, Nyuchi Learning, and tools for organisations. Built in Harare.

What Nyuchi runs

Mukoko apps running on it today:

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

The infrastructure

Mukoko sits on Nyuchi. So can you.

One API, one console, one design system. Every Mukoko app and every Nyuchi product reads and writes through the same platform — the same platform organisations can build on.

  • Nyuchi API

    Live

    The one API every Mukoko app and Nyuchi product reads and writes through: identity, organisations, workspaces, places, events, news, weather and more.

  • Nyuchi console

    Live

    Where organisations sign in, manage their workspaces, and issue API keys for the platform.

  • Mzizi

    Live

    The open design system every Nyuchi and Mukoko surface is built with — components, tokens, a registry API, and the @bundu/ui package. Governed by the Bundu Foundation.

  • Nyuchi AI

    In development

    The AI layer inside the platform. Its consumer face is Shamwari, an African AI companion that answers in Shona, Ndebele and English and cites its sources — being built in public.

Built by Nyuchi

We build products on our own platform.

The best test of the infrastructure is shipping on it. These are ours.

Consumer · mukoko.com

Mukoko

Africa's super app, and Nyuchi's largest product. Every Mukoko app runs on the Nyuchi API — one identity, one data platform. The apps already live on the web:

Education · Nyuchi Learning

Nyuchi Learning

Classroom tools and training for schools. First out: theToddle Enhancement Extension, live on the Chrome Web Store. It expands every rubric in the Toddle gradebook into per-criterion columns, exports them to CSV, and hides student flags with one switch so you can share your screen safely.

Core features are free. An organisation licence, covering your whole school domain, is US$149.99 a year.

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 is designed to sit on your device or in your Web3 pod under your keys, where the platform has no copy and cannot read it (pods are in development). 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 — four pillars it governs: bundu labs (research), nyuchi (the frontier-infrastructure company and its products), mukoko (consumer), and shamwari ai (community). nyuchi builds the infrastructure underneath the other pillars, 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 technology company with two jobs. It builds and runs the infrastructure — the Nyuchi API, the console at platform.nyuchi.com, and the Mzizi design system — that Mukoko and its other products run on. And it builds products on that infrastructure: Mukoko, Nyuchi Learning, and services and tools for organisations. 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 a super app built by nyuchi, and nyuchi's largest product. It sits on nyuchi: every Mukoko app — Mukoko Events, Weather, News, Kweli and the rest — reads and writes through the Nyuchi API under one identity. Its home is mukoko.com.

What is Nyuchi Learning?

Nyuchi Learning builds classroom tools and training for schools. Its first product, the Toddle Enhancement Extension, is live on the Chrome Web Store: it expands Toddle gradebook rubrics into per-criterion columns, exports them to CSV, and hides student flags with one switch. Core features are free; an organisation licence is US$149.99 a year.

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 is designed to live on the device or in a Web3 pod under the user’s keys (pods are in development) — 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.