Work
Carried for other people.
Some of this is 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.
01
Border verification, offline
Edge nodes for a police information system rollout, built to keep working when the satellite link does not.
Public safety · 2025
02
Field capture on a bad connection
An offline-first data entry interface for remote clinics, built so an outbreak signal is not lost to a dropped connection.
Global health · 2025
03
Business Report
An independent Kenyan business publication, rebuilt as a server-rendered newsroom its editors run themselves.
Publishing · 2026
04
Khendo FM
A radio station whose website is part of the transmission rather than a poster for it.
Broadcast · 2026
05
COFEK
A rebuild of cofek.africa for the country’s consumer watchdog, an organisation whose credibility is the product.
Civil society · 2026
What these have in common is not a sector. It is that in each one 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 in front of them, a clinic on a connection that comes and goes.
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.