Axivor Bridge connects your trading accounts through a simple Sender and Receiver workflow.

Choose Sender on the account you trade and Receiver on each account you want to follow it. Open a position, set or modify Stop Loss and Take Profit, or close the trade on the Sender — Bridge reproduces the supported lifecycle on the connected Receivers.

One Sender can serve multiple Receivers, and every Receiver can use its own volume settings.

For a basic cTrader-to-cTrader setup, there is no journal configuration, preset or external service to configure: choose the roles, start the Sender first, start the Receivers and wait for READY.

One Sender. Multiple Receivers.

Bridge is designed for traders managing more than one account from the same native Windows computer or VPS.

Each Receiver operates independently with its own:

• trade mapping
• volume configuration
• processing state
• execution result

This allows the same source trade to be copied differently across different Receiver accounts.

Supported Trade Lifecycle

Version 1.0 supports:

• Market position open
• Initial Stop Loss and Take Profit
• Stop Loss and Take Profit modifications
• Full manual close

Bridge maintains persistent source-to-target mapping so later modifications and closes are applied to the correct Receiver position.

Completed actions remain mapped across normal restarts to protect against replay and duplicate execution.

Flexible Volume Handling

Each Receiver can be configured independently.

Same as Sender
Uses source and target contract information to preserve the intended economic volume across the connection.

Fixed Volume
Uses the configured target volume regardless of the Sender position size.

Multiplier
Scales the source volume by the configured multiplier.

Maximum Volume
Adds an optional safety ceiling. If the resolved volume exceeds a non-zero Maximum Volume, Bridge rejects the request rather than silently reducing the trade size.

This means one Sender can, for example, feed one Receiver using Same as Sender, another using Fixed Volume and another using a Multiplier.

Mixed-Platform Support

Bridge can also connect cTrader with a supported third-party desktop platform running on the same native Windows computer or VPS.

Mixed-platform setup requires the cTrader connector to select the Shared Journal created by the supported third-party platform. Automatic journal discovery is not included in Version 1.0.

The detailed manual provides step-by-step Windows instructions, including how to display hidden folders and locate the correct Shared Journal.

Local by Design

Bridge does not depend on an external trade-copying relay, synchronization executable or cloud copying service.

Communication and durable state are maintained locally on the Windows computer or VPS running the connected platforms.

The cBot declares:

AccessRights.None

Basic cTrader Setup

For a standard cTrader-to-cTrader connection:

1. Add Axivor Bridge to the sending and receiving accounts.
2. Set Role = Sender on the source account.
3. Leave the target instance as Receiver.
4. Keep the automatic cTrader Journal configuration.
5. Leave Supported Third-Party Journal (Mixed Platform) empty.
6. Use the same Copy Group.
7. Start the Sender first.
8. Start the Receiver or Receivers.
9. Wait for READY before trading.

No preset, external journal file or additional synchronization software is required for basic same-platform use.

Before Using Bridge Live

We strongly recommend completing a simple demo test first:

1. Open a minimum-size market position.
2. Verify the Receiver position.
3. Verify Stop Loss and Take Profit.
4. Modify one protection level.
5. Close the source position.
6. Verify the Receiver closes the mapped target.
7. Restart the Receiver and confirm that the completed trade is not replayed.

Version 1.0 Scope

Axivor Bridge Version 1.0 focuses on reliable market-position copying.

The following are not included in Version 1.0:

• Pending-order copying
• Partial-close copying
• cTrader Cloud
• Automatic universal broker-symbol mapping
• Automatic mixed-platform journal discovery
• Seamless Sender changes while managed trades remain open

Changing Sender is supported as a deliberate flat-account maintenance procedure and is explained in the manual.

Mixed-Platform Acknowledgement Visibility

When cTrader is the Sender and a supported third-party platform is the Receiver, platform file-access permissions may prevent cTrader from reading the Receiver's acknowledgement files.

The Receiver still processes the trade and records its execution result. Receiver-side execution records remain authoritative. This limitation affects Sender-side acknowledgement visibility, not the trade-copy lifecycle.

Documentation and Support

For detailed instructions, presets and support documentation please visit our company website.

Important Execution Information

Axivor Bridge is an execution utility, not a trading strategy or signal service.

Actual Receiver execution depends on platform, broker and symbol conditions including symbol availability, contract size, minimum and maximum volume, volume steps, price precision, stop-distance rules, trading sessions, spread, liquidity and slippage.

Bridge cannot guarantee execution price or timing and cannot override broker or platform restrictions.

Trading involves risk. Past performance does not guarantee future results.

Version 1.0 — cTrader Desktop