MQLPro — Signals & Market

MQLPro

Trading Signals

Browse trading systems and compare monitored performance.

TRADING SYSTEM

PROFIT / MONTH, %

MAX DRAWDOWN, %

SUBSCRIPTION FEE

Maximum profitReliabilityProfitable within a monthIntradayUnder $50Having reviewsUsing robots

Reliability

3 featured signals

Gold Strategy Pro

StrategyLab

+82%

98%Reliability

124Subscribers

4.81%Max DD

★★★★★Copy for $35/mo

FX Momentum MT5

AlgoWorks

+61%

96%Reliability

96Subscribers

6.20%Max DD

★★★★☆Copy for $29/mo

Quantum Gold

QuantForge

+47%

94%Reliability

78Subscribers

7.15%Max DD

★★★★★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.

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 time

Equity curve — illustrative mock data

$12k$10k$8k$6k$4k

Trading Statistics

Verified period: 68 weeks

TOTAL 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.

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.

My Account

Manage your profile, signals, purchases and copy-trading configuration.

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

Forex · 12 Month subscription

+18.42%

DD 5.21%

Active

Gold Momentum

XAUUSD · 6 Month subscription

+12.61%

DD 4.81%

Active

Index Pulse

Indices · 3 Month subscription

+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

Forex · 12 Month subscription

+18.42%

DD 5.21%

Active

Gold Momentum

XAUUSD · 6 Month subscription

+12.61%

DD 4.81%

Active

Index Pulse

Indices · 3 Month subscription

+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

MQLPro User

user@example.com

Copy Trading Accounts

Connect follower accounts and manage their copy-trading configuration.

Connected Accounts1

Active Copies1

Last Sync2 min

Connection StatusConnected

Primary Follower

Follower Account · Alpha Trend

Connected

BrokerDemo Broker

PlatformMT5

Account•••• 4821

Copy StatusActive

Risk Mode

Risk Multiplier

Maximum Drawdown Guard

Copy Direction

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

Account Label

Server

Time	Event	Account	Status
22:14	Heartbeat received	Primary Follower	OK
22:12	Copy instruction synchronized	Primary Follower	Synced
22:03	Signal subscription checked	Alpha Trend	Active
21:48	Connector authenticated	Primary Follower	Connected

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

MetaTrader 5 · Expert Advisor / terminal bridge

Available

Trade events · account state · execution routing · heartbeat

Broker API Connector

Broker-provided REST / WebSocket API

Setup Required

Depends on broker API access, permissions, authentication and order endpoints.

Python Execution Bridge

Local / hosted Python integration

Prototype

Can act as an execution bridge where the supported broker/platform interface permits it.

Custom Broker Connector

Broker-specific implementation

Setup Required

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

Event EVT-98214 · normalized · 22:14:02

Accepted

Gold Momentum · Position Updated

Event EVT-98213 · normalized · 22:13:41

Accepted

Alpha Trend · Stop Modified

Event EVT-98212 · normalized · 22:12:18

Queued

Index Pulse · Position Closed

Event EVT-98211 · normalized · 22:11:57

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

ENABLED

Account Drawdown GuardBlocks new exposure after the configured threshold.

10%

Current 3.2%

Risk MultiplierScales the normalized master allocation.

1.00x

Follower profile

ACTIVE

Maximum ExposurePrevents exposure above account-level limits.

20%

Current 11.4%

Instrument MappingRequires a valid follower symbol mapping.

Required

1 pending

CHECK

Default Risk Profile

Risk Mode

Risk Multiplier

Maximum Drawdown

Maximum Exposure

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.

Follower Equity

Master Allocation

Risk Multiplier

Drawdown

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

XAUUSD · BUY · created 22:14:03 · connector MT5

PROCESSING

REQ-77101

Gold Momentum · Primary Follower · Position Update

XAUUSD · MODIFY · created 22:13:42 · connector MT5

ACKNOWLEDGED

REQ-77100

Index Pulse · Follower C · Position Close

US500 · CLOSE · created 22:12:01 · connector MT5

EXECUTED

REQ-77099

Alpha Trend · Follower D · Position Open

XAUUSD · BUY · blocked by risk guard

BLOCKED

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

ACC-10021 · MT5 Connector

$10,000 equity

Last sync 22:14:05

HEALTHY

Follower B

ACC-10022 · MT5 Connector

$5,000 equity

Last sync 22:14:04

HEALTHY

Follower C

ACC-10023 · API Connector

$2,500 equity

Last sync 22:13:58

HEALTHY

Follower D

ACC-10024 · API Connector

$1,000 equity

Last sync 21:58:12

STALE

Privacy 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

Canonical · Gold Spot

XAUUSD.a

MT5 Profile A

VALID

XAUUSD

Canonical · Gold Spot

GOLD

API Profile B

VALID

EURUSD

Canonical · Euro / US Dollar

EURUSDm

MT5 Profile A

VALID

US500

Canonical · US Equity Index

SPX500.cash

API Profile B

REVIEW

Broker 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

Block new exposure when configured account drawdown threshold is reached.

10%

ENABLED

Maximum Exposure

Prevent new positions when total strategy exposure exceeds the account policy.

25%

ENABLED

Daily Loss Guard

Stop eligible new requests after the configured daily loss limit.

ENABLED

Symbol Eligibility

Reject symbols not mapped or explicitly permitted for the follower.

Strict

ENABLED

Trading Session

Reject requests outside the follower broker's supported session.

Broker

ENABLED

Allocation 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.

Subscription & Billing

Manage signal subscriptions, billing status and copy-trading entitlements.

Subscription & Billing Overview

Billing determines whether a user has an active commercial entitlement to copy a selected signal. Payment state and trading authorization should remain separate backend concepts.

Active Subscriptions84

Monthly Recurring$8,420

Pending Renewal6

Payment Issues2

Entitlement Flow

Signal Selected

→

Checkout

→

Payment

→

Subscription

→

Entitlement

→

Copy Eligible

Billing States

State	Meaning	Copy Access
Active	Paid and within subscription period	ELIGIBLE
Pending	Payment or activation not finalized	HOLD
Past Due	Renewal payment requires attention	POLICY
Cancelled / Expired	Entitlement period ended	NOT ELIGIBLE

Active Subscriptions

Subscriptions connect a user to a signal product and its commercial terms.

Alpha Trend

SUB-10421 · Monthly · Next renewal 01 Oct 2026

$99/mo

Auto renewal

ACTIVE

Gold Momentum

SUB-10418 · Monthly · Next renewal 28 Sep 2026

$129/mo

Auto renewal

ACTIVE

Index Pulse

SUB-10402 · Quarterly · Ends 12 Nov 2026

$249/qtr

Manual renewal

ACTIVE

EUR Scalper

SUB-10387 · Monthly · Payment requires attention

$79/mo

Renewal failed

PAST DUE

Signal Plans

Commercial plans are separate from the strategy's performance and risk metrics.

Plan	Billing	Price	Copy Entitlement	Status
Alpha Trend Standard	Monthly	$99	1 strategy	ACTIVE
Alpha Trend Pro	Monthly	$149	3 strategies	ACTIVE
Portfolio Access	Monthly	$249	10 strategies	ACTIVE
Trial	Limited	$0	Read-only / configured trial	LIMITED

