Blog / Introduction
Your next market, not your next data silo.
For two years I have been building something I have hardly talked about in public. Time to change that. OpenMDTA is infrastructure for market and reference data, built for fintechs, on more than twenty years of experience founding and running a fintech.
Paul Mallach, founder of OpenMDTA · October 2026
01 / THE PATTERN
The fourth integration hurts more than the first.
I have seen the same pattern many times. A fintech succeeds, the product grows, and new markets and features are on the roadmap. Suddenly everything hinges on the data: one vendor per market, each with its own identifiers, its own fields, and its own opinion on what an instrument is called. The result is a data estate that was patched together during the growth phase.
Every new market adds another integration, another mapping, and another set of edge cases that only a few people understand.
02 / OPENMDTA
Many feeds in. One typed SDK out.
- Feeds in, SDK out. Price and reference data feeds go in; a typed SDK for your developers comes out.
- Remix, not one-size-fits-all. You build your own dataset from all sources. You decide which source wins for each field, what the fallback is, which instruments are admitted, and which key figures you add. It stays your data model, not your vendor’s.
- Everything in one place. Prices, reference data, search and filters, including your own fields, as if they were part of the standard.
- Day 2 operations included. Data corrections with a reason and an expiry date, license provenance for every value, and schema updates that never silently break a client.
03 / WHERE IT STARTED
Recovery at the core.
It started with a question. Data and connection failures are part of everyday operations, so why are they so often handled as rare exceptions? I wanted a system with recovery as a load-bearing part of the architecture, not an emergency plan. That decision turned out to have side effects I had not expected, which I describe in Recovery as a principle, not a patch.
04 / WHY IT MATTERS
Table stakes, not differentiators.
Prices, reference data, and identity are the three areas every market data stack has to get right. None of them makes your product special. No customer chooses you because your identifiers are mapped cleanly. But everyone notices when they are not.
That is exactly the work nobody should have to build again for every product, and the work OpenMDTA takes off your team’s plate.
Facing your next market?
I am looking for pilot customers: fintechs with traction, several data feeds, and a new market on the roadmap.