Docs / Test and optimise

Strategy versioning

How commits, version numbers and restores give your strategies Git-like history, and when to cut a new version.

Strategy versioning provides Git-like version control for your trading strategies. Use it whenever you're about to change a working strategy and want a way back, or when you're pushing an update to community subscribers.

How it works#

  • Commit — Saves an immutable snapshot of your current strategy configuration (indicators, signals, risk management, etc.)
  • Version Number — Auto-increments: v1, v2, v3...
  • Change Log — Add notes describing what changed
  • Restore — Roll back to any previous version

Snapshot contents#

Each version snapshot includes: indicators, signal rules, bias generators, risk management, ticker, timeframe, data feed, leverage. The snapshot is backtested automatically upon commit.

NOTE

When you share a strategy to the community, subscribers see the version you shared. Commit a new version + re-share to push updates to subscribers.

Related
The strategy builder How to create a strategy and where every part of it lives — the tabs across the top of the strategy page. Backtesting Replay a strategy over history and read the result honestly — which numbers matter, which mislead, and how to avoid fooling yourself. Community and sharing Publish a strategy so others can follow its signals — and earn when they subscribe — without giving away how it works.
Was this page helpful?
Previous Charts Next What a Squad is
Community Docs About Discord Gateway Sign Up Login
© 2026 riskmanaged.io — All rights reserved.
Trading carries substantial risk of loss. Nothing here is financial advice, and past or simulated performance does not predict future results.