Architecture rule: the frontend should never decide that payment equals trading authorization. A backend entitlement service should validate subscription status, product scope, expiry and any account-specific conditions before copy eligibility is granted.

Invoices & Payments

Illustrative billing records. Payment provider references should be stored securely and only safe display fields exposed here.

Invoice	Subscription	Amount	Date	Status
INV-2026-09121	Alpha Trend	$99	01 Sep 2026	PAID
INV-2026-09118	Gold Momentum	$129	28 Aug 2026	PAID
INV-2026-09103	EUR Scalper	$79	01 Sep 2026	PAST DUE
INV-2026-09088	Index Pulse	$249	12 Aug 2026	PAID

Copy Entitlements

Entitlement is the final authorization state consumed by the copy engine. It should be independently queryable and auditable.

User / Account	Signal	Subscription	Expires	Copy Access
Primary Follower	Alpha Trend	SUB-10421	01 Oct 2026	GRANTED
Follower B	Gold Momentum	SUB-10418	28 Sep 2026	GRANTED
Follower C	Index Pulse	SUB-10402	12 Nov 2026	GRANTED
Follower D	EUR Scalper	SUB-10387	01 Sep 2026	SUSPENDED

Copy eligibility check: entitlement should be evaluated together with risk policy, broker connectivity, symbol mapping and account safety state. An active subscription alone does not override a safety block.

Signal Intake Gateway

Receive, validate, deduplicate and normalize external strategy events before they enter the MQLPro signal engine.

Signal Intake Overview

The intake gateway is the boundary between external strategy providers and the internal copy-trading pipeline. It should accept only authenticated, schema-valid events and assign a unique event identity before processing.

Active Endpoints12

Events Today18,421

Accepted18,307

Rejected114

Signal Intake Flow

External Provider

→

Webhook / API

→

Authentication

→

Schema Validation

→

Deduplication

→

Canonical Event

→

Signal Engine

Canonical Event Contract

{ "event_id": "evt_01J...", "strategy_id": "strategy_alpha", "instrument": "XAUUSD", "action": "OPEN", "direction": "BUY", "timestamp": "2026-09-16T14:32:11Z", "source": "provider_a" }

Production rule: the intake gateway should treat the event ID as an idempotency key. A repeated event must not create a second copy instruction.

Signal Endpoints

Endpoints represent controlled ingestion channels. Secrets and signing keys are never rendered in the browser.

Strategy Alpha Webhook

POST · /v1/signals/alpha · HMAC signature

18,102 events

Last: 14:32 UTC

ACTIVE

Gold Momentum API

POST · /v1/signals/gold · API key + timestamp

6,841 events

Last: 14:31 UTC

ACTIVE

Index Pulse Webhook

POST · /v1/signals/index · HMAC signature

3,214 events

Last: 14:29 UTC

ACTIVE

Legacy Connector

POST · /v1/legacy/signals · migration pending

264 events

Last: 11:02 UTC

REVIEW

Event Log

Operational view of received events and their intake disposition.

Event ID	Source	Instrument	Action	Received	Status
evt_8F21A	Strategy Alpha	XAUUSD	OPEN BUY	14:32:11	ACCEPTED
evt_8F219	Strategy Alpha	EURUSD	CLOSE	14:31:48	ACCEPTED
evt_8F217	Gold Momentum	XAUUSD	OPEN SELL	14:30:02	DUPLICATE
evt_8F211	Legacy Connector	US500	OPEN BUY	14:27:39	REJECTED

Validation Pipeline

Validation should happen before an event becomes an internal signal instruction.

Check	Purpose	Example Result
Authentication	Verify source identity/signature	PASS
Timestamp Window	Reject stale or replayed requests	PASS
Schema	Require valid event structure	PASS
Idempotency	Prevent duplicate processing	PASS
Strategy State	Confirm strategy is allowed to publish	PASS
Instrument	Confirm canonical symbol exists	PASS

Intake Security

The gateway should be treated as a security boundary. Authentication, replay protection and rate controls belong on the server.

Control	Configuration	Status
Request Signing	HMAC / provider signature	ENABLED
Timestamp Validation	± 5 minutes	ENABLED
Idempotency	Event ID required	ENABLED
Rate Limiting	Provider-specific	ENABLED
Secret Storage	Server-side secret store	REQUIRED

Do not expose: API keys, webhook signing secrets, broker credentials, private connector tokens or raw authentication headers in frontend HTML or client-side JavaScript.

Copy Orchestrator

Coordinate an approved signal from intake through follower order lifecycle, with deterministic state transitions and reconciliation.

Copy Orchestrator Overview

The orchestrator coordinates already-validated instructions. It should not blindly mirror a broker order; it creates an auditable lifecycle for each follower request and preserves idempotency across retries.

Requests Today4,821

Executed4,674

In Flight23

Exceptions7

Copy Lifecycle

Canonical Signal

→

Eligibility

→

Risk / Allocation

→

Symbol Mapping

→

Copy Request

→

Broker Execution

→

Broker Result

→

Reconcile

State Model

State	Meaning	Next Transition
RECEIVED	Canonical signal accepted	ELIGIBILITY_CHECK
ELIGIBLE	Follower passed policy checks	QUEUED
QUEUED	Waiting for connector execution	SUBMITTED
SUBMITTED	Broker request sent	EXECUTED / REJECTED
EXECUTED	Broker acknowledged execution	RECONCILED
EXCEPTION	Unexpected or unresolved state	RECOVERY / REVIEW

Order Lifecycle

A copy request gets its own lifecycle ID so the system can distinguish a signal event, a follower request and the broker's resulting order/deal.

COPY-8F21-001 · Alpha / Follower A

XAUUSD · BUY · target 0.27 lot

14:32:11

Broker: MT5-A

RECONCILED

COPY-8F21-002 · Alpha / Follower B

XAUUSD · BUY · target 0.14 lot

14:32:12

Broker: API-B

EXECUTED

COPY-8F21-003 · Alpha / Follower C

EURUSD · CLOSE

14:31:48

Broker: MT5-C

RETRY

COPY-8F20-991 · Gold / Follower D

XAUUSD · SELL · blocked by policy

14:30:02

Broker: API-D

BLOCKED

Copy Requests

Each request carries the source event, follower account, policy version, mapped instrument and execution intent.

Request ID	Source Event	Follower	Intent	Status
COPY-8F21-001	evt_8F21A	Follower A	OPEN BUY 0.27	RECONCILED
COPY-8F21-002	evt_8F21A	Follower B	OPEN BUY 0.14	EXECUTED
COPY-8F21-003	evt_8F219	Follower C	CLOSE	RETRY
COPY-8F20-991	evt_8F217	Follower D	OPEN SELL	BLOCKED

Idempotency rule: the request ID should remain stable through retries. A timeout after submission must not automatically create a new broker order unless the connector can safely determine the prior request's outcome.

Retries & Recovery

Transient connector failures require controlled retries. Permanent policy or validation failures should not be retried as if they were network failures.

Failure	Classification	Action	Status
Network timeout	Transient	Retry with bounded backoff	RETRYABLE
Rate limit	Transient	Respect retry-after / backoff	RETRYABLE
Invalid volume	Permanent	Recalculate or reject	NO RETRY
Market closed	Conditional	Apply session policy	POLICY
Unknown broker result	Critical	Query broker before retry	RECONCILE

