For Government
We build what a country should not import.
Software and hardware for the records a state keeps about its people: who they are, what they are owed, what they have achieved. Built with the institution that will run it, and handed over.
The problem
A state is only as good as its records.
Duplicate beneficiaries, workers on the payroll who do not exist, people who cannot prove who they are, results no one can stand behind. Every one of them is a record the state keeps about a person that is not true, and every one costs money, trust, or both.
These records rarely get fixed because the systems that hold them are rarely the state’s own. They are specified elsewhere, built elsewhere and operated under licence. The state holds the obligation; someone else holds the source, the roadmap and the renewal date. A ministry that cannot alter its own system cannot respond to its own policy, and when the contract ends, the capability leaves with the vendor.
What we build
Where the work is now.
- Palm Identity Network
- Strengthens trust between people and the institutions that serve them, by verifying a person from the vein pattern beneath the skin of their palm. Enrolment does not require a prior document, so a register can be built from the people themselves.
- EDU AI Research
- Marks exams at scale with results a school can stand behind, flagging what it is unsure of for a teacher to check. Piloted in Kenyan classrooms under a 2025 memorandum with the State Department for Foreign Affairs.
How we work
Build it so it outlives us.
- The institution holds it. What we build is operated by the body responsible for it, on infrastructure that body controls. It does not sit in a vendor’s custody.
- Designed for the last mile. Intermittent connectivity, shared terminals, minimal training. A system that only works in the capital has not solved the problem.
- Built here, for the long run. The engineering happens in Nairobi, with people who stay after the launch. This work is measured in decades, and we staff and contract accordingly.
How an engagement starts
Bounded before broad.
- 1. A defined problem
- One service, one county, one record that needs to be true. Not a national programme on day one.
- 2. A measured pilot
- A baseline taken before any work begins, so the result can be judged honestly against it.
- 3. Scale, or stop
- If the pilot moves the baseline, it grows with the institution that runs it. If it does not, we say so.
Questions
Common questions
What does Hurman provide to governments?
Software and hardware for the records a state keeps about its people, operated by the institution itself rather than rented indefinitely. Current work spans the Palm Identity Network and EDU AI Research in Kenyan classrooms. Hurman works on long horizons with public bodies, and builds so that the capability stays with the state.
Who holds the data?
The institution does. Hurman’s position is that a public system is sovereign infrastructure and cannot sit in a vendor’s custody. Deployments are designed so that the operating body holds and controls the system and its data, and so that both survive the end of any commercial relationship with Hurman.
How does an engagement begin?
Usually with a defined problem and a bounded pilot rather than a national programme: a single service, a single county, a measurable baseline. Write to enquiries@hurmangroup.com. We reply within two business days.