Appearance
Personalize your experience
Backtest anything. Trust the numbers.
Six languages. One set of fills, costs and statistics.
Six languages, one set of rules
The language picks the engine. Fills, costs and statistics are shared.
Move a slider. Everything re-runs.
The Backtesting page's own charts, on a backtest computed in your browser.
Fills you can defend
Decide on close, fill next open
One deterministic path inside a bar
Slippage: bps, ticks or √ impact
Cost of one round trip
6.7 bps round tripOrders
marketlimitstopstop-limittrailingbracket sl / tpOCOreduce-onlyday / expiredrawdown kill switchPer-run settings
fill: next_open | closedelayBarslotSizemaxParticipationsession: crypto | india | usProve the edge before you trade it
Same strategy, data and costs. Six tests.
Order books, replayed event by event
Latency on both legs. Fills only when your order reaches the front of the queue.
Defaults
feed 500 µsorder 1,000 µsqueue: probabilisticmaker −0.0025%taker 0.0075%tick 0.5max position 10≤ 2M eventsReports
Every run, the same scorecard
Return
Risk-adjusted
Drawdown
Trades
Distribution
Breakdowns
Idea to live in one workspace
12 result views
Research locally. Same numbers on Quatick.
The SDKs implement the server's fill rules and statistics.
Quick answers
The one built for its language: builder strategies on the C++ DSL engine, QuaScript on its own engine, SQL in DuckDB, and Python, C++ and TypeScript in their runtimes. One statistics module scores them all.
Test the strategy you already have
Pick a strategy, a market and a date range. Research views are one tab away.