Platform — Institutional Tools

Institutional Tools

Professional-grade execution infrastructure, API connectivity, and analytics tooling designed for the operational demands of institutional trading desks globally.

Order Matching & Execution Infrastructure

The FundInsight order matching system implements a Central Limit Order Book (CLOB) architecture with strict price-time priority. Each instrument maintains a dedicated order book process, isolated via memory-mapped ring buffers to prevent cross-instrument interference under high-load conditions. The matching engine processes FIX 4.4 New Order Single (D) and Order Cancel Replace (G) messages through a pipeline that enforces pre-trade risk checks before order admission to the book. This pre-admission validation layer evaluates gross notional exposure, per-instrument position limits, and margin utilisation thresholds in under 8 microseconds, ensuring that no non-compliant order ever reaches the matching core. Execution reports are generated as FIX Execution Report (8) messages and delivered to clients via dedicated TCP sessions with configurable resend intervals.

Multi-Layer Risk Management Framework

FundInsight's institutional toolset incorporates a three-layer risk management architecture. The first layer—pre-trade controls—operates in the order admission pipeline and enforces configurable limits on maximum order size, gross notional exposure, and margin utilisation before orders reach the matching engine. The second layer—intraday monitoring—runs asynchronously and continuously recomputes real-time Value-at-Risk (VaR) using an EWMA covariance model (λ=0.94), flagging breach events via webhook and email alerts. The third layer—post-trade attribution—reconciles execution records against pre-trade P&L estimates, generating slippage attribution reports that quantify the market impact coefficient κ for each instrument and session. This layered architecture ensures comprehensive risk visibility across the pre-trade, intraday, and post-trade lifecycle.

Liquidity Aggregation & Smart Order Routing

The FundInsight Smart Order Routing (SOR) engine aggregates real-time top-of-book and Level 2 data from all 28 connected liquidity providers, constructing a composite synthetic order book that represents the best available liquidity across the entire LP network. For each incoming institutional order, the SOR evaluates the optimal routing strategy by solving a convex optimisation problem that minimises the expected execution cost—defined as the sum of spread cost and market impact—subject to constraints on partial fill acceptability and per-LP exposure limits. The routing decision is computed within 50 microseconds and the resulting child orders are dispatched to selected LPs simultaneously via dedicated FIX sessions. Post-routing execution analytics measure effective spread, fill rates, and slippage for each parent order, providing the empirical data that drives continuous SOR model recalibration.

Co-location & Network Infrastructure

FundInsight maintains dedicated co-location server presence at Equinix SG1 (Singapore), LD4 (Slough, UK), NY4 (Secaucus, NJ), and TY3 (Tokyo, Japan). Each facility operates as an independent execution node with full order book and risk engine replication, providing geographic redundancy and local connectivity to regional LP relationships. Cross-facility synchronisation is maintained via a dedicated MPLS private network with sub-10ms replication latency. The network topology is designed for a recovery time objective (RTO) of 30 seconds and a recovery point objective (RPO) of zero, ensuring that no order or risk data is lost in the event of a facility-level failure. All infrastructure is monitored continuously via SIEM and custom trading-specific alerting built on the OpenTelemetry observability stack.

Global Latency Map
SG1 — Singapore0.3ms
LD4 — London0.4ms
NY4 — New York0.8ms
TY3 — Tokyo1.2ms
API Throughput (msg/s)
99.9%
Uptime SLA
28
LP Connections
<8μs
Pre-trade latency
4
Hubs

Institutional clients access FIX API credentials and the full toolset via the Secure Gateway.

Access Secure Gateway →