Execution Reconciliation

Reconciliation compares the intended copy state with the broker's observed state. This closes the loop between order submission and actual account state.

Request	Intent	Broker State	Match	Action
COPY-8F21-001	BUY 0.27	BUY 0.27	YES	Close lifecycle
COPY-8F21-002	BUY 0.14	BUY 0.14	YES	Close lifecycle
COPY-8F21-003	CLOSE	Position still open	NO	Investigate

14:32:12 · Broker acknowledgementCOPY-8F21-002 accepted by connector.

14:32:13 · Account syncFollower B position observed at broker.

14:32:13 · ReconciliationRequested volume and observed volume match.

Broker Connector Runtime

Manage the runtime layer that translates approved copy requests into broker-specific execution commands and returns normalized results.

Broker Connector Overview

The connector is the broker-facing execution boundary. MQLPro should send a normalized execution intent and receive a normalized result regardless of whether the underlying adapter uses MT5, a broker API, FIX or another supported transport.

Active Connectors18

Connected Accounts247

Healthy244

Exceptions3

Execution Boundary

Copy Request

→

Connector Adapter

→

Broker Transport

→

Broker

→

Normalized Result

→

Reconciliation

Normalized Execution Intent

{ "request_id": "COPY-8F21-001", "account_id": "acct_1024", "instrument": "XAUUSD", "side": "BUY", "quantity": 0.27, "order_type": "MARKET", "client_reference": "mqlpro_copy_8f21_001" }

Design rule: broker-specific credentials and transport details stay inside the connector service. The orchestrator should not need to know how an individual broker executes the request.

Connector Registry

Each adapter has its own capability profile, transport and health state.

MT5 Connector A

MetaTrader 5 · terminal/bridge adapter · 64 accounts

Latency 82 ms

Last heartbeat 14:32

CONNECTED

Broker API B

REST API · 31 accounts · market + pending orders

Latency 104 ms

Last heartbeat 14:32

CONNECTED

MT5 Connector C

MetaTrader 5 · bridge adapter · 87 accounts

Latency 96 ms

Last heartbeat 14:31

CONNECTED

Broker API D

REST API · 12 accounts · authentication renewal required

Latency —

Last heartbeat 13:57

ATTENTION

Runtime Workers

Workers consume execution jobs, communicate with broker adapters and publish normalized outcomes.

Worker	Queue	Throughput	Last Heartbeat	Status
worker-eu-01	execution.eu	142/min	14:32:12	RUNNING
worker-ap-02	execution.ap	118/min	14:32:11	RUNNING
worker-us-01	execution.us	96/min	14:32:10	RUNNING
worker-recovery-01	recovery	7/min	14:32:08	STANDBY

Connector Health

Health monitoring should cover transport availability, authentication, latency, execution acknowledgements and account synchronization.

Check	Expected	Observed	Status
Transport	Reachable	Reachable	PASS
Authentication	Valid	Valid	PASS
Heartbeat	< 30 sec	4 sec	PASS
Execution ACK	Received	Received	PASS
Account Sync	Current	Current	PASS
API credential renewal	Valid	Pending	ATTENTION

Connector Credentials

Credentials are represented only by safe metadata in this UI. Secret values must be managed by the backend or a dedicated secret-management system.

Connector	Credential Type	Last Rotated	Expiry	Status
MT5 Connector A	Terminal / bridge credential	01 Sep 2026	Not applicable	HEALTHY
Broker API B	OAuth / API token	15 Aug 2026	15 Nov 2026	HEALTHY
Broker API D	API token	01 Jun 2026	20 Sep 2026	RENEW

Security boundary: never place broker passwords, API secrets, private keys or access tokens in frontend source, localStorage or URL parameters.

Account Sync & Reconciliation

Compare intended copy state with broker-observed account state and resolve differences before they become persistent drift.

Account Sync Overview

Synchronization closes the loop between MQLPro's internal ledger and the real state reported by connected broker accounts.

Accounts Monitored247

Positions Synced1,284

Matched1,276

Exceptions8

Synchronization Flow

Copy Intent

→

Broker Execution

→

Broker State

→

Account Snapshot

→

Compare

→

Reconcile

→

Audit

Reconciliation Principles

Principle	Purpose	Result
Source of truth	Broker state is observed independently	Current account snapshot
Idempotency	Repeated sync must not duplicate actions	Stable state
Drift detection	Find intent/state differences	Exception generated
Safe recovery	Do not blindly force an order	Policy-based action

Connected Accounts

Account health and last observed snapshot for connected follower accounts.

Follower A · MT5-A

acct_1024 · Equity $10,842 · 4 open positions

14:32:14

Snapshot age 2 sec

SYNCED

Follower B · API-B

acct_1138 · Equity $7,214 · 2 open positions

14:32:13

Snapshot age 3 sec

SYNCED

Follower C · MT5-C

acct_1202 · Equity $15,901 · 7 open positions

14:32:12

Snapshot age 4 sec

SYNCED

Follower D · API-D

acct_1320 · Last broker snapshot incomplete

14:28:57

Snapshot age 3m 17s

STALE

Position Reconciliation

Compare expected follower positions with broker-observed positions after execution.

Account	Symbol	Expected	Observed	Match
Follower A	XAUUSD	BUY 0.27	BUY 0.27	MATCH
Follower B	XAUUSD	BUY 0.14	BUY 0.14	MATCH
Follower C	EURUSD	FLAT	BUY 0.10	DRIFT
Follower D	US500	BUY 0.05	UNKNOWN	STALE

Drift handling: a mismatch should first create an exception and trigger a fresh broker query. Automatic corrective trading should require an explicit, policy-approved recovery path.

Order Reconciliation

Order-level checks link MQLPro request IDs to broker order/deal identifiers.

Copy Request	Broker Ref	Requested	Observed	Status
COPY-8F21-001	MT5 #7812401	BUY 0.27	BUY 0.27	MATCH
COPY-8F21-002	API-B #99218	BUY 0.14	BUY 0.14	MATCH
COPY-8F21-003	Pending lookup	CLOSE	Position open	DRIFT
COPY-8F20-991	None	BUY 0.05	Blocked	EXPECTED

Sync Exceptions

Exceptions require deterministic handling rather than silent correction.

Exception	Account	Cause	Recommended State	Status
EXC-2031	Follower C	Unexpected EURUSD position	Investigate	OPEN
EXC-2029	Follower D	Stale account snapshot	Refresh	OPEN
EXC-2024	Follower A	Delayed broker acknowledgement	Re-query	REVIEW

Observability & Audit Center

Monitor the copytrade pipeline, investigate incidents, and maintain an immutable operational trail from signal intake to broker reconciliation.

Observability Overview

A cross-layer operational view of MQLPro. Metrics here describe system state and processing health, not trading performance.

Pipeline Events / min486

Successful Actions99.72%

Open Incidents3

Audit Events Today18,742

End-to-End Health

Signal Intake

Webhook validation, authentication and deduplication

82 events/min

Latency 21 ms

HEALTHY

Copy Orchestrator

Eligibility, allocation and request lifecycle

164 req/min

Latency 38 ms

HEALTHY

Broker Connectors

