Product purpose
Copy a supported trade lifecycle across local accounts
Use one Sender and one or more independently configured Receivers across MT4, MT5 and cTrader Desktop while keeping platform and broker behavior visible.
Platform Connectivity CONNECT
AVAILABLE
Axivor Trade Copier
A local trade copier for MetaTrader 4, MetaTrader 5 and cTrader Desktop, designed for one Sender and independently configured Receivers.
Marketplace price$119per platform edition
MT5 — AvailableMT4 — AvailablecTrader — Available
Overview
Product overview
Axivor Trade Copier is a local multi-account trade copier for MetaTrader 4, MetaTrader 5 and cTrader Desktop. Copy supported market trades, Stop Loss and Take Profit changes and full closes across same-platform or mixed-platform account setups, with flexible Receiver volume control, persistent mapping and restart protection.
The product uses a documented Sender and Receiver workflow. Same-platform setups work locally without a separate relay service; mixed-platform relationships use a local Shared Journal on the same native Windows computer or VPS.
Product story
Purpose, problem and solution
Simple same-platform setup
Start without journal or filesystem configuration
For MT4-to-MT4, MT5-to-MT5 or cTrader-to-cTrader, leave the target as Receiver, set the source to Sender, use the same Copy Group, start the Sender first and confirm READY.
Mixed-platform workflow
Coordinate supported platforms through one local Shared Journal
All nine directed MT4, MT5 and cTrader Desktop combinations are supported. Mixed-platform routes require the documented one-time Shared Journal setup on the same native Windows computer or VPS.
Customer outcomes
Key benefits
Local coordination
Operate on one native Windows computer or VPS without an Axivor cloud relay service.
Independent Receiver control
One Sender can serve multiple Receivers, each with its own supported volume settings and execution outcome.
Persistent mapping and restart protection
Normal restarts preserve mapping and processing progress so completed copy events are not replayed.
Capabilities
Approved product capabilities
Supported trade lifecycle
- Market BUY and SELL copying Copy supported market-position opens from Sender to Receiver.
- Stop Loss and Take Profit synchronization Copy initial levels and later Stop Loss or Take Profit changes.
- Full and manual close copying Copy supported full closes across the active relationship.
Receiver control
- One Sender, multiple Receivers Configure several independent Receivers with the same Copy Group; practical capacity depends on the computer, terminals and brokers.
- Three volume modes Choose Same as Sender, Fixed Volume or Multiplier on each Receiver.
- Maximum Volume rejection ceiling Reject a copy that exceeds a configured non-zero Trade Copier ceiling rather than silently clamping it.
Mapping and resilience
- Explicit symbol mapping Map SOURCE=TARGET when broker symbol names differ.
- Restart protection Preserve source-target mapping and processing progress across a normal restart.
- Local Shared Journal Use documented local coordination for mixed-platform workflows without a separate relay service.
Workflow
How it works
-
1
Choose Sender and Receiver roles
Set the source account to Sender and each target account to Receiver.
-
2
Match the Copy Group
Use the same Copy Group on every participant in the relationship.
-
3
Start the Sender first
Wait for the Sender to become READY, then start each Receiver and confirm READY.
-
4
Validate the full lifecycle on demo
Test a minimum-size OPEN with SL/TP, MODIFY, full CLOSE and RESTART before live use.
Platform fit
Check your platform path
Implementation, customer support and marketplace availability are separate release decisions. Use the labels below to confirm the current platform and release state before planning setup.
Product view
Customer product views
Real product views from the approved customer release.
Customer success
From product fit to confident setup
Use the product page to decide fit, then follow the maintained documentation, platform-specific setup and support path.
Learn more
Understand scope and configuration
Review platform scope, configuration, reference and release information before installation.
Read documentationView setup
Prepare the first validated workflow
Follow the platform-specific installation and validation path before live operation.
View setupGet support
Resolve a blocked setup with context
Use troubleshooting first, then contact Support with platform, version and redacted diagnostics.
Open supportFAQ
Frequently asked questions
Which platforms are supported?
Axivor Trade Copier Version 1.0 is available for MetaTrader 4, MetaTrader 5 and cTrader Desktop. All nine directed same-platform and mixed-platform combinations are supported.
Do same-platform setups need a Shared Journal?
No. Normal MT4-to-MT4, MT5-to-MT5 and cTrader-to-cTrader Basic setup needs no preset, file selection or filesystem work.
Does Trade Copier generate trading signals?
No. Trade Copier copies the supported lifecycle from the Sender; it does not choose trades or market direction.
Will Receiver execution be identical?
No. Symbol availability, broker rules, volume normalization, prices, timing, spread, liquidity and slippage can produce different outcomes.
Where is mixed-platform setup documented?
Use the Axivor Trade Copier documentation on this website. MetaTrader users can also consult the published MQL5 mixed-platform setup guide.
Clear boundaries
What to understand before use
These boundaries are part of evaluating product fit. Detailed operating guidance remains in documentation.
No pending-order copying
Pending orders are not supported in Version 1.0.
No partial-close copying
Partial closes are not supported in Version 1.0.
No risk-based Receiver sizing
Risk-based Receiver sizing is not supported in Version 1.0.
No seamless Sender migration
Changing Sender requires a controlled reset while all affected accounts are flat.
No automatic mixed-platform journal discovery
Mixed-platform operation requires the documented local Shared Journal setup.
No universal automatic symbol mapping
Configure explicit symbol mappings when broker names differ.
No advanced recovery tooling
Preserve Runtime and journal files and follow documented support guidance when recovery is required.
No cTrader Cloud
Version 1.0 supports cTrader Desktop; cTrader Cloud is not supported.
Acknowledgement visibility on some mixed routes
Sender-side acknowledgement visibility on some mixed cTrader-to-MetaTrader routes is limited by platform file-access permissions. Receiver-side execution records remain authoritative. This does not prevent trade copying.
Related workflows
Explore the Axivor system
Each product solves a distinct operating problem. Explore another workflow only when it matches the next decision you need to make.
CONTROL
Need clearer risk decisions before execution?
Axivor Risk Calculator — Plan, size and review a manual trade before execution—using visible Entry, Stop Loss and Take Profit levels, percentage or fixed-cash risk, and broker-normalized volume.
Explore Axivor Risk CalculatorAUTOMATE
Need a defined rules-based automated workflow?
Axivor Liquidity Trend Bot — Run a defined, configurable strategy process on MT5 or cTrader, with methodology, operating filters and risk boundaries made clear before use.
Explore Axivor Liquidity Trend BotMarketplace-first
Choose the correct platform marketplace
MT4 and MT5 products use MQL5 Market. cTrader products use cTrader Store. A purchase link appears only after its destination is verified.
Risk disclaimer
Trading software does not remove market risk.
Trading involves risk. Axivor Trade Copier 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.
Need help?
Start with documentation. Escalate with context.
If the documented setup does not reach the expected state, prepare the platform, version and redacted diagnostic details before contacting Support.