Before going live: demo account, MT4/MT5 export and a checklist

Deployment is a separate skill from research. The goal of the first live phase is not to earn quickly; it is to confirm that the system behaves the way you studied, and to detect the places where reality differs from simulation.

Compile and inspect the export

Raveno can export strategies to MQL4, MQL5, Pine Script, Python for MetaTrader 5, cTrader and NinjaTrader 8. Before running anything, compile the generated code and read the log. Check the instrument, timeframe, magic number or position label, and the exact stop and sizing code.

Platform features differ. A block that depends on a feature the target platform does not support should block the export instead of silently changing meaning. Read the export report and the notes attached to the strategy; they explain any intentional differences.

Use a demo account first

Run the strategy on a demo account with the same broker settings you intend to use. Compare the trades it takes with the backtest trades. Look at spread, slippage and the time at which signals are evaluated. A strategy that reads a closed candle should not act on an unfinished one.

Give the demo phase enough time to include quiet and active sessions. Four to eight weeks is a common starting point; the right length depends on the strategy frequency.

A pre-flight checklist

1. The written specification matches the blocks in the builder.
2. Out-of-sample and walk-forward checks were reviewed.
3. Costs in the test are realistic for this broker and instrument.
4. Risk per trade, daily loss limit and maximum drawdown rules are active.
5. The exported code compiles without errors and the logs are clean.
6. Position identification (magic number or label) is unique and correct.
7. Monitoring exists: email or platform alerts when the system stops or opens trades.
8. A stop procedure exists: how to disable the strategy and close exposure.
9. A journal exists: start date, version, parameters and the reason for each change.
10. The account size and starting risk are small enough to tolerate a normal losing sequence.

During the first live period

Keep the version fixed. Do not adjust parameters because of a losing week; the purpose of this phase is comparison. Record differences between demo, live and backtest. If the system makes an unexpected trade, find out why before continuing.

A note on expectations

Live results can be worse than a simulation for reasons that have nothing to do with the idea: latency, costs, data differences, or a rule interpreted differently. Expect friction and plan for it.

This article is educational and is not financial advice.