NeoAlgo is trade execution and risk-management software built for algo traders — with strategy development and backtesting tooling in the same system. One pipeline, from idea to order.
Execution, strategy development, and backtesting aren't bolted together after the fact — they share one codepath from day one.
Route orders through a single execution layer with position sizing, stop-loss management, and exposure limits enforced before anything reaches the market.
Build and iterate on trading logic in a structured environment — parameterized, testable, and portable across accounts.
Validate logic against historical data before it touches live capital, using the same rules that govern production trading.
Live, Paper, and Backtest aren't three separate implementations that can drift apart — they run through the same exchange class, with a mode tag distinguishing the record. What passes in backtest is the same code path that runs live.
Orders route through the broker's REST API with market-hours enforcement and tick-size rounding applied before anything is sent.
Identical strategy and risk logic runs against live prices without placing a real order — for validating behavior before capital is at risk.
The same execution and risk code that governs live trading runs against historical data, so a backtest result reflects how the strategy would actually have been executed — not a simplified simulation.
Configure strategy parameters and risk rules.
Run logic against historical data before it's live.
Route orders through the managed execution layer.
Track positions, risk, and performance in real time.
NeoAlgo is built for traders who need their execution layer to behave the same way every time — in backtest, and in the market.
Execution respects actual exchange sessions and product-type rules — no simulated shortcuts in the paths that touch live capital.
Each order event is recorded as it happens, with status changes tracked rather than overwritten, so the record stays auditable.
Position and exposure rules are enforced at the execution layer itself, not left to strategy code to remember.