A spot exchange with a matching engine built for latency, not just liquidity — order book, wallet custody and compliance in one stack.
A spot exchange built around a matching engine designed for latency first — the order book, wallet custody and compliance layer all had to fit around that constraint, not the other way round.
The client needed to compete for institutional order flow, which meant execution quality had to hold up under load. Most exchange software is built for feature breadth first and discovers its latency problems after launch, when fixing them means a rewrite.
We built the matching engine first, in Rust, sub-millisecond under load, and fit everything else — custody, compliance, the API — around that constraint rather than bolting latency fixes on afterward. Custody got equal priority: hot/warm/cold wallet separation with multi-signature withdrawal approval, because a fast matching engine means nothing if custody is the weak point.
The exchange now handles institutional-grade order flow with sub-millisecond matching, and passed both a security audit and penetration testing before its first dollar of real liquidity touched it.
Matching latency dropped from a multi-second prototype to sub-millisecond in production, and the exchange has run since launch with zero custody incidents.
Unfinished and posted anyway. Drag, swipe, or use the arrows — these change often.
The pieces that make up this project, shipped and in production.
"We'd been told sub-millisecond matching was a nice-to-have we could add later. It's not — it's the whole reason a serious desk will route flow to you at all."
— Head of Trading, digital asset exchange (client name withheld under NDA)