VPS-Native NinjaTrader Trade Copier: How to Get Sub-10ms Execution on Any Prop Firm

Sub-10ms from leader order to all follower executions is achievable. It requires three things working correctly together: a copier that runs locally inside NinjaTrader (not in the cloud), a VPS located geographically close to the exchange, and broker connections that don't introduce unnecessary round-trip overhead. Here's how to put all three together.

Understanding the Latency Stack

Total execution latency is the sum of several components:

1. Copier internal latency: time from leader order detection to follower order generation (inside NinjaTrader)
2. VPS-to-exchange latency: round-trip time from your VPS to the broker's servers and back
3. Broker processing time: time the broker takes to route and confirm the order

You can control the first two. The third is broker-dependent and largely fixed.

Benchmark targets:

• Copier internal (Copilink, local NinjaTrader): ~1.6ms
• VPS-to-CME (Chicago datacenter): ~1-2ms
• Broker processing (Tradovate or Rithmic): ~3-5ms
• Total realistic target: 6-9ms

Compare that to a cloud-based copier from a home machine: copier cloud relay (20-40ms) + home internet to broker (10-30ms) + broker processing (3-5ms) = 33-75ms. Not comparable.

VPS Location: Why Chicago Over Everywhere Else

CME Group's Globex matching engines are in Aurora, Illinois — a suburb of Chicago. Every NQ, ES, CL, and GC futures order you place travels from your machine to Aurora and back. Physical distance = latency. There's no software fix for geography.

A VPS in Chicago's major datacenters (Equinix CH1/CH2, CyrusOne Chicago) sits 1-2ms from CME. A VPS in New York is 5-8ms. A VPS in London or Frankfurt is 90-110ms. For futures specifically — not forex, not equities — Chicago is the only correct answer for minimizing latency.

Providers with Chicago datacenter presence and NinjaTrader compatibility:

• QuantVPS — purpose-built for trading, pre-configured Windows instances, Chicago nodes
• Vultr (Chicago) — general cloud, good performance, requires manual Windows/NinjaTrader setup
• Contabo — budget option, US Midwest location, higher-variance latency than dedicated trading VPS providers

VPS Specs for Sub-10ms Execution

The VPS hardware affects copier internal latency — specifically how fast NinjaTrader can process the leader order and generate follower orders. On a slow VPS, the copier's "1.6ms" benchmark doesn't hold; it degrades.

Minimum specs for consistent sub-10ms total execution:

• CPU: 4+ dedicated cores (not shared vCPUs) — NinjaTrader is single-threaded heavy; core speed matters more than core count
• RAM: 16GB minimum for 5-10 accounts with active charts
• Storage: NVMe SSD — rotational disk causes I/O spikes during data loads
• Network: 1Gbps dedicated uplink — standard on any reputable VPS provider

Broker Connection: Tradovate vs. Rithmic for Latency

Rithmic has slightly lower exchange-side latency than Tradovate — it's purpose-built for institutional-grade execution. The difference in NinjaTrader-based prop firm trading is approximately 2-4ms in favor of Rithmic on the broker processing component.

However, Rithmic's Plugin Mode overhead (when running multiple accounts) can partially offset that advantage. For a single-account leader configuration with Tradovate followers, the total latency difference is often negligible in practice.

The cleaner setup for sub-10ms total across many accounts: Tradovate API connections for all accounts (no Plugin Mode dependency), local Copilink for copying, Chicago VPS. This delivers consistent sub-10ms performance without the session management complexity of Rithmic at scale.

Verifying Your Latency

Once your setup is configured, verify the actual execution latency before going live. Copilink logs timestamps for leader order detection and follower order execution — pull these from the trade log on a test session and calculate the delta. You should see consistent sub-10ms leader-to-follower replication if everything is configured correctly.

If you're seeing 15ms+, check in order: VPS location (are you actually on a Chicago node?), VPS CPU performance under load (Task Manager during a busy session), and whether the Tradovate or Rithmic connection is adding latency due to a configuration issue.

Start the configuration at copilink.com — the 7-day trial is enough time to validate your latency profile before committing.