The evidence-led FIX protocol engine
LibHFT
The shortest, most defensible path from FIX message to market.
LibHFT is a low-latency FIX engine family for C++, Java, .NET and Rust, built by Atrekes, with dated, reproducible benchmark evidence. Its documentation, benchmarks and guides have their own home: libhft.com.
Public simulator access: username atrekes_demo · password demo_password.
Film produced 19 October 2026. The Rust scene is Rust Pure's own session-engine source; the figures, shown and spoken, are the HP reference campaign: response time at 50,000 requests per second, TCPDirect 4.702 µs at p50. Reference results: HP, 19–20 September 2026 Rust Pure and the other flavors
Language surfaces
C++, Java Pure, Java/JNI, .NET Pure, .NET Native, and Rust Pure.
Tail evidence
Measured transport results and percentile markers stay tied to the stated benchmark setup.
Visible operations
The read-only Workbench makes fleet health, session state and conformance evidence inspectable locally.
What LibHFT is
Six flavors. One FIX engine family.
Pick a native engine, an independent managed engine or a managed API over the C++ core. Every flavor shares the same tracked session behaviors and typed FIX messages; libhft.com documents where each one’s behavior and transport ownership actually live.
Go deeper on libhft.com
Documentation and evidence for every flavor.
libhft.com carries the technical detail: low-latency FIX engine architecture, the benchmark methodology and FIX engine benchmarks, a practical guide to what a FIX engine is, FIX session recovery, the QuickFIX migration guide and the complete LibHFT documentation.
For an evaluation or an architecture session, talk to the engineers who build it.
Plan a LibHFT architecture session