LEARN · EN · easyquanttrading.com
MT5 export without custody
When a strategy passes gates, export pure MQL templates or a signal bridge. EasyQuant does not hold funds or run your account for you. This guide explains the two delivery types, the parity checks, and the safe path to live.
- pure_mql vs signal_bridge capability badges
- Parity checks where supported
- Deliver SKU unlocks live quotas — still user-side execution
- Source code you can read and audit
The two delivery types: pure MQL vs signal bridge
A pure MQL package exports the strategy as MQL5 source code you run directly in your own MetaTrader 5 terminal. It is the default and preferred path: the code is human-readable, you control the account, and nothing is hosted by us.
A signal bridge forwards validated signals to your broker account through a bridge process. It is optional, never the default, and it still keeps execution on your side — the bridge does not custody funds or keys.
Why 'you keep the keys' matters
The worst failure mode in retail algo trading is handing your account credentials to a black box. When a platform holds your keys, it holds your capital's security, and its incentives (your trading volume, your deposits) are not the same as yours.
The EasyQuant model is the opposite: strategies are generated and validated on the platform, but execution happens on accounts you control, at brokers you choose. You can inspect the exported code, compare it to the backtest, and walk away at any time without losing access to your own account.
Parity: how to confirm the EA matches the backtest
- Compare the cost model: spread, commission and slippage settings in the EA must match the backtest assumptions.
- Check signal timing: the EA should enter and exit on the same bars the backtest used — one-bar offsets silently change results.
- Run the EA on a demo account for 1-3 months and compare win rate, profit factor and drawdown to the backtest.
- Large drift means something in the translation or the cost model is wrong. Fix it before live, not after.
The safe path from export to live
- Validate: strategy passes walk-forward, Monte Carlo and DSR/PBO gates in the pipeline.
- Export: choose pure MQL or signal bridge and download the package.
- Audit: open the MQL source and confirm the rules match the strategy card.
- Paper trade: run the package on a demo account and track the metrics against the backtest.
- Go small: attach small real money, monitor consistency for 1-3 months, then scale.
FAQ
- Do you host signals by default?
- No. Factory delivery prefers local packages. Signal bridge is optional.
- Is the exported MQL5 code readable?
- Yes — pure MQL packages export as source you can open and audit. If a tool only gives you a compiled .ex5, treat it as a black box.
- Does EasyQuant hold my account keys?
- Never. Execution happens on accounts you control. We generate and validate strategies; you run them.
- What is the difference between pure MQL and a signal bridge?
- Pure MQL is source code you run yourself in MT5. A signal bridge forwards validated signals to your broker. Both keep execution and keys on your side.
- How do I know the EA will behave like the backtest?
- Check the parity items — cost model, signal timing, demo performance vs backtest. Paper trade 1-3 months before scaling live.
More guides
Not investment advice. Historical results do not guarantee future performance. EasyQuant is a research factory — you execute on accounts you control.