Izere/Team

Built by someone who has worked
inside the system.

Izere is being built from a simple conviction formed over a career inside public-capital programmes: the execution gap is an intelligence problem, and the data to close it already exists.

Portrait · 2026

Co-founder · CEO

Alain Nkurikiye

Advisor · EC Advisor · AfDB DFI consulting Public investment

Alain has spent his career advising on the design, supervision, and execution of public-capital programmes — consulting work for the European Commission, the African Development Bank, and a portfolio of development finance institutions across Europe and Africa.

The pattern across that career: institutions could commit capital with extraordinary scale, and could not systematically deliver on it. The diagnostic frameworks were retrospective; the supervision tools were linear; the monitoring data was fragmented. Programme failures were structural, not financial — and almost always visible months before they were officially detected.

Izere is built to read what institutions already produce, in a way that a programme manager — and an institutional auditor — can both read end-to-end.

The capital is not the constraint. The capacity to read what the capital is doing is the constraint.

How we work

Three operating principles.

These are not posters on a wall. They are how we make decisions when there is genuine tension between speed, scope, and rigour.

P / 01

Auditable by construction.

If a feature, a score, or a deployment cannot be reviewed end-to-end by an institutional auditor, we do not ship it. This is a hard constraint, not a preference. It rules out whole categories of architectural choices that other ML companies make.

P / 02

Decision-support, not decision-making.

Izere informs institutional judgement. It does not automate it. No score triggers automated procurement, financial, or supervisory action. Every outcome flows through human institutional sign-off — and the system is designed so it cannot be otherwise.

P / 03

Sovereign by default.

EU-only hosting. Federated training. Customer-managed keys. Zero US-jurisdiction routing at any layer. Sovereignty is the deployment default, not an upgrade. The buyer should never have to ask for it.