Backtesting · 4 exchanges · Free, signups open

See What a Rule Would Have Done, Before You Run It

Replay a grid, DCA, dip-buy or signal bot on up to 90 days of historical candles from WOO X, Binance, Bitfinex or Bitkub. You see how the rule would have behaved on those past prices. Then run the same settings on paper against live prices. It is free, and no real order is ever placed.

No invite needed right now. We are scaling up gradually, so this may change.
WOO Xlive prices Binancelive prices Bitfinexlive prices Bitkublive prices

Test a rule on the past before you run it on paper

Historical candles and the same bot logic that runs on paper, so there is no separate simulation engine to trust.

Historical candles

// DATA FEED

Backtests run on historical market data from the exchange you choose, not a synthetic price series.

CANDLE DATA READY

Every bot type supported

// COVERAGE

Backtest grid, DCA, dip-buy and signal bots, and the Strategy Router, with the same settings you would use to run them on paper.

5 BOT TYPES READY

Return, win rate, drawdown

// METRICS

See total return, win rate and max drawdown for the period you tested. They describe what happened on past prices, not what will happen next.

3 METRICS ARMED

Works on 4 exchanges

// VENUES

Backtest on WOO X, Binance, Bitfinex or Bitkub, using each exchange's own historical data.

4 EXCHANGES READY

How backtesting works

From first click to your first backtest result, in three steps.

1

Configure your bot

Set up a grid, DCA, dip-buy or signal bot exactly as you would to run it on paper: pair, range or schedule, sizing and risk rules.

2

Pick a historical period

Choose a date range within the last 90 days, and run the backtest on that exchange's historical candles.

3

Review, then run it on paper

Check the return, win rate and drawdown on that past window. Then run the same settings on paper against live prices.

The parts of a backtest that decide whether its number means anything

Any engine can replay candles and print a percentage. What separates a useful backtest from a flattering one is what it charges you, what it refuses to assume, and whether the data behind it was complete.

It charges each exchange's published maker and taker rates

Fees are applied per fill at the rate the exchange publishes, looked up from the pair's own quote currency where that matters. Bitkub is where it does: 0.25% on THB-quoted pairs and 0.10% on USDT-quoted ones, on the same exchange.

The result reports total fees paid on its own line, beside the return. A strategy that trades often can spend its entire edge on costs, and a backtest that hides the cost of trading inside a single net figure is the easiest way there is to be misled by your own tool.

Gaps in exchange history are detected, not papered over

History is downloaded a window at a time. On some exchanges a window that comes back with fewer candles than asked for means you have reached the start of that market. On others it means only that the window itself had holes in it. Reading the first meaning everywhere once turned a request for a year of Bitkub data into 104 days, and the short result was saved as though it were the full year, so the difference never showed again.

Each exchange is now marked as one kind or the other. The download continues from the start of the window it has just read, puts up with a limited run of empty windows, and refuses to save a download that ended on them. A backtest over a period the exchange cannot fully supply is worth knowing about rather than smoothing over.

Every bot type, with the same code the paper bot runs

Grid, DCA, dip-buy, signal and the Strategy Router all backtest, and each replays through the same decision logic as the paper bot you can start from the dashboard, rather than a simplified model of it.

That is why the router's direction gate, for example, exists in both in the same form: a backtest whose rules differ from the bot's is measuring a bot you cannot actually run. It also means the limits carry over honestly. A signal bot's volatility sizing is worked out from how widely prices are spread rather than from a candle-based ATR, in the backtest exactly as in the running bot.

What the result reports, and how sure it can be

A run returns starting and final equity, total return in currency and percent, maximum drawdown, the full trade list, the equity curve, and the fees paid. Beside them sits a Chance of Loss figure: the run's own closed trades are resampled many times, and it reports how often the total came out below zero.

That figure measures luck within the trades you got, nothing more. It cannot see a setup tuned too closely to one stretch of history, and the result card says so. A result from a past period describes that period. Nothing here presents one as a forecast.

What a single run may replay

Every account has the same limits, free. What is bounded is how much history one run may ask for.

Limit What it bounds Value
Lookback How much history one run may replay, on any bot type and any listed pair. 90 days
Runs per day How many backtests an account may start. unlimited
Runs at once How many backtests compute at the same moment, counted across the whole site. shared pool
Exchanges Whose published candles and fee rates a run uses: WOO X, Binance, Bitfinex or Bitkub. 4

The length of history is what bounds the cost of a run, which is why there is no daily limit on run count: capping runs would punish repeated tweaking, which is the one thing a backtester exists to encourage. How many runs happen at once is limited across the whole site, so one heavy run never starves another account.

Backtest on each exchange's own candles and fees

Backtesting works on WOO X, Binance, Bitfinex and Bitkub. A pair is replayed on the candles that exchange published and charged that exchange's rate, rather than being approximated from a similar pair somewhere else. No account on the exchange is needed.

That approximation is tempting, and wrong for exactly the strategies people want to test. Whether a grid's rung spacing clears its costs depends on the cost of buying and selling once, and on Bitkub that cost differs between the THB and USDT sides of the same exchange.

EXCHANGE CANDLES PUBLISHED FEE RATES GAP DETECTION 90-DAY LOOKBACK

Crypto backtesting — FAQ

01 // CORE CONCEPT What is backtesting?

Backtesting replays a bot's settings on historical price data. It shows what the rule would have done over a past period, before you run it forward on paper.

02 // FUTURE RESULTS Does a good backtest guarantee future results?

No. A backtest describes the past, and it is not a forecast. Market conditions change, and a rule that did well in one period can do very differently in another.

03 // BOT COVERAGE Which bot types can I backtest?

Grid, DCA, dip-buy and signal bots, and the Strategy Router. Each uses the same settings you would use to run it on paper.

04 // DATA COVERAGE Which exchanges have historical data for backtesting?

WOO X, Binance, Bitfinex and Bitkub. A backtest can cover up to 90 days of history.

05 // COST Is backtesting free?

Yes. Vectixs is free and there is nothing to buy. Every account can run backtests on up to 90 days of history. No exchange account or API key is needed.

06 // DATA Where does the historical data come from?

The exchange the backtest is set to, through that exchange's public candle data, saved so one download serves every visitor. There is no third-party data vendor in the path, so what you backtest on is what that exchange published.

07 // FEES Are trading fees included in the result?

Yes, at each exchange's published maker and taker rates, and reported as their own line beside the return rather than folded into it. A high-frequency strategy can spend its whole edge on costs, and a single net number hides that.

08 // HISTORY How far back can I test?

Up to 90 days per run, on every account. The number of runs is unlimited, because running a setup again with one setting changed is the whole point.

09 // ACCURACY Will a paper bot match its backtest?

Not exactly. A backtest steps through candles, so it cannot see the order of moves inside a candle the way a bot reading live prices does. Neither one reproduces a real order book's queue or partial fills. Both run the same decision logic, which is the part that can be made to match.

10 // PROJECTION Can a backtest tell me what will happen next?

No. It shows what the configuration would have done over the period you selected, including its drawdown and its fees. It will not project that forward into an expected balance, and no part of this product will. A past period is a property of that period, not a forecast.