18 adapters / 247 connected accounts

217 req/min

Latency 91 ms

ATTENTION

Account Reconciliation

Position and order state comparison

1,284 positions

8 exceptions

ATTENTION

Pipeline Health

Monitor processing stages independently so a failure in one layer does not become an invisible failure across the whole system.

Stage	Throughput	Latency	Error Rate	Status
Signal Intake	82/min	21 ms	0.08%	HEALTHY
Signal Engine	82/min	14 ms	0.02%	HEALTHY
Risk Engine	79/min	18 ms	0.11%	HEALTHY
Execution Queue	164/min	7 ms	0.03%	HEALTHY
Broker Connector	157/min	91 ms	0.42%	WATCH
Reconciliation	1,284 snapshots	4 sec	0.62%	WATCH

Event Log

Operational events are correlated by event ID, request ID, account ID and connector ID.

2026-09-16 14:32:14 INFO evt_8F21A COPY-8F21-001 reconciliation.match 2026-09-16 14:32:13 INFO evt_8F21A COPY-8F21-002 broker.execution_ack 2026-09-16 14:32:12 INFO evt_8F21A COPY-8F21-002 connector.submit 2026-09-16 14:32:11 INFO evt_8F21A COPY-8F21-001 execution.queued 2026-09-16 14:32:10 INFO evt_8F21A — risk.approved 2026-09-16 14:32:09 INFO evt_8F21A — signal.normalized 2026-09-16 14:32:08 INFO evt_8F21A — intake.accepted 2026-09-16 14:31:49 WARN evt_8F219 COPY-8F21-003 broker.result.timeout 2026-09-16 14:31:48 INFO evt_8F219 COPY-8F21-003 retry.scheduled

Incident Center

Incidents group related failures so operators investigate the root cause rather than treating every retry as a separate problem.

INC-1042 · API-D authentication renewal

Connector: Broker API D · first detected 13:57

17 min

3 accounts

OPEN

INC-1041 · Position drift

Follower C · EURUSD unexpected open position

18 min

1 account

OPEN

INC-1040 · Broker timeout burst

Connector C · 7 requests affected

22 min

7 requests

INVESTIGATING

Audit Trail

Audit records should answer who or what performed an action, what changed, when it happened, and which object was affected.

Time	Actor	Object	Action	Result
14:32:14	system/reconciler	COPY-8F21-001	RECONCILE	MATCH
14:32:12	connector/mt5-a	COPY-8F21-001	EXECUTE	ACK
14:32:10	risk-engine	evt_8F21A	APPROVE	PASS
14:32:08	intake-gateway	evt_8F21A	ACCEPT	VALID
14:28:57	system/sync	acct_1320	SNAPSHOT	STALE

14:32:08 · Signal acceptedGateway assigned correlation ID evt_8F21A.

14:32:10 · Risk approvedPolicy evaluation produced an approved copy intent.

14:32:12 · Broker acknowledgedConnector returned a broker reference.

14:32:14 · ReconciledObserved broker state matched intended state.

Audit rule: audit history should be append-only in production. Administrative corrections should create a new audit event instead of silently modifying the historical record.

Security & Access Control

Control identities, permissions, sessions and sensitive operational actions across the MQLPro platform.

Security Overview

Security boundaries are separated from trading logic. Authentication establishes identity; authorization determines which operations that identity may perform.

Active Users1,284

Active Sessions417

API Credentials63

Open Security Alerts2

Security Layers

Identity & Authentication

1,284 users

0.12% failures

HEALTHY

Authorization

Role and permission checks for dashboard and API actions

42 policies

100% enforced

ACTIVE

Credential Security

Broker secrets and API credentials kept outside frontend state

63 credentials

2 renewals

REVIEW

Privileged Actions

Reset, disable, rotate, reconnect and recovery operations

18 today

100% audited

AUDITED

Production rule: the frontend is not a security boundary. Every privileged operation must be authorized again by the backend, even if the UI hides the corresponding button.

Roles & Permissions

Use least privilege: an identity receives only the permissions required for its operational responsibilities.

Role	Users	Core Permissions	Privileged Actions	Status
Platform Admin	4	All operational views	Connector, access, recovery	PRIVILEGED
Risk Operator	8	Risk policies, exceptions	Approve policy changes	ACTIVE
Support	17	User/account diagnostics	None	ACTIVE
Signal Provider	63	Own signal management	Own signal only	ACTIVE
Follower	1,192	Own account/subscriptions	None	ACTIVE

platform.connector.read platform.connector.manage account.reconcile.read account.reconcile.recover risk.policy.read risk.policy.manage security.session.revoke security.credential.rotate

Session Security

Sessions should be short-lived where appropriate, revocable server-side and bound to an authenticated identity.

Session	Role	Last Activity	Device	Status
sess_7A91	Platform Admin	14:32:18	Chrome / Windows	ACTIVE
sess_8B22	Risk Operator	14:31:49	Chrome / macOS	ACTIVE
sess_19F2	Support	12:08:21	Firefox / Linux	IDLE
sess_0A17	Unknown	09:17:02	Unrecognized device	REVOKED

API Access

API credentials should be scoped, rotated and revocable. Secret material is intentionally never rendered here.

connector-api-prod

Broker connector service · execution scope

Last used 14:32

Expires 2026-11-15

VALID

reconciler-prod

Account snapshots · read + reconciliation scope

Last used 14:32

Expires 2027-01-10

VALID

legacy-import

Historical migration · no live execution scope

Last used 2026-08-12

Expired

DISABLE

Sensitive Actions

High-impact actions should require explicit authorization, server-side policy checks and an audit record.

Action	Required Permission	Extra Control	Audit	Status
Rotate broker credential	security.credential.rotate	Re-authentication	Required	ENFORCED
Reconnect connector	platform.connector.manage	Confirmation	Required	ENFORCED
Manual reconciliation recovery	account.reconcile.recover	Reason + confirmation	Required	ENFORCED
Change risk policy	risk.policy.manage	Admin approval	Required	ENFORCED
Revoke session	security.session.revoke	None	Required	ENFORCED

Defense in depth: hiding a control in the UI does not protect the API. Authorization must be enforced at the service boundary for every request.

Production Readiness & Deployment

Validate the platform before production deployment with explicit release gates, dependency checks, rollback readiness and operational sign-off.

Production Readiness Overview

This control layer separates “the UI works” from “the system is safe to operate in production.” Every critical dependency must have an explicit state.

Readiness Checks28 / 30

Critical Blockers0

Warnings2

Rollback ReadyYES

Release Gates

Application & Routing

All dashboard routes resolve and protected pages remain access-controlled.

100%

0 blockers

PASS

Trading Pipeline

Signal → risk → queue → connector → reconciliation path is defined.

100%

0 blockers

PASS

Security Controls

Authentication, authorization, credential and audit boundaries documented.

93%

2 warnings

REVIEW

Operational Recovery

Incident, reconciliation and rollback procedures are represented.

92%

2 warnings

REVIEW

Important: a passing frontend prototype is not evidence that live trading is production-safe. Real broker credentials, backend authorization, durable storage, monitoring and tested recovery procedures must exist outside this HTML prototype.

Readiness Checks

A production release should fail closed when a critical dependency is unavailable or an essential safety control has not been verified.

