Skip to main content

Trade Copier Beta

Beta — live accounts can lose real funds

Trade Copier can be used with all supported account types, including live and prop-firm accounts, at your own risk. Beta status does not restrict the account type, but the copier is not a guaranteed risk control: copied, synchronized, repaired, or flattened positions can create real orders, fees, losses, rule violations, liquidation risk, or account closure.

Trade Copier observes a configured leader account and creates related actions for one or more follower accounts. It includes execution, order, fast-market, and position-oriented modes, plus symbol mapping, quantity conversion, retry handling, reconciliation holds, synchronization, repair, and flatten operations.

Start with LocalPaper until you understand the mapping, sizing, synchronization, repair, and recovery behavior. Using LocalPaper first is strongly recommended, not required.

Why The Feature Remains Beta​

Copy trading combines multiple independent systems:

  • leader account state
  • follower account identity and provider scope
  • symbol and contract mapping
  • quantity and multiplier conversion
  • order-type compatibility
  • partial fills and protective orders
  • provider latency and disconnect behavior
  • ambiguous submission outcomes

A successful leader order does not guarantee the same price, fill, state, or protection on a follower.

Controls You Must Not Treat As Enforcement Boundaries​

In the current Beta build:

  • The Copy ATM Strategies option is not a reliable boundary for whether protective or OCO metadata is propagated.
  • Account-based sizing and maximum-risk-per-account settings are not approved effective controls.
  • Maximum-slippage and order-timeout settings are not approved effective controls.
  • Daily-loss behavior is not certified for multiple scoped accounts on the same provider connection.

Do not rely on those settings to prevent an order or cap financial loss. Use provider-side limits, conservative sizing, and direct monitoring.

Effective Beta Safeguards​

The current engine includes safeguards for several failure classes:

  • stable client order identifiers for supported routes
  • provider-capability checks before some order operations
  • bounded retries
  • reconciliation holds after an unknown submission outcome
  • follower pause state
  • manual synchronization, repair, and flatten workflows
  • configured minimum and maximum copied quantity

These safeguards reduce some duplicate-order and divergence risks. They do not guarantee identical execution, prevent financial loss, or make unattended live use risk-free.

Before Using A Live Or Prop-Firm Account​

Before enabling a live, broker, or prop-firm account:

  1. Confirm copy trading is permitted by the provider, prop firm, account agreement, and laws that apply to you.
  2. Verify the exact leader, every follower, provider connection, environment, and account type.
  3. Confirm symbol mappings, contract multipliers, and copied quantities for every instrument.
  4. Use the smallest practical quantity and provider-side risk limits.
  5. Keep the provider's own account and order surface open for independent monitoring.
  6. Understand that synchronization and repair can submit market orders and that flatten can close positions.
  7. Stop the copier and reconcile every account immediately after a disconnect, rejection, unknown outcome, or unexpected position difference.

You are responsible for deciding whether the Beta is suitable for an account. HyperionX cannot guarantee prop-firm compliance, equal fills, loss limits, or recovery from provider and network failures.

  1. Use a LocalPaper leader and LocalPaper followers.
  2. Use one follower at first.
  3. Map every symbol explicitly and verify contract multipliers.
  4. Test Market, Limit, Stop, cancel, change, partial-close, and OCO scenarios separately.
  5. Disconnect and reconnect each side during a test.
  6. Verify unknown outcomes produce a hold instead of a blind resubmission.
  7. Compare leader and follower positions, working orders, and realized PnL after every scenario.
  8. Test repair and flatten commands with no external capital at risk.
  9. Move to another supported account type only after you understand the observed behavior and accept the live-account risks.

Reconciliation Holds​

When HyperionX cannot determine whether a provider accepted an order, the copier can pause the affected follower and wait for authoritative reconciliation. Do not clear, bypass, or duplicate the order from another surface until the provider account has been checked.

See Connection Recovery for the general unknown-outcome procedure.

Current Beta Limitations​

  • All supported account types are available, but none is made risk-free by the copier.
  • Unattended Broker-account copying can continue to create exposure while the desktop or a provider is in an unexpected state.
  • Marketplace-sourced copier execution is not part of the supported public workflow.
  • Identical prices, fills, order states, or timing across providers are not guaranteed.
  • Every protective order is not guaranteed to remain synchronized.
  • Beta UI fields must not be used as the only loss limit.

Release status changes will be published in Feature And Provider Status.