Rithmic

A trade copier on Rithmic rails.

Rithmic is the layer a lot of traders use without ever choosing it — several prop firms route their accounts through it, and it turns up as a connection option rather than a product you signed up for. This is what that means for copying trades across accounts.

What Rithmic actually is

Rithmic is order routing and market data infrastructure, not a trading platform you sit in front of. It sits between a front-end — R|Trader Pro, Quantower, a broker's own software — and the exchange, and it is what a number of prop firms use to carry their accounts.

That is why it appears in this context. People rarely go looking for a "Rithmic trade copier". They discover that the funded account they just bought connects through Rithmic, and then need to know whether the thing they wanted to do still works.

It does, and the mechanics are the same as anywhere else: something has to hold a session, receive the fill as an event, and place sized orders on the other accounts.

Where Rithmic sitsyour account path
  1. Front endR|Trader Pro, Quantower, or whatever your firm hands you. This is what you click in.
  2. RithmicOrder routing and market data. The layer carrying your orders and reporting your fills.
  3. ExchangeWhere the trade actually happens.
  4. The copierReacts to the fill report and places its own sized orders on your other accounts.

A copier does not replace your front end. You keep trading exactly as you do.

Why the connection layer matters for copying

It decides what the copier is reacting to, and that is the whole difference between a copier that is right and one that is nearly right.

A copier that polls — asks "what does this account hold now?" every few seconds — infers what happened. Two fills inside one interval look like one; an entry that reverses inside the interval looks like nothing happened at all.

A copier working from execution events is told what happened, with an id attached. It can mirror each partial as a partial, and recognise a retransmission as the same fill rather than a second one. Quanify works this way on every rail it supports.

This is also why per-account addressing matters. A prop-firm login often carries several funded accounts. If the connection is treated as the unit rather than the account, per-account sizing is impossible — and per-account sizing is the point.

Sized for each account, capped for each account

The reason to copy across funded accounts is that they are not the same size, and the reason it goes wrong is that people copy them as if they were.

Whole-number multipliers

Each account scales the leader's fill by its own number, applied before the order is sent. There is no 0.5× — contracts are indivisible and a tool that rounds quietly sizes you wrong without saying so.

One fill, several sizes

Per-account sizing

A whole-number multiplier per account, applied before the order is sent, so a small evaluation and a large funded account do not have to trade the same size.

Sized before dispatch

Mute, not unlink

Pause one account without dismantling the group. Mute is held by the engine, so a refresh or a second device cannot disagree about what is armed.

Configuration survives the pause

Nothing running on your machine

Rithmic front-ends are desktop software, and the reflex is to assume a copier must be too. It does not have to be — and if it is, its uptime becomes your uptime, which is what the VPS advice in every copier forum is really about.

Quanify holds the session server-side. Copies keep landing with your laptop shut, and there is no desktop process whose crash you discover from a position you did not expect, or from one you expected and do not have.

Nothing arms itself either. Every account you add lands disabled, and a trader will not report itself armed until the engine confirms the routing. Configuring is not arming.

Before you arm a funded account

Whether you may mirror across a firm's accounts is set by the firm's contract, not by Rithmic and not by any copier. Rules differ between evaluation and funded accounts at the same firm, and they change without notice.

Read the current rulebook for the specific account, searching for copy, mirror, duplicate, multiple accounts and automated. If a clause is ambiguous, ask support and keep the reply — an ambiguous rule gets resolved at payout time. Copy trading and prop firms covers what those clauses usually guard against.

Common questions

What is Rithmic?

Order routing and market data infrastructure that sits between a trading front-end and the exchange. It is not a platform you trade in directly — it is the layer carrying your orders, and several prop firms route their funded accounts through it.

Can I copy trades between Rithmic accounts?

Yes, provided they are accounts you own and your firm's rules permit it. One account leads, the others follow at their own sizes, with each account's multiplier applied before its order is sent.

Do I need R|Trader Pro open to copy trades?

Not with Quanify. The session is held server-side, so copies continue with your machine off. You keep using whatever front-end you prefer for your own trading.

Is Rithmic better than Tradovate for copy trading?

Neither is better for this. What matters is that the copier reacts to execution events rather than polling a position summary, and that each funded account under a login is addressable on its own. Quanify does both on every rail it supports.

Can I copy between a Rithmic account and a Tradovate account?

Yes, as long as both are accounts you own. The leader and its followers do not have to sit on the same connection or the same platform.

Does my prop firm allow this?

That is a contract question for your specific firm and account type, and firms change their rules without a changelog. Read the current rulebook before arming anything — no copier can make an account compliant with a rule that forbids mirroring.

Start on a simulated account.

Connect a sim or evaluation account and run the whole product against it before you point anything at live money. Nothing about the setup changes when you do.