Exchange connectivity and matching engines
Consulting on exchange connectivity, FIX engines, and matching engines for electronic trading in listed markets and crypto.
What this work is
We build and advise on the software that connects a trading system to a venue, and on matching engines when the brief is the book itself. Connectivity covers the session, the messages, and the recovery behaviour when the session fails. FIX engines are the usual form of that work in listed markets, and they appear in crypto where a venue has chosen FIX. A matching engine is a different component. It accepts orders and produces trades on its own book.
These pieces fail in ordinary operational ways. A sequence number gap, a silent socket, a cancel that was sent and never acknowledged, a logon that succeeded against yesterday’s configuration. The implementation has to make those states visible and recoverable. A strategy cannot decide well if the session under it is dropping messages, and an operator cannot repair a failure the software does not show.
The same care applies to a matching engine. The book has to follow the venue’s own rules for price and time. Trades, cancels, and the market data leaving the engine have to tell the same story. That consistency is the job, for a new engine and for a change to one that already matches.
Who it is for
Clients are brokers and trading firms that need a reliable path to one or more venues, and organisations that run a book of their own. The venues may be equity, futures, options, FX, or crypto. The asset classes we have worked across are listed on the services page. The usual caller is adding a venue, replacing a session layer, or trying to understand an engine they already run.
We have done this inside large platforms at investment banks and in smaller systems built for a single team. A bank connectivity stack already has certification, shared services, and a change process. A smaller firm may be bringing up its first session. Both need software that can say what was sent and what the other side acknowledged.
Typical work
On the connectivity side, the work is the session and the messages. Logon and logout, heartbeats, sequence recovery, order entry, amends, cancels, and execution reports. Where the venue speaks FIX, a FIX engine is the centre of that work. Where it does not, we implement the interface the venue documents, and we keep the platform’s view of an order stable so the rest of the system is not rewritten for each venue. A venue’s quirks have to be visible. If they are hidden, nobody can diagnose a reject.
Recovery is part of the build. After a drop, the engine has to know which orders it believes are working, and how it will confirm that with the venue. We design that resynchronisation with the operations staff who will run it at the open.
On the matching engine side, the work is the book and the rules. Order types the venue supports, the priority of resting orders, how a trade is printed, and how the market data relates to the trades. We also look at the path in. Who can enter an order, what a risk or credit check is allowed to stop, and how a halt or a session state is represented. A matching engine has to be able to explain a trade.
The trading logic that decides to send an order is covered on the algorithmic trading page, and the crypto venue work on the crypto trading page. This page is the session, the messages, and the book. Implementation languages are on the about page.
How an engagement runs
A single session can be a review of a FIX specification, a recovery design, or a matching engine behaviour that the team cannot explain. Building a session or changing an engine takes a larger block, often across certification with the venue. A retainer fits when several venues, or a long certification, are in flight. See consulting packages for the sizes.
Contact us with the venue or the engine, and with what is failing or what you need to add.