Rithmic trade copier software is a low-latency futures order-routing application that listens to one master account and reproduces each approved order across up to 100 follower accounts. It connects through the Rithmic API, preserves order intent through entries and exits, and applies account-specific risk rules before any follower instruction is released.
One master order, account-aware follower sizing, measurable routing latency, and a single emergency flatten path.
Why This Rithmic Trade Copier Software Exists
Manual duplication breaks down when a combine trader manages many accounts. Entries arrive at different prices, partial fills diverge, brackets lose their parent-child relationship, and one disconnected session can leave an unmanaged position. This copier treats synchronization as an order-state problem rather than a button-replay problem. Every master event is normalized, assigned an idempotency key, checked against follower risk, and tracked until the follower reaches a known terminal or recoverable state.
The system supports market, limit, stop, stop-market, bracket, OCO, scale-in, scale-out, partial-fill, cancel, replace, and close-position workflows. It does not promise identical exchange fills; it preserves instructions and continuously reconciles quantities, working orders, stops, and targets against the state reported by Rithmic.
Core Features
| Feature | Description |
|---|---|
| Master-to-Follower Order Fan-Out | Repeated manual entry causes missed or late orders. A single normalized master event is dispatched concurrently to enabled follower accounts with per-account correlation IDs. |
| Bracket and OCO Synchronization | Detached stops and targets create unmanaged exposure. Parent, child, OCO, cancel, and replace relationships remain linked as fills and quantities change. |
| Partial-Fill Reconciliation | Follower fills rarely arrive in the same sequence. The state engine compares cumulative filled quantity and adjusts remaining exits without duplicating orders. |
| Contract Multipliers | Equal sizing is unsuitable across accounts with different limits. Each follower can use a fixed multiplier while maximum contracts and maximum position size remain hard caps. |
| Daily Loss and Account Controls | One account should not continue copying after its threshold is reached. Daily loss limits, enable switches, symbol permissions, and position caps are checked before dispatch. |
| Connection Recovery | A dropped session can hide working orders or open positions. Heartbeats, reconnect backoff, health checks, and post-reconnect snapshots rebuild authoritative account state. |
| Duplicate-Order Protection | Retries must not become second entries. Idempotency keys, master event sequencing, and follower execution records block duplicate submission. |
| Emergency Flatten | Operators need one deterministic response during a fault. The dashboard can cancel working orders, flatten selected or all enabled accounts, and record every acknowledgement. |
Low-Latency Routing Without Losing Order State
The routing core uses C# asynchronous programming for non-blocking API work and bounded TPL Dataflow pipelines for ordered fan-out, backpressure, and isolated follower failures. A master callback is never allowed to wait on 100 sequential submissions. Dispatch latency is timestamped at ingestion, risk approval, API submission, and acknowledgement so p50, p95, and worst-case values can be inspected instead of guessed.
The internal target is below 10 milliseconds when the host, network, entitlement, and API path permit it. That target excludes exchange matching and internet transit. Rithmic itself separates market-data and order-management infrastructure, so the copier measures only the portion it controls. Retries use capped exponential backoff and state queries; blind resubmission is prohibited.
Risk Controls for Combine and Prop Accounts
A Rithmic copy trader should fail closed when account state is uncertain. Before each follower order, the copier checks connection health, account enablement, current position, pending quantity, contract multiplier, maximum contracts, maximum position size, and daily loss status. These controls reflect the broader industry emphasis on pre-trade limits, system capacity, and electronic order-routing supervision described by the NFA's automated order-routing guidance.
{
"followerAccount": "SIM-042",
"enabled": true,
"contractMultiplier": 2,
"maxContracts": 6,
"maxPositionSize": 6,
"dailyLossLimit": 1200,
"flattenOnLimit": true
}
Dashboard and Operational Controls
The dark desktop dashboard shows master and follower connectivity, active positions, working orders, copy status, rejected instructions, reconnect attempts, and measured latency. Operators can filter by account, symbol, order ID, or severity; disable one follower without stopping the group; and run emergency flatten from a confirmation-protected control. Credentials are stored with .NET ProtectedData, while exported configuration files are encrypted and exclude plain-text secrets.
Use Cases
- Run one futures strategy across a large combine portfolio while enforcing different contract multipliers and hard caps for each account.
- Keep stop losses and profit targets synchronized after partial fills, scale-ins, scale-outs, manual cancels, or order replacements.
- Pause a failing follower account, reconcile its live state, and resume copying without resending already acknowledged orders.
- Measure whether routing delays come from the local copier, the API acknowledgement path, or a disconnected follower session.
How to Copy Futures Trades Using Rithmic Trade Copier Software
Download & Set Up the Project
Download, set up, and install Rithmic Trade Copier Software to get the project running. If you hit any difficulty, contact us here.
Connect Accounts
Open the dashboard, add the master Rithmic session, import follower accounts, and confirm green heartbeat and entitlement status for every enabled connection.
Set Copy and Risk Rules
Choose account multipliers, symbol permissions, maximum contracts, maximum position size, daily loss limits, and whether threshold breaches disable or flatten the account.
Start the Copier
Select Start Copier. The activity grid returns routed orders, acknowledgements, fills, errors, and per-stage latency while positions and brackets remain synchronized.
Architecture and Technology Choices
| Layer | Implementation | Why It Fits |
|---|---|---|
| Connectivity | Rithmic API adapters | Direct account, order, fill, and connection events avoid screen scraping or simulated clicks. |
| Execution Core | .NET worker services | Long-running services isolate routing, reconciliation, risk, and persistence from the dashboard process. |
| Concurrency | Channels and bounded dataflow blocks | Per-account ordering is preserved while independent followers run concurrently and apply backpressure. |
| State Store | Embedded database with append-only execution journal | Local durability supports crash recovery, duplicate detection, and audit searches without a remote database dependency. |
| Desktop UI | .NET dark dashboard | A single operator view exposes connection health, account controls, routing activity, and emergency actions. |
| Logging | Structured rolling logs | Order IDs, account IDs, state transitions, retry causes, and latency timestamps remain searchable without exposing credentials. |
Performance Validation and Market Context
The acceptance harness replays mixed market, limit, stop, bracket, OCO, partial-fill, scale, cancel, and reconnect scenarios against at least 100 simulated followers. It records dispatch latency, acknowledgement latency, missed-event count, duplicate count, state divergence, and recovery time. A release is blocked by any duplicate order or unresolved position mismatch.
The load assumptions are realistic for actively traded futures. CME Group reported 28.1 million contracts of average daily volume in 2025, while FIA reported 30.64 billion futures contracts globally during 2025. Those figures do not predict copier performance; they explain why deterministic routing, bounded queues, and recoverable state matter during busy sessions.
Rithmic Trader Pro Copy Trading and Prop-Firm Compatibility
The phrase Rithmic Trader Pro copy trading often refers to accounts visible through R|Trader Pro, but this application does not automate the desktop interface. It uses authorized API sessions. A Rithmic trade copier for Apex or another prop firm works only when that firm permits the connection, exposes the required account entitlements, and allows the intended order behavior.
Apex Trader Funding trade copier support and a Rithmic vs Tradovate trade copier comparison are connection questions, not interchangeable features. This build is Rithmic-native; it does not claim a Tradovate order adapter unless one is added and tested separately. Traadence provides trade copier customization and deployment and maintenance for approved account environments.
What the Download Includes
- Clean C# source, solution files, encrypted configuration handling, and environment-specific example settings without embedded credentials.
- Installation instructions, an operator guide, reconnect and flatten runbooks, plus structured log fields for support diagnostics.
- Unit, integration, load, and recovery tests covering order states, 100-follower fan-out, duplicate prevention, and reconnect reconciliation.
- A defined bug-fix period for reproducible defects within the delivered scope, supported by logs and repeatable test cases.
Project Directory
rithmic-trade-copier/
├── src/
│ ├── TradeCopier.App/
│ │ ├── App.xaml
│ │ ├── DashboardViewModel.cs
│ │ └── EmergencyFlattenCommand.cs
│ ├── TradeCopier.Core/
│ │ ├── MasterOrderNormalizer.cs
│ │ ├── FollowerDispatchPipeline.cs
│ │ ├── OrderStateMachine.cs
│ │ ├── PartialFillReconciler.cs
│ │ └── DuplicateOrderGuard.cs
│ ├── TradeCopier.Rithmic/
│ │ ├── RithmicSession.cs
│ │ ├── RithmicOrderAdapter.cs
│ │ ├── HeartbeatMonitor.cs
│ │ └── ReconnectCoordinator.cs
│ ├── TradeCopier.Risk/
│ │ ├── FollowerRiskPolicy.cs
│ │ ├── DailyLossGuard.cs
│ │ └── PositionLimitGuard.cs
│ └── TradeCopier.Persistence/
│ ├── ExecutionJournal.cs
│ ├── EncryptedSettingsStore.cs
│ └── CopierDbContext.cs
├── tests/
│ ├── TradeCopier.UnitTests/
│ │ ├── OrderStateMachineTests.cs
│ │ └── DuplicateOrderGuardTests.cs
│ └── TradeCopier.LoadTests/
│ ├── HundredFollowerFanoutTests.cs
│ └── ReconnectRecoveryTests.cs
├── config/
│ ├── appsettings.example.json
│ └── risk-policy.schema.json
├── docs/
│ ├── installation.md
│ ├── operator-guide.md
│ └── recovery-runbook.md
├── TradeCopier.sln
└── README.md
Questions
How do I copy trades across Rithmic accounts?
Connect one authorized master session and each follower account, set account-level multipliers and risk limits, then start the copier from the dashboard. Master order events are normalized and routed through the Rithmic API; fills, cancellations, brackets, stops, and targets are reconciled continuously rather than copied as isolated clicks.
Can I copy trades between Rithmic accounts at Apex and Take Profit Trader?
Only when both Apex Trader Funding and Take Profit Trader permit the intended API connection and the supplied Rithmic credentials expose the required accounts. The copier can isolate risk rules by account, but it cannot override prop-firm terms, account permissions, symbol restrictions, or API entitlements.