Strategy Router · Paper regime switching · Free, signups open

One Paper Bot Graph That Switches Strategy When the Market Regime Changes

Map Grid, DCA, Dip-Buy and Signal bots to trending, ranging and volatile market conditions. Vectixs reads the regime from live prices, using trend strength and Bollinger Band width confirmed over several candles. It then starts the matching paper bot, even with no browser tab open. No real order is ever placed, and you need no exchange account.

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

A router built on measured regime detection, not guesswork

Every switch is driven by trend strength and volatility readings, not a fixed calendar or a coin flip.

Automatic trend/range/volatile detection

// DETECTION

Trend strength and Bollinger Band width percentiles classify the market as trending, ranging or volatile. A regime must hold for several candles, so one noisy tick can't flip your bot back and forth.

HYSTERESIS CONFIRMED LIVE

Map any bot type to any regime

// GRAPH BUILDER

Build a graph from a Start node through a Market Regime node into Grid, DCA, Dip-Buy or Signal legs. Each leg has its own take-profit, stop-loss, timeout and notify conditions.

4 LEG TYPES LIVE

Keeps watching with no tab open

// SERVER-SIDE

An enabled router is checked on a schedule on our servers, not only while your browser is open, so a regime change is still caught while you're away.

BACKGROUND EVAL LIVE

Every leg trades on paper

// PAPER

Each leg the router starts is a paper bot on your simulated balance. One router can be enabled at once on every account, free.

3 ENABLED ROUTERS PAPER

How the Strategy Router works

From first node to your first automatic regime switch, in three steps.

1

Build your regime graph

Attach a Grid, DCA, Dip-Buy or Signal leg to each of trending, ranging and volatile. Then set entry conditions (RSI, price level, session window, cooldown) and exit conditions (take profit, stop loss, timeout, notify) for each leg.

2

Backtest it on past prices

Replay your graph on up to 90 days of history to see which legs it would have started on those prices. It is not a forecast.

3

Enable it on paper, live

Enable the router on your paper balance and watch regime confirmations switch which leg is active against live prices. No exchange account or API key is involved.

How a regime is classified, confirmed, and turned into a leg

A router that switches strategy on a noisy reading is worse than no router. Most of this design is about refusing to act on one.

Two measurements, three regimes

Classification reads Wilder's ADX for trend strength and Bollinger-Band width for how far the market has expanded relative to its own recent history. Actively expanding bands read as volatile. Otherwise an ADX at or above the trend threshold reads as trending, and anything else reads as ranging.

There is a fourth state, idle, and it means only "not enough data yet". It is never a description of the market. That distinction was learned the hard way: an earlier version let a perfectly ordinary quiet reading fall through to idle, and because no strategy is mapped to idle, a router that landed there could not start anything at all. One router spent 14 of 32 bars stuck in it overnight.

ADX is direction-blind, so direction is a separate gate

ADX ends on the absolute difference between the positive and negative directional indicators. A rally and a crash of equal force are the same reading. A router mapping trending to a DCA leg would therefore average down through a collapse and call it a trend.

The optional per-leg direction requirement closes that gap. It compares the positive and negative directional indicators and refuses to act when it cannot tell them apart. It is checked after the entry conditions rather than before, because those conditions fire on a change from a stored previous price, and skipping them would leave that price stale and manufacture a false crossing later. The paper router and the backtester apply the gate identically, or the backtest would be measuring a different bot from the one you can run.

Structured entry and exit conditions, not free text

Entry conditions are chosen from a fixed list: price crossing a level, RSI, Stochastic RSI, Williams %R, Supertrend, a session window, or a cooldown. Exit conditions are take-profit, stop-loss, timeout and notify. A group can require all of its conditions, any one of them, or at least a set number of them.

Exit conditions are measured from what the position actually cost, not from the price the market was at when the router switched to that strategy. The two stop agreeing as soon as a trade fills, because a signal leg arms itself and waits rather than buying straight away. The one deliberate exception is a grid leg: its average cost moves every time a rung fills, which would make a fixed stop tighten and loosen on its own.

A daily stop that latches, and refusals you can read

The daily stop is a percentage of the paper money you allocated to the router. It adds up realized gains and losses since the day began, plus whatever the open position is currently up or down. It latches for the rest of the UTC day and clears only when the date changes, never because the loss recovered, since otherwise a router would re-enter on a day it had already blown. When it trips it closes the open leg at once.

