The Copy Engine and Broker API Connections
The foundation of any futures copy trading setup is the connection between the copy engine and the broker APIs.
Each platform (Tradovate, NinjaTrader, Rithmic, TopstepX) exposes an API that allows software to monitor account activity, receive order events, and submit orders programmatically. The copy engine maintains persistent connections to both the leader account and each follower account through these APIs.
The leader connection:
- Monitors the leader account for order events in real time
- Receives fill confirmations, modification events, and cancellations
- Passes each event to the processing layer
The follower connections:
- Accept order submissions from the copy engine
- Return fill confirmations per account
- Report current account state (position, equity, margin)
The quality of these API connections determines execution speed and reliability. A copy engine that uses direct, persistent API connections produces faster and more consistent results than one that polls accounts on a fixed timer.
Processing a Leader Trade - Step by Step
When the leader executes a trade, the copy engine processes it through several steps before any follower order gets submitted.
Step 1 - event detection. The broker API fires an event when the leader's order is filled. The copy engine receives this event in real time and extracts the relevant details - instrument, direction, fill quantity, fill price, and any bracket parameters.
Step 2 - per-follower evaluation. For each configured follower account, the engine checks whether that account's risk filters permit the trade. Filters checked per account include active status, instrument whitelist, position-size cap, daily or weekly loss limit, and session window. If any filter fails, that account receives no order for this signal.
Step 3 - size calculation. For accounts that pass their filters, the engine sets the follower order size using that account's quantity multiplier. Each follower can be configured to trade a different contract size from the leader, set independently per account.
Step 4 - order submission. The engine submits an order to each follower's broker API. Because this happens via direct API calls rather than sequential processing, followers receive their orders as close together as broker API response times allow.
Step 5 - confirmation logging. Each fill confirmation comes back from the broker API per account. The engine logs fill details, including fill price and time, for each follower independently.
Handling Exits and Modifications
Copy trading covers more than entries. A complete implementation handles the full trade lifecycle.
Exits. When the leader closes a position (via manual close, stop-loss trigger, or take-profit), the copy engine captures the exit event and submits closing orders to each follower that has an open position from that entry.
Bracket modifications. If the leader adjusts a stop or take-profit after entry, the engine propagates the modification to each follower's open order.
This full lifecycle handling is what separates a production-grade copy engine from a basic signal forwarder. An entry-only implementation leaves followers with open positions when the leader exits or with stale brackets when the leader modifies them.
Per-Account Risk Filters in Practice
Per-account risk filters are what make copy trading practical for prop firm traders. Each funded account has different rules, and the copy engine needs to apply them independently.
An example setup with three accounts:
- Account A (Tradeify on Tradovate) - max 3 contracts, $500 daily loss limit, 8am to 3pm CT session window
- Account B (Apex on Rithmic) - max 5 contracts, $800 drawdown stop, no session restriction
- Account C (TopStep on TopstepX) - max 2 contracts, equity stop at $48,000, 9:30am to 4pm ET session window
When the leader trades a 4-contract entry, Account A receives a 3-contract order (capped), Account B receives a 4-contract order (within limit), and Account C receives a 2-contract order (capped). If Account A has already hit its daily loss limit, it receives no order at all while B and C proceed normally.
Each account's evaluation is independent. One account hitting a limit does not affect any other.
See the prop firm trade copier guide for a full breakdown of available risk filter settings.
Desktop vs Hosted - Where the Copy Engine Runs
The copy engine needs to run continuously during market hours. Where it runs determines how you manage it.
Desktop - Tradecopia Pro at $49.99/month. The copy engine runs as an application on your Windows or macOS machine. Your broker credentials and trade data stay local. If your machine is off or your connection drops, copying pauses.
Managed hosting - Tradecopia Pro+ Lite at $79.99/month. The copy engine runs in the cloud, accessible from any browser. You do not need to keep a local machine running. The engine runs continuously and maintains broker API connections independently of your local setup.
Dedicated VPS - Tradecopia Pro+ at $149.99/month. The copy engine runs on a dedicated cloud instance with a static IP, accessible from any browser. The right choice for traders who want a dedicated static IP and guaranteed isolated compute resources.
The copy engine is the same on all three plans. The difference is where it runs and how you access it. See full plan details.
