Low-latency trading terminal
C++20 and Qt desktop client with a 480 µs order path
C++20 and Qt desktop client with a 480 µs order path
Kestrel Capital · United StatesResults
480 µs
Click-to-order latency
11
Venues integrated
0
Dropped messages in 9 months
3
Operating systems supported
Kestrel's traders used a web terminal with a 40 millisecond click-to-order path, and their market data handler dropped messages during opening auctions. Both were unacceptable for their strategy.
A native Qt client with a lock-free message bus, custom widget rendering for the depth-of-book grid, and FIX/ITCH handlers written against each venue's specification. We profiled on the trading desk hardware and set a per-subsystem latency budget that fails CI when exceeded.
Click-to-order latency dropped from 40 ms to 480 µs. Zero dropped messages across nine months of production, including three opening auctions with record volume.
“Forty milliseconds to four hundred and eighty microseconds. They profiled on our desk hardware, not on a laptop, and that is why the numbers held in production.”
David Ruiz
Head of Trading Technology, Kestrel Capital

A double-entry ledger core written in C++20 with Go service edges, settling 38,000 transactions per second with reproducible end-of-day balances.

A policy administration platform handling 2.1 million active policies, migrated from a mainframe without a feature freeze.
Next case study
Freight TMS for 2,300 vehicles
Send a brief and a solution architect replies within one business day — with questions, not with a template.