Skip to content
Chronix Chronix Docs

Strategy Integration Paths

Chronix supports several paths for adding new strategies, depending on how close the strategy should sit to the trading runtime and how much latency budget the desk has:

  • native Chronix Rust modules for the tightest integration path. This is the fastest option when the strategy belongs directly inside the live trading backend, because there is no FFI boundary, no extra serialization layer and no bridge overhead between strategy logic and the execution path;
  • FFI modules callable from Rust when the desk wants to keep an existing implementation but connect it to Chronix with a high-speed boundary. Typical options include C, C++, Python native bindings, Go, Java/JVM through JNI and .NET/C# through native interop;
  • external strategy engines through Chronix APIs when the desk wants to run its own strategy engine separately. In this mode the engine can consume Chronix market data, send order intent to the trading adapter, receive order, fill, position and account state, and control exposure/risk through Chronix account and risk interfaces.