FinBlocks Tech builds the engine underneath an auction market. Mehrexis our trading-system product line: matching engine, Market Control Panel, client front-end, risk, clearing and market data, delivered as one sequenced path rather than a shelf of integrations — and configured for whatever is being traded, from fractional gold to a national securities market.
We are not trying to be the cheapest software in the room. We are trying to be the shortest honest path between a market model on paper and a market that trades, at a price a regional venue can actually carry.
Market infrastructure has traditionally been sold as a nine-figure, multi-year programme. Mehrex is a product, licensed per venue, configured for your market rather than rebuilt for it — so the number at the bottom of the proposal is a different order of magnitude.
Instruments, tick tables, calendars, sessions and risk profiles are configuration, published from the Control Panel as versioned bundles. The work between signature and a traded order is configuration and testing, not a bespoke build.
We start from your market model, not ours. The workshop maps your sessions, priority rules, clearing arrangements and regulatory regime onto the platform, and we say plainly which parts are standard and which need work.
<1 ms
Typical order round-trip on commodity hardware
Provable
Every trade reproducible exactly from the journal
Any asset
One matching model, configured not coded
Day one
Every module a market needs, in the box
In a regulated market, a fast-but-occasionally-wrong matcher is worthless. The core is deterministic and journaled: every accepted command is written to an append-only sequence before it executes, and the same ordered input reproduces the same trades on any replay. On any internal inconsistency the affected market segment halts rather than emit an incorrect trade.
New instruments, new sessions, new risk profiles — and even a new asset class — are Control Panel configuration, not a software release. Changes are versioned, approved under four-eyes control, and applied without downtime. A venue that cannot change its own market model without waiting on a vendor release does not really control its market.
Maker–checker approval and role-based access sit on every market-affecting action, rejects name the limit and the scope that tripped, and the audit trail reaches into the matching core itself. Operator actions travel the same sequenced path as orders, so market operation is as auditable as trading.
A trading system is not a delivery, it is a relationship with an operating market. The platform ships with structured documentation, a customer-testing programme, and named technical account management for the evaluation, the launch and the live service.
Mehrex clears: each trade is stamped with its clearing type and matching type, multilateral netting per participant and settlement date produces net obligations on configurable cycles, fees and commissions are computed per trade, and enriched trade-capture records are emitted for downstream consumers.
Settlement itself is not ours. It is performed by a downstream settlement module, or by your existing CSD or registry and banking integration, consuming the clearing messages the engine emits. That boundary is deliberate: it keeps the trading core independent of any particular settlement regime, so the same engine runs in a T+2 book-entry market and in a market with its own central depository and its own cash leg, without a fork.
Three more things we are honest about:
How the matching engine, Control Panel, front-end, risk, clearing and connectivity compose into one validated, sequenced path.
See the architecture →TechnologyWhat is journaled, in what order, and what exact replay buys an operator, an auditor and a regulator.
Read the principles →EngagementMarket model workshop, configure and test, then go live and support — with the outputs each phase owes you.
How delivery works →DocumentationFive guides, how they are version-controlled, and how to request the one an evaluation team reads first.
See the documents →A live demonstration runs about an hour: the order book, the Control Panel, an auction uncrossing, and a replay of the journal that produced it.