Check	Area	Evidence	Gate	Status
Frontend route integrity	Application	Dashboard navigation	Required	PASS
Authentication & session policy	Security	Security control definition	Required	PASS
Server-side authorization	Security	Permission model	Critical	VERIFY BACKEND
Credential secret storage	Broker	Secret manager integration	Critical	VERIFY
Idempotent execution	Execution	Request ID / deduplication	Critical	DEFINED
Broker reconciliation	Operations	Expected vs observed state	Critical	DEFINED
Backup & restore test	Infrastructure	Restore evidence	Required	PENDING
Incident response test	Operations	Game-day record	Required	PENDING

Release Control

Production deployment should be versioned, traceable and reversible. No direct “deploy now” action is implied by this prototype.

Current Release · mqlpro-web 0.29.0

Baseline: STEP 29 · Security & Access Control

2026-09-16

Build verified

CURRENT

Candidate Release · mqlpro-web 0.30.0

Includes Production Readiness & Deployment control layer

Pending

Pre-production

CANDIDATE

Release Freeze

Freeze live execution changes during an active incident unless emergency procedure is invoked.

Policy

Incident linked

ENABLED

Rollback Readiness

Rollback is a controlled restoration to a known-good application version. It must not be confused with reversing a financial trade.

Control	Current State	Required Evidence	Status
Previous known-good build	0.29.0	Immutable artifact	READY
Database migration compatibility	Backward compatible	Migration test	VERIFY
Configuration snapshot	Versioned	Restore test	READY
Connector compatibility	Tracked	Adapter version matrix	READY
Operator procedure	Documented	Game-day rehearsal	PENDING

Separation of concerns: application rollback restores software state. It does not automatically undo broker-side executions or close positions. Those are separate operational workflows requiring reconciliation.

Production Sign-off

Final release approval should be explicit and attributable. The prototype records the structure of the sign-off, not a real production authorization.

Owner	Area	Evidence	Decision	Status
Engineering	Application	Build & route checks	Approve	RECORDED
Security	Access & secrets	Backend verification	Pending	PENDING
Operations	Recovery	Incident rehearsal	Pending	PENDING
Trading Operations	Execution	Connector & reconciliation test	Pending	PENDING

Release gate: all critical backend, credential, recovery and broker-integration checks must be independently verified before any real-money deployment.

Infrastructure & Service Health

Monitor the runtime dependencies that keep the MQLPro trading pipeline available, responsive and recoverable.

Infrastructure Overview

Infrastructure health is separate from trading logic. A healthy service does not imply a successful trade; it means the dependency is available to perform its defined role.

Services Healthy14 / 15

API Availability99.98%

Queue Depth12

Recovery Readiness94%

Critical Dependencies

API Gateway

Authentication, routing and inbound service boundary

12 ms

99.99%

HEALTHY

Application Services

Signal, risk, orchestration and account services

28 ms

99.98%

HEALTHY

Message Queue

Durable execution and event processing

12 pending

0 stuck

HEALTHY

Database

Users, subscriptions, ledger, configuration and audit metadata

18 ms

99.99%

HEALTHY

Secrets / Configuration

Runtime credentials and environment configuration

Rotation due

2 items

REVIEW

Operational boundary: infrastructure monitoring detects dependency failures. It should not silently retry financial actions without the execution policy and idempotency controls defined by the trading pipeline.

Service Health

Each service has an independent health state and dependency relationship.

Service	Instance	Latency	Error Rate	Status
Signal Intake	3 / 3	21 ms	0.08%	HEALTHY
Signal Engine	3 / 3	14 ms	0.02%	HEALTHY
Risk Engine	3 / 3	18 ms	0.11%	HEALTHY
Copy Orchestrator	4 / 4	38 ms	0.03%	HEALTHY
Connector Runtime	12 / 13	91 ms	0.42%	DEGRADED
Reconciliation	3 / 3	4 sec	0.62%	WATCH

Database Health

Database state supports operational records, configuration, subscriptions and audit metadata. Financial execution state should remain consistent with the broker reconciliation model.

Primary Database

Read/write workload · application state

18 ms

Healthy

ONLINE

Read Replica

Read workload · reporting and dashboard queries

24 ms

Lag 0.4 sec

ONLINE

Backup Snapshot

Latest verified snapshot

02:00 UTC

Age 12h

AVAILABLE

Restore Test

Last complete recovery rehearsal

2026-09-02

14 min

RETEST

Queue Health

Queues isolate asynchronous work and provide durable request state. Every financial execution message should have an idempotency key or equivalent deduplication mechanism.

Queue	Depth	Oldest	Retry	Status
signal-events	0	—	0	HEALTHY
execution-requests	7	1.8 sec	1	HEALTHY
broker-results	3	0.9 sec	0	HEALTHY
reconciliation	2	2.1 sec	1	HEALTHY
dead-letter	0	—	0	EMPTY

Recovery Readiness

Recovery controls restore service availability while preserving the integrity of execution and reconciliation records.

Control	Last Test	Target	Evidence	Status
Service restart	2026-09-15	< 2 min	Runbook #SR-12	PASS
Database restore	2026-09-02	< 30 min	Restore #DB-44	RETEST
Queue replay	2026-09-10	No duplicates	Replay #Q-19	PASS
Connector failover	2026-09-11	Controlled	Failover #CX-07	PASS
Audit continuity	2026-09-12	No gaps	Audit #AU-31	PASS

Recovery distinction: restoring infrastructure does not authorize new trades, cancel broker orders, or close positions. After recovery, reconciliation must establish the actual broker state before normal execution resumes.

Disaster Recovery & Business Continuity

Define how MQLPro continues operating, contains failures and restores service without losing execution or audit integrity.

Recovery Overview

Disaster recovery is broader than restarting servers. The objective is to restore critical services while preserving durable execution state, account reconciliation and audit continuity.

Critical Services15

Recovery Plans12 / 12

Last Full Drill2026-09-02

Continuity Readiness94%

Recovery Domains

Application Services

Restore application instances, routing and configuration.

Target < 10 min

Last 6 min

READY

Data Layer

Restore durable data and validate consistency before reopening writes.

Target < 30 min

Last 14 min

READY

Trading Pipeline

Rebuild queues and processing state without duplicating execution requests.

Target < 15 min

Last 11 min

READY

Broker Connectivity

Restore connectors, then compare broker state with internal state.

Target < 20 min

Last 17 min

REVIEW

Core rule: after a disaster, MQLPro should recover into a controlled state. New execution should remain paused until identity, queues, connector health and broker reconciliation have been verified.

RTO / RPO

Recovery Time Objective (RTO) describes the target time to restore a service. Recovery Point Objective (RPO) describes the maximum acceptable amount of data loss for the defined workload.

Component	RTO Target	RPO Target	Current Evidence	Status
API / Dashboard	< 10 min	< 5 min	Restore test 6 min	PASS
Operational Database	< 30 min	< 15 min	Restore test 14 min	PASS
Execution Queue	< 15 min	0 lost requests	Replay test	PASS
Audit Records	< 30 min	0 gaps	Continuity test	PASS
Broker State	< 20 min	Reconcile before resume	Connector test	REVIEW

Do not equate RPO with “number of trades lost.” For financial execution, the system must reconcile actual broker state rather than assume an internal event log is the authoritative source of open positions.

