Sign in to the broker
Platform + Server + Login
EA2YOU / WORKSPACE
MT4 / MT5 connection guide
Choose the runtime mode, then follow each checkpoint.
MT4 uses EX4 and MT5 uses EX5; files are not interchangeable. Production must verify every readiness checkpoint before orders are enabled.
VISUAL WALKTHROUGH
See the flow before you begin
Illustrations show location and sequence. Menus can vary by version and region.
MQL4 / MQL5EA2YOU Bridge · EX4 / EX5Refresh ↻
Install the matching Bridge
MT4 ≠ MT5
- Terminal online
- EA attached
- Algo Trading
- WebRequest
Wait for every checkpoint
Keep each status separate
Run on your own device
1. Download the matching EX4/EX5.
2. Sign in to the broker server on your own device.
3. Place the file under Experts and refresh.
4. Open the selected symbol/timeframe chart.
5. Attach the EA and enable Auto/Algo Trading.
6. Add the EA2YOU HTTPS domain to Allow WebRequest.
7. Create a one-time pairing code in the profile and enter it in the Bridge.
8. Wait for heartbeat and Strategy Version acknowledgement.
2. Sign in to the broker server on your own device.
3. Place the file under Experts and refresh.
4. Open the selected symbol/timeframe chart.
5. Attach the EA and enable Auto/Algo Trading.
6. Add the EA2YOU HTTPS domain to Allow WebRequest.
7. Create a one-time pairing code in the profile and enter it in the Bridge.
8. Wait for heartbeat and Strategy Version acknowledgement.
EA2YOU managed runtime
1. Choose MT4/MT5, broker server and login.
2. Submit a Trade or Investor credential only through the encrypted form.
3. At service start, the system provisions an isolated Windows identity, terminal overlay, process and Bridge.
4. Verify account identity and permissions read-only first.
5. Choose bot/version/symbol/timeframe/risk.
6. Rehearse on Demo.
7. Review price and capacity.
8. Confirm start and wait for real Terminal/Bridge acknowledgement.
2. Submit a Trade or Investor credential only through the encrypted form.
3. At service start, the system provisions an isolated Windows identity, terminal overlay, process and Bridge.
4. Verify account identity and permissions read-only first.
5. Choose bot/version/symbol/timeframe/risk.
6. Rehearse on Demo.
7. Review price and capacity.
8. Confirm start and wait for real Terminal/Bridge acknowledgement.
Pi MT5: confirmed scope versus required checks
1. Choose Pi Securities and MT5 on the connection page.
2. Use the broker server and login shown by the real account; never guess the server name.
3. Confirm the exact instrument in that account's Market Watch.
4. Verify the Thai share board lot; it is usually 100 shares, but exceptions can exist.
5. DR trades on the Thai market from one unit, but Pi must still confirm that the MT5 account and exact symbol are supported; DW requires separate instrument confirmation.
6. For DW, verify expiry, conversion terms, strike and instrument liquidity.
7. Read Contract Specification from the terminal and compare digits, volume step and sessions.
8. Rehearse first; activation requires every readiness state to agree.
2. Use the broker server and login shown by the real account; never guess the server name.
3. Confirm the exact instrument in that account's Market Watch.
4. Verify the Thai share board lot; it is usually 100 shares, but exceptions can exist.
5. DR trades on the Thai market from one unit, but Pi must still confirm that the MT5 account and exact symbol are supported; DW requires separate instrument confirmation.
6. For DW, verify expiry, conversion terms, strike and instrument liquidity.
7. Read Contract Specification from the terminal and compare digits, volume step and sessions.
8. Rehearse first; activation requires every readiness state to agree.
The public information reviewed confirms Pi MT5 for Thai stocks, but not every DR/DW. Selecting Pi is a test-mode route and checklist until Pi confirms the account and instruments.
Readiness checklist
Broker connected
Terminal online + EA attached
Algo Trading + WebRequest allowed
Strategy version acknowledged
WebRequest is synchronous and unavailable in Strategy Tester. Backtests therefore use a fixed strategy definition and remain separate from the live Bridge flow.