Automated execution is optional.
When you want it, make it controlled.
Autopilot connects approved strategy channels, execution controls and account-level safeguards inside Apex Market Pros.
What actually has to happen before Autopilot can place a single trade.
This is the real pipeline — local machine, cloud infrastructure, and the broker or exchange itself — laid out end to end. Every layer below has to be installed, configured and kept alive correctly, in order, or nothing executes. We build and maintain all of it for you.
PHASE 01Local Environment
Python runtime, MT4 & MT5 terminals, EA staging, local credential security.
PHASE 02Cloud / VPS Deployment
Provisioning, hardening, mirrored install, supervision, ingress, monitoring.
PHASE 03Broker / Exchange Connect
KYC, execution path, scoped API keys, reconciliation, hard risk gates.
PHASE 04Signal, Execution & Monitoring
Signal → authenticated dispatch → validation → fill → live oversight.
PHASE 01 · LOCAL ENVIRONMENT5 STEPS
1Python runtimeInstall a pinned Python version, create an isolated virtual environment, and install every broker/exchange SDK and dependency the strategy needs.
2MetaTrader 4 (MT4)Install the 32-bit MT4 terminal and MQL4 compiler, log in to the broker's trade server, and stage the Expert Advisor in the correct Experts folder.
3MetaTrader 5 (MT5)Install the separate 64-bit MT5 terminal and MQL5 compiler — MT4 and MT5 do not share a runtime — and repeat login and EA staging.
4Terminal permissionsEnable AutoTrading, allow DLL imports where the EA requires it, and set the exact symbol, timeframe and chart template each strategy expects.
5Local securityAdd firewall and antivirus exceptions for outbound terminal traffic, and store every API key and login encrypted — never as plain text in a script.
PHASE 02 · CLOUD / VPS DEPLOYMENT6 STEPS
1Provider + regionSelect a VPS provider and data-center region chosen for low latency to the broker's matching engine, not just lowest cost.
2Remote hardeningChange default remote-access ports, enforce 2FA, and allow-list connecting IPs before anything else touches the box.
3Mirror the stackReinstall Python, MT4 and MT5 remotely so the VPS runs an exact, independent copy of the local setup.
4Process supervisionConfigure every terminal and service to auto-restart on crash or server reboot, unattended, with no manual intervention.
5Webhook ingressStand up a reverse proxy with TLS termination and shared-secret authentication so signals can reach the box securely.
6MonitoringSchedule automated snapshots and connect uptime/latency monitoring with alerting if the box goes dark.
PHASE 03 · BROKER / EXCHANGE CONNECTION6 STEPS
1Account + verificationComplete broker or exchange verification and open the live account the system will actually trade on.
2Execution pathDecide per market whether orders route through an MT4/5 bridge, a REST/WebSocket API, or FIX — each market can differ.
3Scoped credentialsGenerate API keys restricted to trade-only permissions, explicitly excluding withdrawal rights.
4Account settingsSet margin, leverage and execution model to match exactly what the strategy was built and tested against.
5Reconciliation loopBuild ownership-tagging so the system's own fills never get confused with, or accidentally close, a manually placed trade.
6Hard risk gatesEnforce max open positions, max deployed capital, and fail-closed behavior the moment any API or connectivity error appears.
PHASE 04 · SIGNAL, EXECUTION & MONITORING6 STEPS
1Signal generationA rules-based strategy engine produces an entry or exit signal — no discretionary, in-the-moment clicking.
2Authenticated dispatchThe signal is sent to the bridge service over an authenticated, secret-signed webhook call.
3Validation + risk gateThe bridge checks the payload, applies every risk control from Phase 03, and only then forwards the order.
4Broker executionThe order is placed, the fill is confirmed, and the result is written to an immutable audit log.
5Live oversightA dashboard tracks P&L, exposure and system health in real time, with alerts on anything abnormal.
6Watchdog recoveryAn independent process checks that every layer above is still alive, and halts trading rather than failing silently.
This is the same infrastructure most people would otherwise have to piece together themselves across a local machine, a VPS, and a broker or exchange account — 23 individual steps across 4 layers. Apex Market Pros builds, connects and monitors all of it as part of your Autopilot access.
Watch a single trade move through the system, start to close.
Same signal, one continuous path. Everything below is what actually happens between the moment a rule fires and the moment the ticket closes — watch the marker travel the loop in real time.
Apex Market Pros platformCustomer's local / VPS terminalBroker / exchangePosition openActive managementPosition closed
The bright marker is one trade, looping continuously: signal → dispatch → EA → order → broker fill → open → managed → closed → next signal. Every hop is logged, and every hop is a place the system can also stop and fail safe instead of continuing blind.