Failure Scenarios

Each scenario has a containment action, recovery path and explicit condition for resuming normal execution.

Scenario	Immediate Response	Recovery	Resume Condition	Status
Application outage	Fail traffic / preserve state	Restore instances	Health checks pass	DEFINED
Database failure	Stop writes	Restore snapshot / replica	Consistency verified	DEFINED
Queue failure	Pause execution consumers	Recover durable queue	Deduplication verified	DEFINED
Connector outage	Pause affected execution path	Reconnect / fail over	Broker state reconciled	DEFINED
Credential compromise	Revoke credential	Rotate and re-authenticate	Access audit complete	DEFINED
Regional infrastructure loss	Activate recovery environment	Restore critical services	Full readiness gate	REHEARSE

Business Continuity

Continuity defines which functions remain available during degraded operation and which functions are deliberately suspended.

Read-only Dashboard

Users can inspect known internal state while writes are restricted.

Priority P1

Degraded mode

AVAILABLE

Signal Intake

Can accept events only when durable storage and downstream controls are healthy.

Priority P1

Conditional

GATED

New Trade Execution

Must remain paused when broker state or execution idempotency cannot be verified.

Priority P0

Fail-closed

CONTROLLED

Reconciliation

Used to establish actual broker state after a connectivity or data incident.

Priority P0

Recovery path

REQUIRED

Audit Trail

Must remain durable across recovery and preserve operational traceability.

Priority P0

Continuous

REQUIRED

Recovery Drills

Recovery procedures are only meaningful when rehearsed. Drill results should capture duration, evidence, failures and corrective actions.

Drill	Date	Duration	Result	Follow-up
Database Restore	2026-09-02	14 min	Successful	Retest quarterly
Queue Replay	2026-09-10	11 min	Successful	Keep dedupe test
Connector Failover	2026-09-11	17 min	Successful	Test regional failover
Audit Continuity	2026-09-12	8 min	Successful	Verify retention
Regional Recovery	Pending	—	Not tested	Schedule rehearsal

Incident Management

Coordinate detection, containment, investigation, recovery and post-incident review without confusing service recovery with trading-state recovery.

Operational Incident Overview

An incident is an operational event that can affect availability, data integrity, security or trading execution. Severity determines the response path, not the blame assigned to an individual.

Open Incidents1

Critical0

Last Major Incident18 days ago

Runbooks Ready18 / 18

Operational Domains

Application Availability

Routing, frontend and backend service availability.

Severity S2

On-call

MONITORED

Data Integrity

Unexpected divergence, missing records or inconsistent state.

Severity S1

Immediate

MONITORED

Trading Execution

Unexpected order state, connector outage or execution mismatch.

Severity S0

Immediate

HIGH PRIORITY

Security

Credential compromise, unauthorized access or suspicious activity.

Severity S0

Immediate

HIGH PRIORITY

Fail-safe principle: if an incident can make the system's internal execution state unreliable, affected trading actions should be paused until the broker state and internal state can be reconciled.

Active Incidents

Current operational events and their containment state.

INC-2026-014 · Connector latency degradation

Affected scope: one connector runtime · Detection: automated latency alert · No confirmed duplicate execution.

SEV-2

Investigating

OPEN

No other active critical incidents

Security, database and queue health currently within defined thresholds.

—

CLEAR

Operational Runbooks

Runbooks provide repeatable response steps. Production procedures should live in version-controlled operational documentation and require appropriate authorization.

Runbook	Trigger	Primary Action	Resume Gate	Status
RB-01 Application Outage	5xx / availability	Failover / restart	Health checks	READY
RB-02 Database Recovery	DB unavailable	Protect writes / restore	Consistency check	READY
RB-03 Queue Recovery	Queue stalled	Pause consumers / recover	Deduplication check	READY
RB-04 Connector Failure	Broker link loss	Pause affected path	Broker reconciliation	READY
RB-05 Security Incident	Credential anomaly	Revoke / contain	Access review	READY
RB-06 Data Divergence	State mismatch	Freeze affected actions	Reconciliation complete	REVIEW

Incident Timeline

Timeline entries establish what happened and when. They should be append-only and attributable in a production audit system.

Time	Event	Actor	Evidence	State
22:14:02	Latency threshold exceeded	Monitoring	ALERT-9182	DETECTED
22:14:18	Connector path marked degraded	Automation	HEALTH-447	CONTAINED
22:15:01	Affected execution path paused	Policy	POL-EXEC-04	SAFE
22:17:42	Connector diagnostics started	Operator	RUN-2231	INVESTIGATING
Pending	Broker reconciliation	Operations	—	PENDING

Post-Incident Review

The review focuses on system conditions, detection quality, recovery time and preventive controls. The objective is learning and risk reduction.

Review Item	Evidence	Owner	State
Root cause / contributing factors	Logs + metrics + change history	Engineering	REQUIRED
Customer / account impact	Scope and affected accounts	Operations	REQUIRED
Trading-state impact	Broker vs internal reconciliation	Trading Ops	REQUIRED
Detection / response quality	Alert and incident timeline	SRE	REQUIRED
Corrective actions	Tracked remediation tasks	Owner assigned	REQUIRED

Important: an incident review should not declare an incident “resolved” merely because the application is online. Resolution includes confirming that affected financial execution state is understood and reconciled.

Monitoring, Alerting & SLO

Turn system telemetry into operational signals with defined thresholds, service objectives and actionable alerts.

Monitoring Overview

Monitoring provides evidence about system behavior. It does not replace authorization, execution controls or broker reconciliation.

Services Monitored15 / 15

Active Alerts2

SLOs Within Target7 / 8

Telemetry Ingest99.97%

Key Signals

API Availability

Successful requests across public and authenticated endpoints.

99.99%

Target 99.90%

HEALTHY

Execution Queue Age

Age of the oldest pending execution request.

1.8 sec

Alert > 10 sec

NORMAL

Connector Latency

Round-trip latency for broker connector operations.

91 ms

Alert > 75 ms

ALERT

Reconciliation Lag

Time between broker observation and internal reconciliation.

4 sec

Target < 10 sec

NORMAL

Alerting principle: an alert should correspond to an actionable condition. High-volume informational events should not be treated as incidents merely because they are visible.

System Metrics

Core metrics used to detect degradation across the application and trading pipeline.

Metric	Current	Target	Window	Status
HTTP 5xx rate	0.08%	< 0.50%	5 min	NORMAL
API p95 latency	142 ms	< 300 ms	5 min	NORMAL
Queue depth	12	< 100	1 min	NORMAL
Connector latency	91 ms	< 75 ms	5 min	DEGRADED
Database connections	42 / 200	< 160	1 min	NORMAL
Reconciliation lag	4 sec	< 10 sec	5 min	NORMAL
Audit ingest delay	0.7 sec	< 5 sec	5 min	NORMAL

Alert Rules

Alerts are evaluated against thresholds and routed to the appropriate operational owner.

AL-001 · Connector latency

Trigger when p95 connector latency exceeds 75 ms for 5 minutes.

SEV-2

Trading Ops

ACTIVE

AL-002 · Queue backlog

Trigger when execution queue exceeds 100 pending requests for 2 minutes.

