Monivero KYB
Monivero is an early-stage compliance product, not public yet, so this covers only the part I built: the KYB flow. An analyst enters a company registration number, watches every public register and every sanctions/PEP check resolve in real time, and gets back a report where each fact carries its source.
- One numberIn, full sourced report out
- Live runStreamed progress, not a spinner
- SourcedEvery value, with retrieval time
01Context
The KYB module answers one question for a regulated customer: who is this company, and is there anything on it. It pulls the public registers a Czech company appears in, screens the company and its current officers against sanctions and PEP lists, and turns the result into a filable report.
The product is pre-launch, so this case study stays on my side of it: the run, the waiting, and the report.
02The challenge
A check like this is slow. Querying every register and screening each officer takes minutes, not milliseconds, and the first version showed a disabled button for all of it. From the outside, a working check and a stuck one looked identical.
The second problem is trust. A report that looks clean because two registers never answered is worse than no report at all, so coverage cannot be a footnote.
03What I built
The run streams. Submitting the form swaps it for a live progress view that lists the whole plan up front, every register and every screened party, then resolves each one to what actually happened, failures included. The old blocking path was deleted rather than kept as a fallback: two code paths that run the same check differently eventually disagree about what was checked.
The report screen puts coverage before conclusions. What ran, what failed, and what was skipped sits directly under the red flags, and every value carries its source, retrieval time, and the register's own data version. The same screen prints to a PDF an analyst can file, while the on-screen version keeps the raw upstream responses available for anyone who needs to argue with a finding.
04Outcome
The flow runs end to end: a check, a stored report, and standing monitors that re-run a saved company on a cadence and email a change report when the facts move.
Monivero is not public yet, so there is little more I can show. The interesting part was the same one as in KYC work: a compliance process that people can actually see happening, without softening what it found.
Client companies are not named here, and their logos and screens are not shown. That is by agreement between the parties: the work is mine to describe, the brand and the product are theirs. Everything above is the engineering problem and my part in it.