04Work
Carried for other people.
Some of this runs under contract terms that limit what we can describe. Where that is true the page says so and names the boundary. No metrics appear anywhere here: someone else’s numbers are not ours to publish.
Index
- 01RestrictedBorder verification, offlineEdge nodes for a police information system rollout, built to keep working when the satellite link does not.Public safety2025
- 02RestrictedField capture on a bad connectionAn offline-first data entry interface for remote clinics, built so an outbreak signal is not lost to a dropped connection.Global health2025
- 03
Business ReportAn independent Kenyan business publication, rebuilt as a server-rendered newsroom its editors run themselves.Publishing2026 - 04
Khendo FMA radio station whose website is part of the transmission rather than a poster for it.Broadcast2026 - 05
COFEKA rebuild of cofek.africa for the country’s consumer watchdog, an organisation whose credibility is the product.Civil society2026
Pattern
What these share is not a sector. It is that the software was load-bearing for something that mattered more than the software.
An archive cited for years. A station people tune into daily. An officer at a border with a person standing in front of them. A clinic on a connection that comes and goes. In each one, the thing being carried was already important before we arrived, and the job was to not be the reason it stopped working.
That changes which problem is interesting. On the rebuilds it is migration, because an audience is lost in the URLs rather than in the design. On the restricted work it is what the system does when the network is not there, because the answer to that decides whether it can be relied on at all.
Who did it