Use-case fit

Rotation work usually falls apart in the same places: unrealistic turnover, a weak benchmark choice, a flattering in-sample window, and no serious forward follow-up. Alphrex is built to keep those failure modes attached to the research workflow rather than leaving them for a separate spreadsheet pass.

Why Alphrex fits rotation research

Benchmark choice is not an afterthought

Rotation strategies need a fair baseline. Alphrex lets you compare against same-ticker buy-and-hold, a single benchmark proxy, or a weighted basket such as SPY:0.60, IEF:0.40 instead of forcing one blunt reference series.

Turnover cost stays visible

Rotation rules often look strongest before commission and slippage appear. Alphrex keeps frictions in the core backtest contract so high-turnover mythology is harder to mistake for a durable edge.

Validation is attached to the result

Holdout and walk-forward summaries sit close to the headline metrics. That matters for rotation because small ranking changes can produce backtests that look stable right until the sample boundary moves.

A realistic ETF rotation workflow

1. Start in Strategy Library or Strategy Studio
Begin with a simple momentum, mean reversion, or factor thesis before inventing a large allocation story. The goal is to keep the ranking logic interpretable.
2. Use Backtest to pressure-test assumptions
Check the rule against realistic costs, a defensible benchmark, and validation splits. Rotation logic that only wins in one uninterrupted sample window is usually not worth promoting.
3. Use Compare to reject flattering variants
Place competing rotation ideas side by side and look for differences that remain once active return, drawdown, benchmark fit, and validation quality are in the same surface.
4. Track the survivors in Paper
The few variants that still look credible should continue as paper sleeves or portfolios. That is where you learn whether the rotation logic keeps its edge outside the historical sample.

What this still does not solve

Execution realism

Alphrex models costs, but it is not a live execution stack. Rotation implementations with intraday constraints, tax lot logic, or broker-specific routing still need separate execution planning.

Benchmark design judgment

Weighted baskets help, but the platform does not magically choose the correct economic benchmark for you. Rotation work still depends on framing the right opportunity set.

Regime certainty

Even with holdout and walk-forward checks, a good result is still a model output, not proof of regime invariance. Forward paper evidence remains necessary.