Backtesting & results
Portfolios
Backtest several strategies and pairs together as one account — fixed weight or a shared pool, the account settings every leg shares, each leg's own settings, and the book's risk policy.
Updated 2026-09-19·Rev. 2026.09
A portfolio runs several strategies together as one account. Each leg is one strategy on one pair and timeframe, and the same strategy can sit on several legs with different pairs. The backtest returns one result for the whole book (one equity curve, one drawdown, combined metrics), and each leg keeps its own numbers.
Open it from Portfolio in the workspace switcher at the top of the app.
A premium feature
Portfolios are included on paid plans. On a plan without them, creating one opens an upgrade prompt. A portfolio backtest counts as one deep backtest per leg against your daily allowance.
Capital model
The Capital model decides how the book's capital reaches its legs.
| Model | How it works |
|---|---|
| Fixed weight | "Each strategy runs on its own slice of the pool. Weights must total 100%." Every leg is its own account with its own slice. |
| Shared pool | "All strategies draw from the same capital pool; their orders compete for buying power." There's one account, and every leg trades from it. |
Fixed weight can Rebalance (Never, Weekly, Monthly, Quarterly, Annual). On each date, capital moves from the winning legs to the laggards, so later trades are sized from the target weights. You can also limit it to legs that have drifted far enough from their target (Every date, or Off by 2 / 5 / 10 pts). Money tied up in an open trade moves once that trade closes.
Shared pool has no weights. Every leg sees the whole pool, and a fill by one leg uses buying power the others then can't. Two consequences follow:
- An entry can be refused because another leg holds the capital.
- It's one margin account. Every leg's open loss counts against it, so a leg can be liquidated because another leg's loss sank the pool. See margin, liquidation, and funding.
The account
The editor's Account section holds what belongs to the wallet, not to any one strategy. Everything here applies to every leg:
- Currency: what the book's cash and results are counted in.
- Position mode: One-way (one net position per symbol) or Hedge (a long and a short on the same symbol at once). On Binance this is an account-wide setting.
- Book rails: the portfolio's risk policy. With a shared pool it's judged on the pool every leg trades from. With fixed weight it's judged on the combined sleeves (every leg's equity added up).
Each leg's settings
Each leg row has a settings chip showing its leverage, sizing, and fee. It opens Leg settings, the same dialog as a strategy's backtest settings, covering fees, slippage, margin, sizing, and the leg's own rails. Currency, position mode, and capital come from the portfolio.
A leg copies its strategy's settings when you add it. From then on it owns them: editing a leg changes that leg only, and editing the strategy later doesn't silently change the portfolio. The chip tells you when the two have drifted apart:
| Badge | Meaning |
|---|---|
| Edited | You changed this leg's settings in the portfolio. The strategy is untouched. |
| Strategy updated | The strategy's settings changed after this leg copied them. |
To catch up, open the leg and choose Sync (or Copy from strategy). The leg takes the strategy's current settings, and the leg's own edits are replaced.
A strategy's own risk policy doesn't come along
A leg never copies its strategy's risk policy. Rails belong to the account, so a portfolio uses its Book rails plus any Leg rails you set on each leg.
Leg rails
In Leg settings, Leg rails add limits to that leg alone, on top of the book's:
- Soft drawdown and Hard drawdown, measured from the leg's peak.
- Max margin share: the leg's initial margin ÷ the book's equity.
A leg follows whichever is stricter, the book's state or its own. When the book halts, every leg is flattened. When a leg halts, only that leg closes and stops, and the other legs keep trading.
Reading the report
Run the book with Run backtest. The results column opens alongside the editor, and next to the combined equity curve and metrics, two panels matter most for the account model:
-
Risk shows what the book's and legs' rails did: the state the book ended in, time in each state, exposure, the peak margin ratio, downsized and refused entries, every state change, and a row per leg. Without a policy it says so.
-
Settings is the receipt: what each leg actually ran with. It stays true however the portfolio or its strategies are edited afterwards. Its columns are Leverage, Size, Fee, Slippage, and Pyramiding, plus:
- Liquidation: the price that would have liquidated the leg at the end of the run, with the rest of its account frozen. In a shared pool this price moves with the other legs. The column also shows how many of the leg's closes were liquidations.
- Funding: what the leg paid (−) or received (+), open positions included. It reads not charged when the pair's funding history was unavailable.
A line above the table names the account's currency and position mode, and what liquidation was judged on (for example, the mark price and Binance's leverage brackets, with the date they were fetched).
Deploying a portfolio
A tested portfolio deploys in one action, as one paper bot per leg. Each bot runs with the settings its leg ran with in the backtest. It carries the book's rails and its own leg rails, enforced the way the backtest enforced them. If the book reaches its hard drawdown, every bot in the portfolio stops. See monitor the Fleet.