Software that holds its invariants

Payment and banking systems that cannot get into invalid states. Invariant Software builds and hardens financial software so that whole classes of failure, such as double debits, lost transactions and impossible balances, are ruled out by design rather than caught in production.


An invariant is a property guaranteed to hold no matter what the rest of the system does. We named the company after it because that is the standard we hold our software to.

What we believe

Most software fails not because the problems are hard, but because invalid states are allowed. We design systems where illegal states cannot be expressed, so the compiler catches the mistake instead of the on-call engineer at 3 a.m.

Where we work

We focus on systems where a wrong state costs money: payments, banking integrations, ledgers and the APIs between them, for fintechs and banks in Nigeria and across Africa. We build new systems in OCaml, and we bring the same discipline to the code you already run in Kotlin, Java and other languages, including code written with AI assistants: we write the contracts, and the compiler checks every implementation against them, whoever wrote it. See our services →

Start small: an invariant audit

Pick one critical service. In two weeks we map the states it can reach that it never should, and deliver a written report with concrete fixes ranked by risk. You keep the report whether or not we work together again. Ask about an audit →

Built in the open

We use our own tools and contribute to the open-source software we rely on. Our first product, Chaufr, a trust-centred chauffeur marketplace built entirely in OCaml, launches in Lagos this December.

Latest writing

Great engineering can come from anywhere. Let's build something that lasts.