01 / FRAGMENTED
Same entity, different records
Names, identifiers and attributes vary by source. No single system holds the whole picture.
Data infrastructure for institutions in fragmented markets
Decide which records belong together, then show why.
Phantera builds the infrastructure that lets an institution resolve records across systems it doesn’t control the shape of. Phanx proposes the links, shows the evidence and confidence behind each one, and leaves the decision to a named reviewer. Finance first, Nigeria first.
Early-stage. Built in Lagos.
PHANX · CANDIDATE MATCHIllustrative
System A · Core bankingRecord A
Adaeze OkaforID no. ending 4821 · DOB 12 Mar 1991System B · Lending appRecord B
Adaeze C. OkaforID no. ending 4821 · Phone +234 80x xxx 0142Government ID numberExact match
NameClose variant
Phone numberConflict · flagged
Likely the same person · High confidence
Every signal, weight and conflict is recorded so a reviewer can accept, reject or escalate.
Synthetic example for illustration. Not a product screenshot.
The problem
One person. Several records. No way to show they’re the same.
In markets where identity infrastructure is thin, the same customer sits in a core banking system, a newer digital platform and a handful of vendor tools, under slightly different names, numbers and formats. Teams reconcile it by hand, and often don’t get to see why two records were treated as one.
02 / UNCERTAIN
Wrong links and missed links
Look-alike records get merged by mistake while genuine matches stay hidden. A missed link leaves real history invisible. A wrong link attaches one person’s record to another.
03 / UNEXPLAINED
A score isn’t an answer
Reviewers and auditors need to see why records were linked and what is still uncertain. A number they can’t inspect is a number they can’t sign off.
Our first product
Phanx. Record resolution you can inspect.
Phanx builds every decision out of recorded evidence, so confidence is something a reviewer can open, not something they have to accept.
01Data
Records from systems you already run.
02Evidence
Every comparison becomes a recorded signal.
03Assertion
Signals support or contradict a proposed link.
04Resolution
Weighted and scored, with confidence stated.
05Decision
A named reviewer accepts, rejects or escalates.
Where the evidence is weak, Phanx does not merge on its own. It routes the case to a reviewer with the reasoning attached.
Evidence-based confidence
Weighted, configurable signals. Conflicts stay visible instead of being averaged away.
Each decision recorded
Every outcome is designed to trace back to the evidence that produced it. The full audit trail is still in build.
Hard conflicts stop the merge
A differing identifier halts resolution rather than being smoothed over.
Where we are
Built, in build, next.
Working todayEvidence model and resolution engine
Schema, signal chain, parametric weighting and conflict handling.
In buildReviewer workspace and audit trail
See the evidence, resolve conflicts and keep a record of every decision.
NextAPI and SDK
A clean integration path for developers. The relationship graph comes later, once resolution has been validated.
We say this plainly because the worst thing an institution can discover late is that a vendor overstated what it had.
Built for regulated environments
Designed to run inside your boundary.
Institutions don’t share infrastructure or governance requirements. Phanx is designed to sit inside the institution’s environment rather than pull records into a shared platform.
01
Institutional node
Phanx runs inside your environment. Your records don’t pool with anyone else’s.
02
API and SDK
For teams who want resolution inside their own products and workflows. Where it runs is still being decided.
03
Supervised evaluation
Before either: a scoped set of records you choose, processed on a machine inside your building under your supervision, with a report back. Scope, access and handling are agreed in writing in advance.
Where we begin
We start with financial institutions in Nigeria.
We start in Nigeria because it is where we are and where we can reach institutions directly. It is also a demanding place to prove the product. The problem isn’t Nigerian, and neither is the design.
Evaluation
Start with one decision, not a deployment.
We’re looking for a small number of institutions to run a scoped evaluation with us. The purpose is to find out whether Phanx is right for your records, before anyone talks about a rollout.
1
Choose one decision your team already makes
Which records belong to one person or business. The use case comes from your workflow, not ours.
2
Run it on records you control
Already-closed cases, or sample or synthetic data, on infrastructure inside your boundary.
3
Review it together, including what we got wrong
Then decide whether a production pilot is worth discussing.
Processing stays inside your environment, and the scope, access and handling of records are agreed in writing before anything starts.
Request a scoped evaluation
Working on identity, records or data integration? Send a short note on the decision you would want to test.
We read every message and reply personally.
Team
The people building Phanx.
A geologist who spent two years studying why data in fragmented markets won’t connect, and a machine-learning engineer who builds the models.
Adesoye Ibraheem Toyosi
Co-founder
Geologist by training. Spent two years studying why data in fragmented markets will not connect, and set out the evidence-based approach behind Phanx.
Kofi Opoku
Machine learning engineer
Builds the matching and scoring models. Public work includes a fraud-detection service and applied machine-learning projects.
Why we exist
Read the layers. Show your working.
A geologist reads layers of incomplete, sometimes contradictory evidence to reconstruct what actually happened. Two years studying why data in fragmented markets won’t connect turned up the same pattern inside banks: one person, many systems, and nobody able to show why two records are the same person. Phanx works the way a careful geologist does. It gathers the evidence, weighs it, keeps the conflicts visible, and shows its working.