Axivor Bridge MT4
- Утилиты
-
Aleksander Valentin
I am the founder of Axivor Systems, an independent trading-software brand focused on professional tools for risk control, platform connectivity and systematic automation. - Версия: 1.0
- Активации: 5
Axivor Bridge is a local multi-account trade-copying utility for MetaTrader 4 on
native Windows desktops and VPS environments. The same Expert Advisor can run as
Sender or Receiver. One Sender publishes supported trade lifecycle changes to
multiple independently configured Receivers without a separate relay program.
Bridge does not generate trading signals or choose trades. The trader controls
the source account; each Receiver applies its own configured volume policy and
remains subject to its broker and account conditions.
For normal MT4-to-MT4 use, setup is deliberately simple: attach Bridge to
both accounts, leave the target as Receiver, change the source to Sender and keep
the same Copy Group. No separate relay application is required.
Key Features
- Market BUY and SELL copying
- Initial Stop Loss and Take Profit copying
- Later Stop Loss and Take Profit changes
- Full/manual close copying
- One Sender with multiple independently configured Receivers
- Same as Sender, Fixed Volume and Multiplier sizing modes
- Optional hard Maximum Volume rejection ceiling
- Explicit Symbol Mapping for broker naming differences
- Persistent source-target mapping and restart protection
- Same-platform and supported mixed-platform desktop workflows
- Local Shared Journal architecture with no separate relay service
Basic MT4-to-MT4 Setup
1. Install and attach Axivor Bridge on the source and target MT4 accounts.
2. Leave the target account at the default Receiver Role.
3. On the source account set Role = Sender.
4. Keep copygroup1 on both sides or enter the same unique Copy Group.
5. Start the Sender first, then the Receiver.
6. Confirm both show READY.
7. Run a small demo lifecycle before live use.
No preset, file selection or filesystem work is needed for normal MT4-to-MT4 Basic setup.
What Version 1.0 Copies
Bridge copies market opens, initial Stop Loss and Take Profit, later Stop Loss and
Take Profit changes, and full manual closes. Each Receiver keeps persistent
source-target mapping and processing progress so a normal restart does not replay
completed trade-copy events.
Pending orders and partial closes are outside the Version 1.0 scope.
One Sender, Multiple Receivers
One Sender can serve multiple Receivers that use the same Copy Group. Each
Receiver can use independent volume settings and records its own execution
outcome. A rejection or failure on one Receiver does not mean the other
Receivers failed. Practical capacity depends on the computer, terminals, brokers
and number of accounts.
Volume Control
Same as Sender
Uses source and target contract metadata to preserve the source requested
economic volume, subject to the target platform and broker rules.
Fixed Volume
Uses the configured Receiver lots.
Multiplier
Scales the source volume by the configured Receiver multiplier.
Maximum Volume
Maximum Volume is not a fourth sizing mode. It is a hard Bridge rejection
ceiling. If the resolved Receiver volume exceeds a configured non-zero ceiling,
the copy is rejected rather than silently clamped. With Maximum Volume = 0, no
separate Bridge-level ceiling is applied; platform and broker limits remain
authoritative.
Mixed-Platform Support
Axivor Bridge also supports mixed-platform relationships with a supported
third-party desktop platform. Mixed-platform copying uses the local Shared
Journal and requires additional one-time setup. Detailed mixed-platform setup
instructions are provided in the Axivor Bridge MetaTrader 4 documentation and
MQL5 setup resources.
Automatic mixed-platform journal discovery is not supported. Mixed-platform
operation requires the documented local Shared Journal setup.
Symbol and Broker Notes
Receiver execution depends on symbol availability, broker minimum and maximum
volume, volume step, margin, market hours, stop levels and current execution
conditions. Broker symbol names may differ. Use explicit Symbol Mapping when
required, for example EURUSD=EURUSD.a.
Bridge does not provide universal automatic symbol mapping.
Restart Protection
Each Receiver persists its mapping and processing position. A normal restart
continues the existing relationship without replaying completed copy events. A
fresh relationship or deliberate reset is different from a normal restart.
Changing the Sender requires a controlled reset while all affected accounts are
flat; seamless live Sender migration is not supported.
Version 1.0 Scope — Not Supported
- Pending-order copying
- Partial-close copying
- Risk-based Receiver sizing
- Seamless live Sender migration
- Automatic mixed-platform journal discovery
- Universal automatic symbol mapping
- Advanced recovery tooling
- Cloud copy
Demo Before Live Use
Before live use:
1. Use demo accounts.
2. Verify the Copy Group on every participant.
3. Verify Symbol Mapping if broker names differ.
4. Verify each Receiver's volume behavior and Maximum Volume setting.
5. Test one minimum-size market OPEN with initial SL/TP.
6. Test a later SL/TP modification.
7. Test a full CLOSE.
8. Restart and confirm the completed trade does not replay.
Support and MQL5 Resources
The product description and Axivor Bridge MetaTrader 4 documentation provide the
required setup information. Support is available through MQL5 product comments
and MQL5 messaging. Additional setup guides may also be published on MQL5. When
requesting help, provide the visible status, Copy Group, symbol and approximate
UTC time. Do not provide passwords or account credentials.
Risk and Execution Note
Trading involves risk. Axivor Bridge cannot guarantee target fill price,
identical timing, broker acceptance or an identical execution outcome. Symbol
availability, contract metadata, volume rules, margin, precision, stop levels,
market hours, spread, liquidity, slippage and broker policy remain authoritative.
