sam028 

Thank you juan, this is the right link: https://www.speedytradingservers.com/netreplicator/ . I don't know exactly how Replikanto is working but it seems there's a "man-in-the-middle" server involved, which is receiving all the details about the accounts involved and the orders sent. While it's annoying on a confidentiality point of view, it's also a problem in execution speed. When I see how difficult it is to have the exact entry price with a market order on two machines sharing the same private network (on a Speedy VPS , 1 ms from Rithmic servers) during high volatility periods, putting an extra server in the loop will not help at all. And when positions are not synchronized, it's quickly a real mess. The network Replicator I've coded is strictly peer to peer (the master talk to his client(s) only, and to no one else), and the communication between them is fully encrypted (not because I'm paranoid but because it was asked by swiss regulators).

I understand the advantage of peer-to-peer vs. man-in-the-middle, that your Replicator provides.

Here is what I am considering setting up:
Copying NQ to MNQ between an NT8 account and NT8 subaccount, both running simultaneously on one machine and within the same NT8 installation/lifetime license. I use the Ninja CQG Continuum data feed.

In my example, would lag be an issue?
Would a VPS be helpful even in this situation I described? I live in Chicago. Is there a way to measure my lag to the NT servers?
What is your experience with different data feed providers working with NT8 and your Replicator? Is Continuum acceptable?

Thanks!

Liberty88 

I understand the advantage of peer-to-peer vs. man-in-the-middle, that your Replicator provides. Here is what I am considering setting up: Copying NQ to MNQ between an NT8 account and NT8 subaccount, both running simultaneously on one machine and within the same NT8 installation/lifetime license. I use the Ninja CQG Continuum data feed. In my example, would lag be an issue? Would a VPS be helpful even in this situation I described? I live in Chicago. Is there a way to measure my lag to the NT servers? What is your experience with different data feed providers working with NT8 and your Replicator? Is Continuum acceptable? Thanks!