SEV-1

Engineering

ARMED

AL-003 · Reconciliation divergence

Trigger when broker and internal state remain inconsistent beyond defined tolerance.

SEV-0

Trading Ops

ARMED

AL-004 · Authentication anomaly

Trigger on unusual login or credential activity according to security policy.

SEV-0

Security

ARMED

SLO / Error Budget

Service Level Objectives define reliability targets over a measurement period. Error budget represents the allowed unreliability before reliability work takes priority.

API Availability

Monthly objective: 99.90%

99.99%

Budget 92%

WITHIN SLO

Execution Queue Processing

Requests processed within defined latency objective.

99.96%

Budget 88%

WITHIN SLO

Reconciliation Freshness

Broker state observed and reconciled within target window.

99.71%

Budget 74%

WATCH

Connector Availability

Connector service available for its defined operational window.

99.42%

Budget 61%

WATCH

Governance: an exhausted error budget should trigger reliability review. It should not be used as an automatic instruction to increase trading activity or take financial risk.

Telemetry Pipeline

Telemetry should preserve enough context to investigate failures while respecting access controls and sensitive-data policies.

Source	Type	Retention	Ingest	Status
Application Services	Logs / Metrics	30 days	99.99%	HEALTHY
Execution Pipeline	Events / Metrics	90 days	99.98%	HEALTHY
Broker Connectors	Logs / State	90 days	99.95%	WATCH
Security Events	Audit / Alerts	365 days	99.99%	HEALTHY
Infrastructure	Metrics	30 days	99.97%	HEALTHY

Privacy boundary: telemetry should avoid unnecessary secrets or credentials. Production logs must use redaction and access controls appropriate to the data they contain.

Audit, Compliance & Governance

Establish traceability, controlled access, change accountability and operational evidence across the MQLPro platform.

Governance Overview

Governance connects operational controls with evidence. Every sensitive action should have an accountable actor, a defined authorization path and an auditable record.

Audit Coverage99.98%

Privileged Users8

Policy Controls24 / 24

Open Findings2

Governance Domains

Audit Trail Integrity

Append-only operational evidence for authentication, configuration and execution events.

Coverage 99.98%

Continuous

HEALTHY

Access Governance

Role-based access, privileged actions and periodic access review.

8 privileged

Monthly review

CONTROLLED

Change Management

Production changes require traceability, approval and rollback evidence.

18 changes

30-day window

CONTROLLED

Compliance Findings

Open findings require owner, due date, evidence and closure verification.

2 open

Review weekly

REVIEW

Governance principle: a dashboard indicator is not evidence by itself. Production controls should retain durable records that can be independently reviewed.

Audit Trail

Audit records should answer who acted, what changed, when it happened, what authorization applied and what outcome resulted.

Event	Actor	Authorization	Timestamp	Result
Production configuration change	admin-02	CHG-2041	2026-09-16 18:42	SUCCESS
Connector credential rotation	ops-01	SEC-882	2026-09-16 17:11	SUCCESS
Execution policy update	trading-ops	POL-119	2026-09-16 15:33	SUCCESS
Privileged login	admin-04	MFA + role	2026-09-16 13:08	RECORDED
Failed authorization	user-173	Denied by policy	2026-09-16 11:49	DENIED

Access Governance

Access should follow least privilege, separation of duties and periodic review. High-impact operations should require explicit authorization.

Role	Users	Privileged Actions	Review	Status
Platform Admin	2	Configuration / user access	Monthly	REVIEWED
Trading Operations	3	Execution controls / reconciliation	Monthly	REVIEWED
Security	2	Credentials / security controls	Monthly	REVIEWED
Read-only Analyst	11	None	Quarterly	REVIEWED

Separation of duties: where practical, the person requesting a high-impact production change should not be the sole person approving and validating that same change.

Change Control

Changes affecting execution, risk, connectivity or security should be attributable and reversible. Emergency changes require retrospective review.

Change	Owner	Approval	Rollback	Status
API release v2.8.4	Engineering	CHG-2044	Verified	COMPLETE
Connector runtime patch	Platform	CHG-2043	Verified	COMPLETE
Risk policy threshold update	Trading Ops	CHG-2042	Pending test	REVIEW
Database maintenance	SRE	CHG-2040	Verified	COMPLETE
Emergency connector mitigation	Operations	Emergency	Post-review pending	FOLLOW-UP

Policy Controls

Policies define the boundaries within which the platform may operate. Technical enforcement should be paired with periodic review.

Authentication & Session Policy

MFA, session expiry and privileged login controls.

POL-AUTH-01

Monthly

ACTIVE

Execution Authorization Policy

Defines which actors and services may submit or control execution actions.

POL-EXEC-04

Monthly

ACTIVE

Data Retention Policy

Defines retention and access requirements for audit and operational records.

POL-DATA-02

Quarterly

ACTIVE

Incident Response Policy

Defines severity, escalation, containment and post-incident review requirements.

POL-INC-03

Quarterly

ACTIVE

Change Management Policy

Defines approval, testing, deployment and rollback requirements.

POL-CHG-05

Quarterly

ACTIVE

Data Governance & Retention

Define how MQLPro classifies, stores, protects, retains, exports and disposes of platform data across its lifecycle.

Data Governance Overview

Data governance establishes ownership, classification, retention and access rules so operational data remains useful, traceable and appropriately protected throughout its lifecycle.

Data Domains9

Retention Policies9 / 9

Classified Assets100%

Open Data Findings1

Primary Data Domains

Identity & Account Data

User identity, authentication and account-management records.

Restricted

Owner: IAM

CONTROLLED

Signal & Strategy Data

Signal metadata, strategy configuration and marketplace information.

Confidential

Owner: Product

CONTROLLED

Trading & Execution Data

Execution events, order state, reconciliation records and connector state.

Restricted

Owner: Trading Ops

CONTROLLED

Audit & Security Data

Authentication, authorization, configuration and security-event records.

Restricted

Owner: Security

CONTROLLED

Data governance principle: retention is not the same as indefinite storage. Each data class should have a documented purpose, owner, retention period and disposal or archival rule.

Data Classification

Classification determines the controls required for storage, access, export and disposal. Labels should be applied consistently across databases, files, logs and backups.

Class	Examples	Access	Export	Control
Public	Public marketplace descriptions	Open	Allowed	STANDARD
Internal	Operational documentation	Authenticated	Controlled	CONTROLLED
Confidential	Strategy metadata / commercial data	Role-based	Restricted	RESTRICTED
Restricted	Credentials / account / execution records	Least privilege	Approval required	HIGH CONTROL

Secret handling: credentials, API keys and similar authentication material should not be exposed through ordinary application views, exports or logs. Store secrets using an appropriate secret-management mechanism.

Data Lifecycle

Every major data domain should have a predictable lifecycle from collection through active use, archival and final disposal.

1. Collection

Capture only data required for a defined product, operational or compliance purpose.

Purpose-bound

Validation

CONTROLLED

2. Active Processing

Use data through authorized services and role-based access controls.

Role-based

Audit

CONTROLLED

3. Archival

Move records that are no longer operationally active but must be retained.

Encrypted

Retention

CONTROLLED

4. Disposal

Delete or securely dispose of data after its approved retention period and legal holds.

Verified

Evidence