When a router decides not to start a leg, it says why. The refusal is saved, sent to you once, and shown on the router's card. Without that, a router waiting for its conditions and a router that cannot start at all look exactly the same from the outside: flat, for hours, with nothing to explain it.

What a router is made of

A router is a regime map plus two condition groups plus a risk budget.

Component What it does Values
regime map Which bot type runs in each detected regime. Nothing maps to idle, by design. ranging | trending | volatile
start_group Typed entry conditions, evaluated together before a leg may open. ALL | ANY | AT_LEAST
exit_group Typed exit conditions, measured from what the leg paid. TP | SL | timeout | notify
require_direction Per leg: refuse a trending regime whose direction is wrong for this bot type. optional
regime_sensitivity The ADX and band-width thresholds, plus how many consecutive readings confirm a switch. tunable
daily_stop_pct Percent of allocation that latches the router closed for the rest of the UTC day. optional
allocation_usdt Paper money set aside for the router. The base the daily stop is measured on, and a backtest's starting cash. It does not size any leg. number

An enabled router is evaluated every 5 minutes, whether or not a leg ever opens. That is why the limit counts ENABLED routers rather than created ones: every account can have 1 enabled at once, across all exchanges. A disabled router does nothing and is not counted.

Regime switching on four exchanges' prices

A router can read the market for a pair on WOO X, Binance, Bitfinex or Bitkub, and its legs trade that pair on paper at the same live prices. Nothing is placed on the exchange and no account there is needed.

One structural limit, stated up front: you can run one bot per pair per type, so a router's leg and a bot of the same type you started by hand on the same pair are competing for one slot. The interface warns you at both ends. The warning is worked out on the server from the same state the refusal itself reads, so it can never disagree with the refusal it is predicting.

3 REGIMES 5-MIN EVALUATION DIRECTION GATE 4 EXCHANGES

Strategy Router — FAQ

01 // ROUTER BASICS What is the Strategy Router?

It's a visual graph builder that maps Grid, DCA, Dip-Buy and Signal bots to trending, ranging and volatile market regimes. Vectixs then starts the matching bot when the market changes, instead of you switching strategies by hand. Every bot it starts trades on paper.

02 // REGIME DETECTION How does it detect trending, ranging, and volatile markets?

Trend strength, plus percentiles of Bollinger Band width for squeeze versus expansion, classify the current regime. A new regime must be confirmed over several candles before the router switches, so a single noisy candle can't whipsaw your bot back and forth.

03 // PAPER ONLY Will it ever place a real trade?

No. Vectixs is paper trading only. Every leg the router starts trades a simulated balance against live public prices. No real order is ever placed, and there is no exchange account or API key to connect.

04 // BACKGROUND EVALUATION Does it keep working if I close the browser tab?

Yes. An enabled router is checked on a schedule on our servers, not only while a browser tab is open, so a regime change is still caught while you're away. Paper bots on an account nobody has signed into for 14 days are stopped automatically, and an email warns you at day 11.

05 // COST Is the Strategy Router free?

Yes. Vectixs is free and there is nothing to buy. Every account can build and backtest routers and keep 1 of them enabled at once on a paper balance of up to $1,000,000.

06 // REGIMES How does the router decide what regime the market is in?

From Wilder's ADX and Bollinger-Band width measured against the pair's own recent history. Expanding bands read as volatile; otherwise an ADX above the trend threshold reads as trending, and everything else reads as ranging. Both thresholds are editable per router.

07 // FLAPPING What stops it switching strategy on every reading?

A candidate regime only becomes the confirmed one after it has been returned several consecutive times, and any dissenting reading resets the streak. The confirmation count is one of the sensitivity settings you can tune.

08 // DIRECTION Does a trending regime mean the market is going up?

No, and this is the single most important thing to understand about any ADX-based router. ADX measures trend strength with no direction in it, so a crash and a rally read the same. The optional per-leg direction requirement is what makes a trending regime mean trending upward, and it fails closed when direction cannot be determined.

09 // DAILY STOP What happens when the daily stop trips?

The router closes its open leg straight away and refuses new entries until the UTC date changes. A recovery later that day does not clear it. The limit is a percentage of the allocation you gave the router, so with no allocation set the daily stop reports itself as not configured rather than guessing at one.

10 // LIMIT Why is the limit on enabled routers rather than created ones?

Because the ongoing work is the evaluator, not the bots. An enabled router reads market data every five minutes whether or not a leg ever opens. A disabled router does nothing at all, so it is not counted. Every account can have 3 enabled at once.