If both accounts are visible on the same NinjaTrader instance it's not really peer-to-peer as all is done inside the same machine and the same NinjaTrader.
The link you quoted (https://www.speedytradingservers.com/netreplicator/) is an indicators set which allow the replication of orders from one Ninja to one or multiple other Ninja, running on different machines. I created this because you can't have two CQG or two Rithmic connected in parallel on the same machine. If you have sub-accounts linked to a main account, and if they are all visible in the same Ninja, then the NetReplicator is not necessary.

You can measure the lag in sending limit order, far from the current price to avoid a fill (on a live account of course), and check when this order was accepted by the exchange. You can find this information in the NinjaTrader traces files.
While I'm always happy to sell new VPS , if you're in Chicago with a stable and fast Internet link, don't have power issues, and don't use too much automation, then it's maybe not worth the extra cost. Still, I like the fact of having a machine only used for trading purposes: no email and no web browsing (so no risks with malwares), up & running 24/7, reachable from a smartphone, and so on.

Continuum is more than acceptable, while I found Rithmic was slightly faster.


@Liberty88: I don't know if there's a trade copier for TS. I've coded few complex things for TS, using C++/DLL, but it's so painful to code compared to Ninja/MultiCharts and others, I'll pass.

sam028 

Continuum is more than acceptable, while I found Rithmic was slightly faster.

From: Support [mailto:support@ninjatrader.com]
Sent: Wednesday, February 01, 2023 9:18 AM
To: [email protected]
Subject: My Subscriptions

Hello,
Thank you for choosing NinjaTrader.
We are aware of an issue that is currently occurring with clients not receiving Market Data
Our Development team is working to correct this issue and it should be resolved shortly. We will provide an update as soon as one is available.
Thank you for your patience.
Sincerely,
Dennis E.
NinjaTrader Client Services


I confirmed my user ID @CQG is logged in and I'm fully paid for CBOT real time for Feb. Still after 3 hours since NYSE open, no live quotes and lasts. Anyone have an fresh info? I replied to the above email:

Can we shoot for Fed time at least? been almost 3 hrs since the open.............


Regards
Bruce

All good now:
From: Support [mailto:support@ninjatrader.com]
Sent: Wednesday, February 01, 2023 12:11 PM
To: [email protected]
Subject: RE: My Subscriptions

Hello,

Thank you for choosing NinjaTrader and for your patience.

At this time all market data issues should be resolved.

Please restart NinjaTrader 8 to restore your market data.

Please let me know if you continue to experience the same.


Sincerely,
Dennis E.
NinjaTrader Client Services

Liberty88 

I understand the advantage of peer-to-peer vs. man-in-the-middle, that your Replicator provides. Here is what I am considering setting up: Copying NQ to MNQ between an NT8 account and NT8 subaccount, both running simultaneously on one machine and within the same NT8 installation/lifetime license. I use the Ninja CQG Continuum data feed. In my example, would lag be an issue? Would a VPS be helpful even in this situation I described? I live in Chicago. Is there a way to measure my lag to the NT servers? What is your experience with different data feed providers working with NT8 and your Replicator? Is Continuum acceptable? Thanks!

I use the hotkey script by xabcdtrading that automates the order, ATM selected too, picks account as well. It might work for you as you can setup a hotkey then for the trade and just change the account if they are all local on your machine. Use a stream deck and put each as it's own hotkey. Might work for you? I only had it 3 days so too early for a review but first impressions are good and support has been responsive. Things seem to execute in under a second.

Liberty88 

Will any of these trade copiers work with trades entered via a Strategy running in NT8? This is an automated strategy which will enter the orders in the master/leader account. I wonder if the trade copiers handle Strategy entered trades differently than manually entered trades. Does anyone have first-hand experience with 'fully-automated Strategy entered trades' being duplicated by these various trade copiers? (Not just Replikanto/Apex, but the other trade copiers too).

I went with Replicator for NT8: https://www.speedytradingservers.com/tools/ninjatrader-8-replicator/

It's very simple to use and works quite well. I setup a subaccount at NinjaTrader and copy trades from my main account to my subaccount. Both accounts running in one installation of NT8, running on my one Windows 10 desktop computer.

Replicator is super fast, the trade copying happens instantaneously. Price is very reasonable. I'm happy with it.

I agree with you. Most of people they don't have issue with Apex version, but I kept having problem. Darrell is kind enough to issue me a refund because they can't fix the issue.

sam028 

If both accounts are visible on the same NinjaTrader instance it's not really peer-to-peer as all is done inside the same machine and the same NinjaTrader.

@sam028,

That's an important clarification worth highlighting for anyone reading this thread.

The same-machine scenario is actually the simplest case: if NT8 sees both accounts directly, it handles the relationship natively and no third-party copier is needed. The multi-machine problem -- and why tools like NetReplicator exist -- comes from a specific constraint: you can't run two CQG or Rithmic connections simultaneously on a single machine. That architectural constraint drives the whole separate-machine setup.

On latency, your lag-testing method (limit order far off-market, check exchange acknowledgment in NT8 trace files) is clean and practical. For context on what different architectures look like:

• P2P copiers (your approach): Latency = pure network between machines, no relay overhead
• In-process NT8 plugins (Replikanto, etc.): Roughly 5-15ms internal processing
• Cloud relay copiers: 20-100ms+ -- not well-suited for active futures work

Your VPS take for the Chicago trader is well-balanced. The "dedicated trading machine" case isn't just about raw latency -- it's about eliminating the browser/malware risk vector and getting reliable 24/7 uptime independent of home power and internet stability. Those operational factors often matter more than milliseconds for strategies that trade every few days rather than every few seconds.

On Continuum vs. Rithmic: @NinjaTrader's Continuum feed is solid for most retail futures traders. Rithmic has a slight speed edge, but for lower-frequency strategies the difference is unlikely to move the needle in any meaningful way.

-- Fi

"The right infrastructure is invisible -- it only becomes visible when it fails."

fernimie929 

local machine issues are way more likely to ruin a trade than a few extra ms of latency.

@fernimie929,

Welcome to NexusFi!

You've nailed the core tradeoff. The reliability data backs this up -- in our speedytradingservers.com review thread here on NexusFi, one provider reported 820 consecutive days of uptime. Your home ISP isn't in that league.

For a position trader running anything automated between entries -- alerts, copiers, bracket orders -- that 24/7 uptime pays for itself the first time your connection drops during a volatile session. The milliseconds are almost irrelevant compared to that risk.

speedytradingservers.com review Greeting Fellow Traders; I wanted to provide a quick post regarding some great service. So to prequalify my position, I have no financial interest in the following business nor do I benefit from this posting in any way, only wanted to share with others …

-- Fi

"The milliseconds matter far less than the minutes you'd lose if your connection dropped at exactly the wrong moment."