GOVERNED

Lifecycle exception: a legal, regulatory or incident-related hold can suspend ordinary disposal. The hold itself should be recorded and have an accountable owner.

Retention Schedule

Illustrative retention controls for the MQLPro architecture. Final production periods must be aligned with applicable legal, contractual and business requirements.

Data Domain	Active Retention	Archive	Disposal Rule	Status
Authentication Events	90 days	365 days	Scheduled deletion	DEFINED
Audit Events	180 days	365 days	Policy-controlled	DEFINED
Execution Events	90 days	7 years*	Controlled archival	VERIFY
Application Logs	30 days	90 days	Automated deletion	DEFINED
Market Content	Active	As required	Owner decision	REVIEW
Backup Snapshots	30 days	180 days	Rotation policy	DEFINED

*Illustrative only: retention periods for trading, financial, tax or regulated records must be determined from the requirements applicable to the actual MQLPro operating entity and jurisdictions. The UI does not establish a legal retention requirement.

Data Access Governance

Access to sensitive data should be purpose-limited, role-based, logged and periodically reviewed.

Data	Primary Role	Secondary Role	Export	Review
User Identity	IAM	Support	Restricted	MONTHLY
Trading Execution	Trading Ops	Audit	Controlled	MONTHLY
Broker Credentials	Connector Service	Security	Prohibited	HIGH CONTROL
Strategy Protection Data	Strategy Owner	Platform Admin	Restricted	MONTHLY
Audit Records	Security / Audit	Compliance	Evidence workflow	QUARTERLY

BlackBox boundary: strategy-protection data may be required internally to execute or monitor a strategy, but public marketplace views should expose only the information intentionally designated for public consumption.

Release & Deployment Control

Control how application, connector, risk and infrastructure changes move from development into production with validation, approval and rollback evidence.

Release & Deployment Overview

Production changes should be traceable to a version, owner, approval path, validation result and recovery plan. High-impact trading changes require additional controls.

Production Versionv2.8.4

Deployments Today6

Release Gates12 / 12

Rollback Ready100%

Current Release State

Application API v2.8.4

Production release containing API and dashboard changes.

Approved

CHG-2044

LIVE

Connector Runtime v1.14.2

Broker connector runtime patch with verified rollback package.

Approved

CHG-2043

LIVE

Risk Policy v3.7

Threshold configuration pending final production validation.

Validation

CHG-2042

STAGED

Database Maintenance

Schema maintenance completed with backup verification.

Completed

CHG-2040

CLOSED

Deployment principle: deployment success means the software was delivered. It does not automatically mean the trading system is safe to resume. Post-deployment health checks and reconciliation remain separate gates.

Release Registry

A release record connects source version, change request, test evidence, approver and deployment result.

Release	Component	Owner	Approval	Status
v2.8.4	Application API	Engineering	CHG-2044	PRODUCTION
v1.14.2	Connector Runtime	Platform	CHG-2043	PRODUCTION
v3.7	Risk Policy	Trading Ops	CHG-2042	STAGED
v5.2.1	Dashboard UI	Frontend	CHG-2039	COMPLETE
v1.6.0	Audit Service	Security	CHG-2038	COMPLETE

Deployment Pipeline

Changes progress through controlled environments before production. Each stage produces evidence for the next gate.

1. Build & Package

Compile, dependency validation, artifact creation and integrity checks.

Automated

Artifact signed

PASSED

2. Automated Tests

Unit, integration, regression and security checks appropriate to the change.

Automated

1,842 checks

PASSED

3. Staging

Deploy candidate to staging and verify functional and operational behavior.

Controlled

Health checks

PASSED

4. Production Approval

Confirm change scope, risk, owner, rollback plan and authorization.

Human gate

CHG-2044

APPROVED

5. Production Deployment

Deploy using controlled rollout and monitor service health.

Controlled

Canary + rollout

COMPLETE

6. Post-Deploy Verification

Validate telemetry, execution pipeline and reconciliation state.

Operational

Resume gate

REQUIRED

Release Gates

Gates prevent a release from progressing when required evidence or controls are missing.

Gate	Requirement	Evidence	Owner	Status
Code Integrity	Artifact matches approved build	Hash / signature	Engineering	PASS
Automated Testing	Required test suite passes	CI report	Engineering	PASS
Security Review	No blocking security findings	Scan report	Security	PASS
Change Approval	Authorized production change	CHG record	Change Owner	PASS
Rollback Plan	Recovery artifact verified	Rollback test	Platform	PASS
Post-Deploy Health	Telemetry remains within thresholds	Monitoring	Operations	PENDING
Trading Resume	Reconciliation and risk checks pass	Resume record	Trading Ops	PENDING

Critical distinction: a successful software deployment should not bypass trading-specific controls. Connector health, account synchronization, risk state and broker reconciliation must be independently validated before automated execution is resumed.

Rollback Control

Rollback restores a previously validated software state when a release causes unacceptable degradation. It is not a substitute for incident investigation.

Application API v2.8.3

Previous production version retained as validated fallback.

Ready

Artifact verified

AVAILABLE

Connector Runtime v1.14.1

Previous connector runtime available for controlled restoration.

Ready

Artifact verified

AVAILABLE

Risk Policy v3.6

Previous policy snapshot available for authorized restoration.

Ready

Snapshot verified

AVAILABLE

Database Schema

Rollback depends on migration compatibility and verified backup restoration.

Conditional

Backup test

REVIEW

Rollback safety: before restoring a trading-related component, confirm the resulting state will not create duplicate execution, stale orders, mismatched account state or other reconciliation problems.

Trading Signals

Reliability

Popular among subscribers

Gold Strategy Pro ACTIVE

Performance

Trading Statistics

Strategy Information

Risk & Allocation

Recent Trading Activity

Copy Configuration

Ranking

Top Signals

How Ranking works

Risk context

Articles

Building a Robust Cross-Broker Copy Trading System

Latest Articles

Building a Robust Cross-Broker Copy Trading System

Understanding Drawdown Before Copying a Signal

Profit Factor vs Win Rate: Reading Signal Statistics

What an Expert Advisor Actually Does

Trading Gold: Understanding Volatility and Exposure

How Signal Rankings Should Be Interpreted

Building a Robust Cross-Broker Copy Trading System

1. Master signal

2. Normalization layer

3. Risk and allocation

4. Execution and reconciliation

5. Monitoring

Community

MQLPro Community

How should symbol mapping work across different brokers?

Join the discussion

Documentation

Welcome to MQLPro Documentation

Get Started

Getting Started

Signals

Copy Trading

Market

Ranking & Performance

Risk Management

Broker Connectors

API & Webhooks

Getting Started

Overview

Core workflow

Important concepts

Signal

Follower

Connector

Example event flow

Next steps

Login

Create an account

My Account

Recent Activity

Dashboard

Welcome back, MQLPro User

My Signal Subscriptions

Copy Trading Accounts

Quick Actions

Browse Signals

My Signal Subscriptions

Copy Trading Accounts

My Purchases

Account Settings

Subscribe to Signal

1. Choose a plan

2. Account

3. Payment method

Subscription Review

Purchase Product

1. License

2. Account

3. Payment

Purchase Review

Orders & Subscriptions

Copy Trading Accounts

Connect another follower account