Trading Signals
Browse trading systems and compare monitored performance.
Maximum profitReliabilityProfitable within a monthIntradayUnder $50Having reviewsUsing robots
Reliability
3 featured signalsGS
Gold Strategy Pro
+82%
★★★★★Copy for $35/mo
FX
FX Momentum MT5
+61%
★★★★☆Copy for $29/mo
QG
Quantum Gold
+47%
★★★★★Copy for $39/mo
Popular among subscribers
Historical statistics| Signal | Growth | Subscribers | Funds | Weeks | Trades | Win % | Activity | PF | Drawdown |
|---|---|---|---|---|---|---|---|---|---|
| Gold Strategy Pro StrategyLab | 82.40% | 124 | $184,230 | 68 | 1,482 | 74% | 82% | 2.14 | 4.81% |
| FX Momentum MT5 AlgoWorks | 61.18% | 96 | $102,810 | 51 | 934 | 69% | 74% | 1.91 | 6.20% |
| Quantum Gold QuantForge | 47.63% | 78 | $76,430 | 43 | 611 | 71% | 67% | 2.03 | 7.15% |
Risk notice. Historical statistics are not a guarantee of future results. Copying trades involves financial risk. Prototype statistics are simulated.
GS
Gold Strategy Pro ACTIVE
by StrategyLab · Automated trading signal · Cross-broker copy
RETURN+82.40%
MAX DRAWDOWN4.81%
PROFIT FACTOR2.14
SUBSCRIBERS124
TRADING WEEKS68
WIN RATE74.0%
Performance
All timeEquity curve — illustrative mock data
$12k$10k$8k$6k$4k
Trading Statistics
Verified period: 68 weeksTOTAL TRADES1,482
PROFITABLE TRADES1,097
LOSING TRADES385
WIN RATE74.0%
AVERAGE PROFIT$38.42
AVERAGE LOSS$24.17
BEST TRADE$284.60
WORST TRADE$137.40
RECOVERY FACTOR3.82
SHARPE RATIO1.67
AVG. HOLDING4h 18m
TRADES / WEEK21.8
Strategy Information
Market: Gold / XAUUSD
Style: Automated momentum
Execution: Cross-broker copy
Activity: Intraday
Strategy Logic
████████████████
Protected proprietary logic. Entry rules, parameters and internal decision model are not publicly exposed.Risk & Allocation
Recommended allocation is determined by the subscriber's own risk profile and account conditions. MQLPro can apply allocation limits, exposure limits and copy controls before execution.
Important
Past performance does not guarantee future results.
Past performance does not guarantee future results.
Recent Trading Activity
Signal-level activity| Time | Symbol | Direction | Result | Duration | Return |
|---|---|---|---|---|---|
| Today 14:32 | XAUUSD | BUY | Profit | 2h 41m | +0.84% |
| Today 09:15 | XAUUSD | SELL | Profit | 1h 58m | +0.52% |
| Yesterday 16:07 | XAUUSD | BUY | Loss | 3h 12m | −0.31% |
| Yesterday 10:42 | XAUUSD | BUY | Profit | 5h 02m | +1.06% |
Risk notice. Trading involves risk of loss. Historical performance and statistics are illustrative prototype data.
Ranking
Compare monitored trading signals using multiple performance and risk metrics.
SIGNALS TRACKED1,284
ACTIVE SIGNALS936
AVERAGE RETURN+24.8%
MEDIAN MAX DD8.42%
DATA PERIOD12 Months
Top Signals
Illustrative marketplace ranking| # | Signal | Return | Max DD | Profit Factor | Win Rate | Subscribers | Weeks | Risk / Return | |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Gold Strategy Pro StrategyLab · Gold / XAUUSD | +82.40% | 4.81% | 2.14 | 74% | 124 | 68 | 17.13 | View → |
| 2 | FX Momentum MT5 AlgoWorks · Forex | +61.18% | 6.20% | 1.91 | 69% | 96 | 51 | 9.87 | View → |
| 3 | Quantum Gold QuantForge · Gold / XAUUSD | +47.63% | 7.15% | 2.03 | 71% | 78 | 43 | 6.66 | View → |
| 4 | Index Flow Pro DataEdge · Indices | +39.22% | 5.17% | 1.82 | 68% | 63 | 47 | 7.58 | View → |
| 5 | Atlas Swing System NorthStar · Forex | +34.75% | 6.41% | 1.76 | 66% | 51 | 82 | 5.42 | View → |
| 6 | Vector Scalper Prime VectorLabs · Forex | +31.60% | 7.56% | 1.69 | 72% | 44 | 36 | 4.18 | View → |
How Ranking works
Ranking is designed as a discovery layer. Users can switch the displayed metric and period rather than treating a single number as a complete measure of a trading system. MQLPro can later calculate these rankings from verified account data.
Risk context
Return alone does not describe risk. Max drawdown, profit factor, consistency, trading history and account-level exposure should be reviewed together before copying a signal.
Ranking notice. The figures in this prototype are simulated. A production ranking engine should use verified performance records, defined calculation windows and anti-manipulation rules.
Articles
Trading, markets, risk management and algorithmic trading knowledge.
Featured · Copy Trading
Building a Robust Cross-Broker Copy Trading System
What needs to happen between a master strategy and a follower account when brokers, symbols, execution rules and risk limits are not identical.
MQLPro
Latest Articles
Knowledge HubCOPY
Copy Trading
Building a Robust Cross-Broker Copy Trading System
Architecture, execution mapping and risk controls for cross-broker replication.
RISK
Risk Management
Understanding Drawdown Before Copying a Signal
Why return alone is an incomplete description of a trading system.
DATA
Education
Profit Factor vs Win Rate: Reading Signal Statistics
Two commonly displayed metrics can tell very different stories.
EA
MetaTrader
What an Expert Advisor Actually Does
A practical overview of automated execution, rules and platform constraints.
XAU
Market Analysis
Trading Gold: Understanding Volatility and Exposure
How volatility can affect position sizing and account-level exposure.
RANK
Signals
How Signal Rankings Should Be Interpreted
Why rankings should be read together with the underlying performance metrics.
Editorial note. MQLPro Articles are designed as an educational and research layer. Published analysis should distinguish historical data, methodology and opinion.
← Back to Articles
Copy Trading · Featured
Building a Robust Cross-Broker Copy Trading System
A cross-broker copy trading platform is not simply a mechanism for duplicating an order. The difficult part is maintaining the intended exposure when the master and follower accounts operate under different trading conditions.
1. Master signal
The master side produces a normalized trading event. The platform should separate the public signal representation from proprietary strategy logic, exposing only the information required by the follower and the risk engine.
2. Normalization layer
Before a follower receives an execution instruction, the platform needs to map symbols, contract specifications, volume rules and execution constraints. A BUY event on one broker is not automatically equivalent to the same raw order parameters on another broker.
3. Risk and allocation
Follower allocation can be proportional, fixed-risk or another defined model. Account equity, exposure limits, minimum volume and other broker constraints should be evaluated before an order is sent for execution.
4. Execution and reconciliation
A connector should report whether an instruction was accepted, rejected or partially executed. Reconciliation then compares the intended follower state with the actual account state so the platform can identify discrepancies.
5. Monitoring
A production platform should retain an auditable event history: signal received, risk checks applied, connector response and resulting account state. This is useful for operational monitoring and user transparency.
Prototype note. This article describes the intended platform architecture. It does not represent live broker connectivity or guarantee execution behavior.
Community
Discuss trading, strategies, platforms, automation and market research with other MQLPro users.
MQLPro Community
Ask questions, share research and discuss trading technology. Community content is separate from verified signal performance and marketplace listings.
AllUnansweredPopularFollowing
AR
How should symbol mapping work across different brokers?
Looking at a cross-broker copy architecture. How should the connector handle differences such as XAUUSD naming, contract size and minimum volume?
Copy TradingExecutionDN
Which metrics do you check before following a signal?
I am comparing return, maximum drawdown, profit factor and trading history. Interested in how others organize the comparison.
SignalsRiskFK
MT5 EA on VPS: what should I monitor?
Collecting a checklist for uptime, terminal connection, order execution and log monitoring for automated systems.
MetaTraderExpert AdvisorSA
Proportional allocation vs fixed-risk copying
What are the practical differences between proportional sizing and fixed-risk models when follower account balances vary?
Copy TradingRisk ManagementNR
How are you handling XAUUSD volatility?
Discussion about exposure limits and execution considerations when gold moves rapidly around major market events.
Market AnalysisGoldCommunity note. User discussions are community-generated and should not be treated as verified performance data, financial advice or an endorsement by MQLPro.
← Back to Community
Copy Trading
How should symbol mapping work across different brokers?
AR
Arif R.
Original post · 2h ago
Looking at a cross-broker copy architecture. How should the connector handle differences such as symbol naming, contract size, minimum volume and execution constraints? I am interested in the architecture rather than a specific broker.
QF
QuantForge
1h 42m ago
A normalization layer is useful. Keep the master event abstract, then map symbol, volume and execution rules for each follower account before sending the order.
AW
AlgoWorks
1h 18m ago
I would also keep reconciliation separate from execution. The connector should report the actual account state so the platform can detect differences between intended and executed positions.
SL
StrategyLab
54m ago
Risk checks should happen before the connector call. That allows allocation, exposure and broker-specific constraints to be evaluated consistently.
Join the discussion
Documentation
Guides and technical references for using the MQLPro platform.
Welcome to MQLPro Documentation
Start with the platform basics, then explore signal discovery, copy trading, market products, performance metrics, risk controls and connector architecture.
Get Started
Recommended pathGetting Started
Understand the platform, create an account and learn the basic workflow.
6 guides
Signals
Learn how to browse signals, inspect historical metrics and open signal details.
9 guides
Copy Trading
Architecture, allocation, execution, reconciliation and follower account concepts.
12 guides
Market
Browse products and understand product listings, versions and marketplace information.
7 guides
Ranking & Performance
Definitions and methodology for performance metrics displayed by MQLPro.
8 guides
Risk Management
Understand exposure, allocation limits, drawdown and account-level controls.
10 guides
Broker Connectors
Technical concepts for connecting follower accounts and handling broker differences.
11 guides
API & Webhooks
Integration concepts for future external applications and event-driven workflows.
5 guides
Documentation status. This prototype defines the public information architecture. Live broker APIs, authentication, webhooks and production connector behavior are not connected yet.
Getting Started
MQLPro Documentation · Updated 16 September 2026
Overview
MQLPro is structured around signal discovery, performance research, marketplace products and copy-trading infrastructure. This documentation explains how those components are intended to work.
Core workflow
- Browse the Signals marketplace and select a signal to inspect.
- Review historical performance, drawdown and other available metrics.
- Check the signal's risk information and subscription/copy settings.
- Configure the follower allocation and applicable risk limits.
- Connect the follower account through a supported connector.
- Monitor execution and reconciliation after copying begins.
Important concepts
Signal
A signal represents a monitored trading strategy or account whose historical and current performance can be presented to users.
Follower
A follower is an account configured to replicate a signal according to its allocation and risk settings.
Connector
A connector is the integration layer responsible for translating platform instructions into broker-specific execution operations.
Prototype scope: examples on this page describe MQLPro's planned information architecture. Actual broker compatibility and execution behavior depend on the eventual connector implementation.
Example event flow
Signal Event → Normalize → Risk Check → Connector → Broker → Execution Report → Reconciliation
Next steps
Use the documentation sidebar to explore the relevant module. For implementation questions, the Community section can provide a discussion layer while production integrations are developed.
← Back
Login
Sign in to manage your MQLPro account, signals and copy-trading settings.
Forgot password?
OR
Don't have an account? Register
Prototype. Authentication is not connected to WordPress or a production user database yet.
← Back
Create an account
Create your MQLPro account to follow signals, manage marketplace purchases and configure copy trading.
Already have an account? Login
Prototype. Account creation currently demonstrates the UI flow only. No credentials are stored.
My Account
Manage your profile, signals, purchases and copy-trading configuration.
IH
MQLPro User
user@example.com
Active Signals2
Subscriptions3
Market Purchases4
Copy Accounts1
Recent Activity
| Activity | Status | Date |
|---|---|---|
| Subscribed to Alpha Trend | Active | 16 Sep 2026 |
| Added follower account | Connected | 15 Sep 2026 |
| Purchased Quantum Titan MT5 | Completed | 12 Sep 2026 |
Account layer. This page is the front-end foundation for the future MQLPro user system. Real authentication, subscriptions, purchases and broker connections will be wired to their respective back-end services later.
Dashboard
Your MQLPro signals, subscriptions and copy-trading activity.
Welcome back, MQLPro User
Monitor your subscriptions and connected copy-trading accounts from one place.
Active Signals2
Monthly Subscriptions3
Copy Accounts1
Market Purchases4
My Signal Subscriptions
Alpha Trend
+18.42%
DD 5.21%
Active
Gold Momentum
+12.61%
DD 4.81%
Active
Index Pulse
+8.77%
DD 3.94%
Paused
Copy Trading Accounts
| Account | Broker | Signal | Status | Last Sync |
|---|---|---|---|---|
| Primary Follower | Demo Broker | Alpha Trend | Connected | 2 min ago |
Quick Actions
Dashboard status. Subscription, payment, broker connectivity and execution values shown here are prototype data.
Browse Signals
Discover trading signals, compare performance metrics and open Signal Detail pages before subscribing.
My Signal Subscriptions
Alpha Trend
+18.42%
DD 5.21%
Active
Gold Momentum
+12.61%
DD 4.81%
Active
Index Pulse
+8.77%
DD 3.94%
Paused
Copy Trading Accounts
| Account | Broker | Signal | Status | Last Sync |
|---|---|---|---|---|
| Primary Follower | Demo Broker | Alpha Trend | Connected | 2 min ago |
Connector status. The connected account is prototype data. Real broker authentication and execution will be connected later.
My Purchases
| Product | Type | Version | Status | Date |
|---|---|---|---|---|
| Quantum Titan MT5 | Trading Tool | v2.4 | Completed | 12 Sep 2026 |
| Risk Manager Pro | Utility | v1.8 | Completed | 08 Sep 2026 |
| Signal Bridge | Connector | v1.2 | Completed | 02 Sep 2026 |
Account Settings
IH
MQLPro User
user@example.com
Subscribe to Signal
Choose a subscription plan and review your order before continuing.
Alpha Trend
$49 / month
1. Choose a plan
Monthly
$49
Billed every month. Cancel according to the applicable subscription terms.
3 Months
$129
Three-month subscription period.
12 Months
$399
Annual subscription period.
2. Account
3. Payment method
Prototype. No real payment is processed. The next stage will connect this flow to the selected payment provider and subscription service.
● Order created
Subscription Review
Your subscription request has been prepared. Review the details below.
SignalAlpha Trend
PlanMonthly
Amount$49
Prototype. Payment confirmation is simulated. No funds have been charged.
Purchase Product
Review the product and complete the purchase setup.
MQLPro
MARKET
MARKET
Quantum Titan MT5
1. License
Personal License
For use on your own supported trading account.
Commercial License
For eligible commercial or multi-account usage.
2. Account
3. Payment
Prototype. No real payment is processed. Product delivery and licensing will be connected in a later integration stage.
● Order created
Purchase Review
Your market purchase request has been prepared. Review the details below.
ProductQuantum Titan MT5
LicensePersonal
Amount$149
Prototype. Payment is simulated. No funds have been charged and no product has been delivered.
Orders & Subscriptions
Manage your MQLPro signal subscriptions and Market purchases.
Signal Subscriptions
Market Purchases
Alpha Trend
$399
ActiveStarted16 Sep 2026
Renewal16 Sep 2027
Performance+18.42%
Max DD5.21%
Gold Momentum
$249
ActiveStarted01 Sep 2026
Renewal01 Mar 2027
Performance+12.61%
Max DD4.81%
Index Pulse
$129
PausedStarted10 Aug 2026
Renewal10 Nov 2026
Performance+8.77%
Max DD3.94%
Prototype data. Billing, renewal, cancellation, license delivery and order history will be connected to the production account system in a later backend stage.
Copy Trading Accounts
Connect follower accounts and manage their copy-trading configuration.
Connected Accounts1
Active Copies1
Last Sync2 min
Connection StatusConnected
Primary Follower
Connected
BrokerDemo Broker
PlatformMT5
Account•••• 4821
Copy StatusActive
Connect another follower account
Choose a supported broker connector and authorize the follower account. MQLPro will use the connector to receive and route eligible copy instructions.
Broker Connector Center
Monitor broker connections, connector health and the copy-trading execution path.
Connector Overview
MQLPro separates the public marketplace from broker authentication and execution. A connector acts as the controlled bridge between a follower account and the MQLPro copy engine.
Active Connectors1
Connected Accounts1
Heartbeat2 min ago
System StatusOperational
Primary Connector
Demo Broker — MT5 Connector
TransportConnector
PlatformMT5
AuthenticationConnected
ExecutionReady
Supported Connections
These are prototype connector types. Production support will depend on broker infrastructure, platform capabilities and the connector implementation.
MT5 Direct Connector
Trade events · account state · execution routing · heartbeat
Broker API Connector
Depends on broker API access, permissions, authentication and order endpoints.
Python Execution Bridge
Can act as an execution bridge where the supported broker/platform interface permits it.
Custom Broker Connector
Used where a broker requires its own authentication, API or platform integration.
Connection Health
Operational indicators for the prototype connector.
AuthenticationOK
HeartbeatOK
Account ReadOK
Execution ChannelREADY
Recent Checks
| Check | Result | Last Checked | Latency |
|---|---|---|---|
| Connector heartbeat | OK | 22:14 | 84 ms |
| Account synchronization | OK | 22:13 | 126 ms |
| Signal routing | READY | 22:12 | 91 ms |
| Execution channel | READY | 22:12 | 118 ms |
Production note: A green health indicator in the UI must not be treated as proof that a broker supports every required API or execution operation. Capability verification belongs in the connector onboarding process.
Copy Execution Architecture
Logical flow for cross-broker copy trading. The public Signal page does not directly access follower broker credentials.
Signal Provider
→
MQLPro Signal Engine
→
Risk / Allocation
→
Connector
→
Follower Broker
The connector receives only the information required for the authorized account operation. The implementation may differ between MT5, broker APIs and other supported platforms.
Security boundary: Broker credentials, tokens and execution secrets should be isolated from the public marketplace UI and stored using appropriate server-side security controls.
Onboarding Requirements
Before activating a production connector, MQLPro should verify authentication, account read access, order placement/modification/cancellation, symbol mapping, position state, error handling, rate limits, heartbeat and disconnect recovery.
Signal Engine
Monitor master signals, normalized trade events and downstream copy routing.
Engine Overview
The Signal Engine converts authorized master activity into normalized events before risk allocation and connector execution. Public users see strategy performance, not broker credentials or execution secrets.
Master Signals12
Active Events3
Followers Routed47
Engine StatusOperational
Core Processing Flow
Master Account
→
Trade Event
→
Normalize
→
Risk / Allocation
→
Follower Queue
→
Connector
Execution boundary: The engine should not assume that a follower broker can execute the same symbol, volume, price or order type as the master. Mapping and validation occur before execution.
Master Signals
Prototype master strategies currently registered with the engine.
| Signal | Asset Group | Followers | State |
|---|---|---|---|
| Alpha Trend | Forex | 24 | LIVE |
| Gold Momentum | XAUUSD | 15 | LIVE |
| Index Pulse | Indices | 8 | LIVE |
| Crypto Swing | Crypto | 0 | TEST |
Normalized Trade Events
A normalized event is an internal representation. It is not a public copy instruction and does not expose a master's account credentials.
Alpha Trend · Position Opened
Accepted
Gold Momentum · Position Updated
Accepted
Alpha Trend · Stop Modified
Queued
Index Pulse · Position Closed
Routed
Example internal event
event_id: EVT-98214
signal_id: SIG-ALPHA
event_type: POSITION_OPEN
instrument: XAUUSD
direction: BUY
master_reference: internal
timestamp: 2026-09-16T22:14:02
status: ACCEPTED
Follower Routing
The routing layer resolves which authorized followers receive an eligible event and passes the result to the appropriate connector.
| Signal | Followers | Risk Mode | Queue | Status |
|---|---|---|---|---|
| Alpha Trend | 24 | Proportional | Normal | Ready |
| Gold Momentum | 15 | Fixed Risk % | Normal | Ready |
| Index Pulse | 8 | Proportional | Normal | Ready |
Important: Routing eligibility must check subscription status, follower account status, symbol mapping, risk limits and connector health before an execution request is created.
Engine Monitoring
Event Latency91 ms
Queue Depth3
Rejected Events0
Last Heartbeat22:14:02
Operational Checks
| Component | Check | Result | Last Check |
|---|---|---|---|
| Event Listener | Master event intake | OK | 22:14 |
| Normalizer | Schema validation | OK | 22:14 |
| Risk Layer | Follower allocation | OK | 22:14 |
| Routing Queue | Dispatch readiness | OK | 22:14 |
Risk & Allocation Engine
Apply follower-specific risk rules before an eligible copy instruction reaches a broker connector.
Risk Engine Overview
A master trade event is not copied blindly. The allocation layer evaluates each follower's subscription, account equity, configured risk mode, limits and instrument constraints.
Followers Evaluated47
Rules Applied142
Blocked Requests2
Engine StatusOperational
Processing Flow
Normalized Event
→
Subscription Check
→
Risk Profile
→
Volume Allocation
→
Safety Guards
→
Execution Request
Risk Rules
Prototype rules used to determine whether and how a signal is allocated to a follower.
Subscription ActiveFollower must have an eligible subscription.
Required
Pass
ENABLEDAccount Drawdown GuardBlocks new exposure after the configured threshold.
10%
Current 3.2%
OKRisk MultiplierScales the normalized master allocation.
1.00x
Follower profile
ACTIVEMaximum ExposurePrevents exposure above account-level limits.
20%
Current 11.4%
OKInstrument MappingRequires a valid follower symbol mapping.
Required
1 pending
CHECKDefault Risk Profile
Follower Allocation
Illustrative allocation results for a single normalized event. Values are prototype calculations, not live orders.
| Follower | Equity | Risk Mode | Multiplier | Calculated Allocation | Eligibility |
|---|---|---|---|---|---|
| Primary Follower | $10,000 | Proportional | 1.00x | 0.27 lot* | Eligible |
| Follower B | $5,000 | Proportional | 0.50x | 0.07 lot* | Eligible |
| Follower C | $2,500 | Fixed Risk % | 1.00x | 0.03 lot* | Eligible |
| Follower D | $1,000 | Proportional | 1.00x | — | Blocked |
*Illustrative only. Final volume depends on the strategy's normalized risk input, instrument contract specifications, broker constraints, account currency, leverage and the follower's configuration. The UI must not imply guaranteed identical sizing across brokers.
Safety Guards
Hard checks that can stop an execution request before it reaches a connector.
| Guard | Condition | Current | Action | Status |
|---|---|---|---|---|
| Max Drawdown | ≥ 10% | 3.2% | Block new copy | Clear |
| Max Exposure | ≥ 20% | 11.4% | Block new exposure | Clear |
| Connector Health | Not operational | Operational | Pause routing | Clear |
| Subscription | Inactive / expired | Active | Reject request | Clear |
| Symbol Mapping | Missing | 1 pending | Reject request | Review |
Allocation Simulation
Test the allocation logic with example account parameters before connecting a production execution path.
No simulation has been run.
Execution Queue
Track eligible copy requests from allocation through connector acknowledgement and final execution state.
Execution Overview
The queue is the controlled handoff between risk-approved follower instructions and broker connectors. Each request receives an internal identifier so its lifecycle can be audited.
Queued3
Processing1
Executed Today126
Failed2
Execution Flow
Risk Approved
→
Create Request
→
Queue
→
Connector
→
Broker
→
Acknowledge
→
Reconcile
Order Queue
Prototype requests waiting for or passing through the execution layer.
REQ-77102
Alpha Trend · Primary Follower · Position Open
REQ-77101
Gold Momentum · Primary Follower · Position Update
REQ-77100
Index Pulse · Follower C · Position Close
REQ-77099
Alpha Trend · Follower D · Position Open
Order Lifecycle
Example lifecycle for request REQ-77102.
22:14:02.118 — Event receivedMaster event EVT-98214 normalized successfully.
22:14:02.136 — Risk approvedFollower subscription, drawdown and allocation rules passed.
22:14:02.141 — Request createdExecution request REQ-77102 assigned.
22:14:02.158 — Connector dispatchedRequest handed to the MT5 connector.
22:14:02.247 — Broker acknowledgementPrototype acknowledgement received.
22:14:02.251 — ReconciliationFollower position state queued for verification.
Reconciliation
Compare the expected internal state with the follower account state after connector execution.
| Request | Expected | Follower State | Result |
|---|---|---|---|
| REQ-77102 | Position Open | Pending check | VERIFY |
| REQ-77101 | Position Modified | Modified | MATCH |
| REQ-77100 | Position Closed | Closed | MATCH |
| REQ-77098 | Position Open | Volume mismatch | REVIEW |
Reconciliation matters: a successful connector response does not by itself prove that the final follower position matches the intended state. The production system should verify actual account state and handle partial fills, rejected orders and broker-side modifications.
Errors & Recovery
Failed requests should become observable and recoverable rather than silently disappearing.
| Request | Failure | Action | Status |
|---|---|---|---|
| REQ-77098 | Volume constraint | Recalculate / review | REVIEW |
| REQ-77091 | Connector timeout | Retry with backoff | RECOVERED |
| REQ-77082 | Symbol mapping missing | Block request | BLOCKED |
Account Synchronization
Maintain a consistent internal view of follower balances, positions and execution state across connected brokers.
Synchronization Overview
The synchronization layer continuously refreshes the platform's internal representation of follower accounts. It is separate from the signal engine: signals create intent, while synchronization verifies actual account state.
Connected Accounts47
Healthy45
Needs Review2
Last Sync22:14:05
State Synchronization Flow
Broker Connector
→
Account Snapshot
→
Normalize
→
Compare
→
Reconcile
→
Internal State
What is synchronized?
| State | Purpose | Frequency | Status |
|---|---|---|---|
| Account Balance | Risk and exposure calculations | Periodic | ACTIVE |
| Open Positions | Copy state and reconciliation | Near real-time | ACTIVE |
| Pending Orders | Execution tracking | Near real-time | ACTIVE |
| Margin / Exposure | Safety guard evaluation | Periodic | ACTIVE |
Connected Accounts
Illustrative follower account health across connector types.
Primary Follower
$10,000 equity
Last sync 22:14:05
HEALTHYFollower B
$5,000 equity
Last sync 22:14:04
HEALTHYFollower C
$2,500 equity
Last sync 22:13:58
HEALTHYFollower D
$1,000 equity
Last sync 21:58:12
STALEPrivacy boundary: the dashboard should expose only the minimum account information required by the user. Broker credentials, API secrets and connector tokens should never be rendered in this page.
Follower Positions
Compare platform intent with the current broker-reported position state.
| Account | Symbol | Side | Volume | Platform State | Broker State |
|---|---|---|---|---|---|
| Primary Follower | XAUUSD | BUY | 0.27 | Open | MATCH |
| Follower B | XAUUSD | BUY | 0.07 | Open | MATCH |
| Follower C | US500 | SELL | 0.03 | Closed | MATCH |
| Follower D | XAUUSD | BUY | — | Blocked | NO ORDER |
Balance & Exposure Snapshot
Illustrative account snapshots used by the risk layer.
| Account | Balance | Equity | Margin Used | Exposure | Snapshot |
|---|---|---|---|---|---|
| Primary Follower | $10,120 | $10,000 | $1,220 | 11.4% | 22:14:05 |
| Follower B | $5,040 | $5,000 | $620 | 9.8% | 22:14:04 |
| Follower C | $2,520 | $2,500 | $310 | 8.1% | 22:13:58 |
Reconciliation Center
Exceptions are retained until the platform state and broker state are aligned or an operator resolves the difference.
| Reference | Mismatch | Detected | Suggested Action | Status |
|---|---|---|---|---|
| ACC-10024 | Account snapshot stale | 21:58 | Refresh connector | OPEN |
| REQ-77098 | Volume differs from intent | 21:42 | Review execution | OPEN |
| REQ-77091 | Connector timeout | 20:11 | Verify broker state | RESOLVED |
Symbol Mapping
Normalize instruments and broker-specific symbol names before a copy request reaches execution.
Symbol Mapping Overview
Cross-broker copy requires an instrument normalization layer. A strategy may publish one canonical instrument while individual brokers expose different symbol names, suffixes, contract sizes or trading constraints.
Canonical Symbols38
Broker Profiles7
Active Mappings214
Needs Review1
Normalization Flow
Master Symbol
→
Canonical Instrument
→
Broker Profile
→
Follower Symbol
→
Contract Validation
Why this layer exists
| Difference | Example | Required Handling |
|---|---|---|
| Symbol name | XAUUSD / XAUUSD.a | Explicit mapping |
| Contract size | 100 / broker-specific | Contract metadata |
| Volume step | 0.01 / 0.10 | Normalize and validate |
| Minimum volume | 0.01 / 0.10 | Broker constraint check |
| Trading session | Different market hours | Session eligibility |
Active Mappings
Illustrative mappings from canonical MQLPro instruments to broker-specific symbols.
XAUUSD
XAUUSD.a
MT5 Profile A
VALIDXAUUSD
GOLD
API Profile B
VALIDEURUSD
EURUSDm
MT5 Profile A
VALIDUS500
SPX500.cash
API Profile B
REVIEWBroker Profiles
A broker profile stores non-secret trading metadata required for safe normalization and execution validation.
| Profile | Connector | Symbols | Metadata | Status |
|---|---|---|---|---|
| MT5 Profile A | MT5 | 82 | Complete | ACTIVE |
| API Profile B | Broker API | 61 | Complete | ACTIVE |
| MT5 Profile C | MT5 | 43 | Complete | ACTIVE |
| API Profile D | Broker API | 28 | 1 missing | REVIEW |
Security boundary: broker credentials, API keys and login secrets are connector secrets. They should be stored in the backend/secret store and never included in the symbol-mapping payload rendered to the browser.
Normalization Rules
Rules define how canonical instruments are translated into broker-specific execution parameters.
| Rule | Purpose | Example | Status |
|---|---|---|---|
| Alias Mapping | Translate symbol aliases | XAUUSD → XAUUSD.a | ENABLED |
| Volume Step | Round to broker step | 0.273 → 0.27 | ENABLED |
| Minimum Volume | Reject unsupported size | 0.03 below 0.10 → reject | ENABLED |
| Contract Size | Normalize sizing calculation | 100 units | ENABLED |
| Session Check | Prevent closed-market requests | Outside trading session | ENABLED |
Mapping Validation
Every execution request should pass instrument validation before entering the connector.
| Check | Result | Details |
|---|---|---|
| Canonical symbol exists | PASS | XAUUSD registered |
| Follower symbol mapped | PASS | XAUUSD.a |
| Contract metadata | PASS | Available |
| Volume constraints | PASS | Step 0.01 |
| Trading session | PASS | Open |
Copy Policies
Define how a follower subscription may translate a strategy signal into an eligible copy instruction.
Copy Policy Overview
Policies sit between a published strategy and the execution queue. They determine whether a signal is eligible for a specific follower before sizing and broker execution occur.
Active Policies32
Protected Accounts47
Rules Evaluated Today4,821
Blocked Requests17
Policy Evaluation Flow
Signal
→
Subscription
→
Safety Rules
→
Allocation
→
Exposure Limit
→
Execution
Policy Principles
| Principle | Purpose | Example |
|---|---|---|
| Explicit opt-in | Only subscribed accounts receive copies | Active subscription required |
| Risk bounded | Respect account-level limits | Maximum DD / exposure |
| Broker aware | Respect follower constraints | Volume and session checks |
| Fail closed | Reject uncertain requests | Missing mapping → block |
Safety Rules
Rules that can stop a copy request before it reaches the execution layer.
Maximum Drawdown Guard
10%
ENABLEDMaximum Exposure
25%
ENABLEDDaily Loss Guard
3%
ENABLEDSymbol Eligibility
Strict
ENABLEDTrading Session
Broker
ENABLEDAllocation Policy
Choose the sizing model applied after a request passes subscription and safety checks.
| Mode | Calculation Basis | Use Case | Status |
|---|---|---|---|
| Proportional Equity | Follower equity / reference equity | Scale strategy exposure | AVAILABLE |
| Risk Percentage | Target risk per position | Risk-normalized copying | AVAILABLE |
| Fixed Lot | Configured volume | Simple volume policy | AVAILABLE |
| Multiplier | Base size × multiplier | Controlled scaling | AVAILABLE |
Important: allocation is a calculation policy, not a guarantee of identical broker exposure. Contract size, leverage, minimum volume, volume step and execution conditions must still be validated by the broker profile.
Exposure Limits
Account-level and strategy-level limits provide a second control layer after position sizing.
| Limit | Configured | Current | Action |
|---|---|---|---|
| Strategy Exposure | 25% | 11.4% | ALLOW |
| Symbol Exposure | 15% | 8.2% | ALLOW |
| Daily Loss | 3% | 0.7% | ALLOW |
| Open Positions | 20 | 7 | ALLOW |
Emergency Controls
Operational controls for temporarily stopping new copy instructions. Existing broker positions are not automatically altered by these controls unless a separate close-position policy is explicitly implemented.
| Control | Current State | Effect |
|---|---|---|
| Global Copy Pause | OFF | Stops new copy requests globally |
| Strategy Pause | OFF | Stops a selected strategy |
| Account Pause | OFF | Stops copying to selected follower |
| New Exposure Lock | OFF | Blocks new positions while allowing state sync |
Production requirement: emergency controls should be enforced server-side. A browser-only toggle is not a reliable trading safety mechanism.
Market
Trading robots, indicators and tools for MetaTrader and algorithmic trading.
FeaturedTop RatedFreeUnder $50MT5MT4
Popular products
24,812 productsQT
Quantum Titan MT5
QuantForge
Automated multi-session system designed for systematic market execution.
$99View product →
GM
Gold Momentum Pro
AlgoWorks
Momentum-oriented trading robot with configurable risk and execution settings.
$79View product →
MS
Market Structure X
ChartLab
Charting toolkit for market structure, levels and configurable alerts.
$49View product →
TM
Trade Manager Pro
RiskTools
Position management utility with risk sizing and trade control tools.
$35View product →
VF
Volume Flow Analyzer
DataEdge
Volume and flow visualization with configurable market filters.
$29View product →
EC
Execution Core
DevStack
Reusable execution and order-management components for developers.
$59View product →
Become a developer on MQLPro
Publish trading applications, manage versions, documentation, licensing and sales from one developer account.Quantum Titan MT5
by QuantForge · Expert Advisor · MetaTrader 5
Product overview
Quantum Titan MT5 is a prototype marketplace listing for an automated trading application. The real MQLPro implementation will expose product documentation, supported platforms, release history, licensing information and developer details.
Product specifications
PLATFORMMetaTrader 5
TYPEExpert Advisor
VERSION3.8.2
LAST UPDATE2 days ago
LICENSEPersonal
INSTALLATIONAutomatic / Manual
What's included
EA package, user documentation, update access and product support. Actual files and licensing will be implemented with the marketplace backend.