Skip to content

Trading engine and market data

A simulated account is only fair if its fills look like the real market. A fill better than any exchange would give is an edge the firm pays for at payout time; one that's worse drives good traders away.

What tends to go wrong

  • In 2024 many prop firms lost MetaTrader access when MetaQuotes withdrew licences, and some had to move platforms within days. A firm that owns its execution and rule logic depends less on any one vendor.
  • Market prices arrive fast and approximate; account state has to be exact. Handling both on one path makes both worse.
  • A terminal needs live order books, trades, candles and account updates, pushed to every open tab without overloading the API.

What I've built

Market-data ingest

One ingest process holds a fenced leadership grant and streams order books and trades from Hyperliquid. The latest frame per instrument goes to Redis through a compare-and-set on epoch and sequence, and everything is archived for replay.

See it in the case study: Market-data ingest

Fills against real depth

Orders walk the observed order book within slippage bounds. An order that would fill too far from the price, or beyond the depth the feed shows, is cancelled with a specific reason.

See it in the case study: Fills against real depth

Perpetual futures

Market and limit orders, take-profit and stop-loss, reduce-only closes, position reversal, leverage changes, funding and liquidation, netted into one position per instrument.

See it in the case study: Perpetual futures

Trading terminal

Live order book, trades, candles and an account stream over Socket.IO, with P&L and margin updating as prices move.

See it in the case study: Trading terminal

What I can take on

  • A simulated execution engine on exchange market data. My experience is with crypto perpetual futures; other markets need their own data feed.
  • Market-data ingest with a replayable archive, so breaches and disputes can be judged after the fact.
  • WebSocket gateways and a trader terminal.
  • Race and load tests for the order path.

What I haven't done yet

I haven't shipped an integration with MetaTrader 5 (Manager API), cTrader, DXtrade or Match-Trader. NEXETRO runs its own execution and rule engine on exchange market data from Hyperliquid, so its risk logic doesn't depend on a platform licence. If your firm runs on one of those platforms, I'd scope the integration against its API documentation and say so in the estimate. NEXETRO's order admission is also still below the throughput I set for launch; the case study gives the numbers.

Related work

  • Challenge and risk engine

    Profit targets, daily-loss and drawdown floors, consistency rules, phase progression and breach detection.

  • Ledger, payouts and reconciliation

    A double-entry ledger for fees, refunds and payouts, with idempotent money changes and scheduled reconciliation.

  • Back office, risk desk and dashboards

    Admin panels and a risk desk for staff, trader-facing dashboards, role-based access and audit logs.

All prop firm development work

Building or fixing part of a prop firm?

Tell me which platform or market data you use, roughly how many accounts you run, and what needs to change. I'll reply with questions or a first outline of the work.

Get in touch