Pilot Keys is designed around trader-controlled execution and risk management. The EA helps prepare, size and manage trades; it is not presented as a guaranteed-profit automated trading system.
FAQ
Questions before you plug Pilot Keys in.
Clear answers about the EA, the Web platform, MT5 synchronization and subscriptions.
The EA is built for MetaTrader 5. Broker-specific symbol naming, contract specifications, permissions or server behavior can vary, so compatibility should always be tested on demo before live use.
In the first sync architecture, yes. The Pilot Keys EA is the bridge, so the MT5 terminal running the EA must be connected. If it was offline, the EA can catch up account history after reconnection.
The planned EA-based sync does not require the Web platform to store the trader's MT5 master password. The EA runs inside the already authenticated MT5 terminal and uses a Pilot Keys Sync Code.
Yes. The standalone EA subscription is intended for traders who only want the MT5 execution and risk-management tool.
That is the planned Web subscription structure. Eligible Web subscribers receive the Pilot Keys EA and the Sync Code entitlement so MT5 can connect to the Web journal.
EA trading controls and synchronization are intended to stop when the subscription is inactive. Historical journal and performance data should remain preserved rather than being deleted.
The current Pilot Keys Web backtester is built around downloaded historical tick data, market replay and Bid/Ask spread behavior rather than a simple static candle-by-candle result table.
No. Pilot Keys is software for execution, backtesting, journaling and performance analysis. Trading involves risk, and past or simulated results do not guarantee future performance.