If you run a NinjaTrader trade copier across multiple prop firm accounts, a VPS (Virtual Private Server) is not optional — it is infrastructure. A VPS gives you 24/5 uptime, eliminates your home internet as a single point of failure, and reduces latency to the exchange by running in a data centre close to the CME. The two biggest copier failure modes — ghost orders (from unstable connections) and missed copies (from machine restarts or internet drops) — are both mitigated by running on a dedicated VPS. Key specs: Windows Server 2022, 4+ GB RAM, 2+ vCPU, SSD storage, and a data centre in Chicago (closest to CME) or New York.
A trade copier only works when NinjaTrader is running. If your home computer restarts, your internet drops, or Windows decides to install updates during the US session open, your copier stops — and your follower accounts are left with open positions that the leader is no longer managing.
A VPS solves this by running NinjaTrader in a data centre with enterprise-grade uptime (99.99%+), redundant internet connections, and no dependency on your local environment. You connect to the VPS via Remote Desktop when you need to manage settings, but the trading and copying happen on the server 24 hours a day, 5 days a week.
For prop firm traders running 10-50+ accounts through a copier, the VPS is not a nice-to-have. It is the difference between a reliable operation and a single point of failure that can breach multiple funded accounts simultaneously.
VPS setup walkthrough for NinjaTrader and trade copier.
NinjaTrader 8 requires Windows. Most VPS providers offer Windows Server 2022, which is fully compatible. Do not use a Linux VPS for NinjaTrader — it will not run natively. Some traders attempt Wine or virtual machine workarounds, but these add instability to exactly the system that needs to be rock solid.
The CME (Chicago Mercantile Exchange) is where your futures orders are matched. A data centre in Chicago gives you the lowest latency to the exchange. New York is the second-best option. For most prop firm traders running a copier, Chicago or New York provides sub-5ms latency to the exchange, which is more than fast enough.
London-based data centres work for European session traders but add 70-100ms of latency to CME — acceptable for manual trading but worth considering if you are scalping tick-by-tick.
1st choice: Chicago (closest to CME). 2nd choice: New York (still sub-5ms to CME). 3rd choice: Any US East Coast location. Avoid: West Coast US, Europe, or Asia for CME futures trading — the added latency compounds across multiple follower accounts.
NinjaTrader 8 is resource-hungry, especially when running multiple broker connections and a trade copier add-on. Minimum specs for a copier setup:
| Accounts | RAM (minimum) | vCPU | Storage |
|---|---|---|---|
| 1-10 accounts | 4 GB | 2 cores | 60 GB SSD |
| 10-30 accounts | 8 GB | 4 cores | 80 GB SSD |
| 30-50+ accounts | 16 GB | 4-6 cores | 120 GB SSD |
SSD storage is non-negotiable. NinjaTrader writes to disk constantly (logs, workspace data, tick data). A spinning HDD adds latency to every disk operation and will cause NinjaTrader to lag under load.
Look for 99.99%+ uptime guarantees. At 99.9%, you are accepting up to 8.7 hours of downtime per year. At 99.99%, that drops to under 53 minutes. For a copier managing funded prop firm accounts, every minute of downtime is a minute where follower positions are unmanaged.
Several VPS providers specifically target NinjaTrader and futures traders. The landscape includes trading-specific providers (pre-configured for NinjaTrader) and general cloud providers (you configure yourself). Both work. The trade-off is convenience vs cost.
These come pre-configured with Windows Server, NinjaTrader-ready environments, and data centres in Chicago or New York. Pricing typically starts at $50-$80/month for basic plans and scales to $150-$300/month for high-performance setups. The advantage is zero configuration — you connect via Remote Desktop and start running NinjaTrader immediately.
AWS, DigitalOcean, Google Cloud, and Azure all offer Windows Server VPS instances. You configure NinjaTrader yourself. Pricing can be lower ($30-$60/month for equivalent specs) but requires more technical knowledge for initial setup. AWS has a data centre in us-east-2 (Ohio) which is close to Chicago. DigitalOcean has New York and Toronto.
| Provider type | Typical cost | Setup time | Pre-configured? | Best for |
|---|---|---|---|---|
| Trading-specific VPS | $50-$300/mo | Minutes | ✓ Yes | Traders who want zero config — just start trading |
| General cloud (AWS, DO, Azure) | $30-$150/mo | 1-2 hours | ✗ No | Technical traders who want cost control and customisation |
Ghost orders — phantom positions that appear in NinjaTrader but do not exist at the broker level — are one of the most frustrating issues in any copier setup. They are caused by connection interruptions between NinjaTrader and the broker's data feed. When the connection drops and reconnects, NinjaTrader can lose sync with the broker's actual position state.
A VPS with enterprise-grade internet (redundant connections, low-latency routing) experiences far fewer connection drops than a home internet setup. The connection between NinjaTrader on your VPS and the Rithmic/CQG servers stays stable because both are in data centres with direct peering — not routing through your ISP's consumer network.
Ghost orders do not disappear entirely on a VPS. They are a NinjaTrader-level issue that any local copier inherits regardless of infrastructure. But the frequency drops dramatically when the underlying connection is stable.
NinjaTrader 8 requires Windows. Windows Server 2022 is the current standard. Avoid Windows 10/11 desktop licences on VPS — server editions are optimised for always-on operation.
Download NinjaTrader 8 from ninjatrader.com. Import your copier add-on via Tools → Import → NinjaScript Add-On. Connect all broker accounts (leader + followers).
Windows Updates will restart your VPS during trading hours if you do not disable auto-restart. Set active hours to cover the full trading session or defer restarts to weekends.
If the VPS restarts (maintenance, crash), NinjaTrader should start automatically. Add NinjaTrader to Windows Startup and configure your workspace to load on launch. Some traders use a watchdog script that detects crashes and relaunches.
Before connecting live accounts, run the full copier setup in simulation on the VPS. Place trades on the leader, verify every follower copies correctly — entry, stop, target, modification, and close.
Use Remote Desktop from your phone or laptop to check the VPS during the trading session. Some providers offer mobile apps. Set up email or Discord alerts for connection drops or account issues.
Most prop firm copier traders run accounts from multiple firms simultaneously — Apex, Topstep, Take Profit Trader, Bulenox, Tradeify, and others. A single NinjaTrader instance on one VPS can connect to all of these, provided each account's data feed is configured correctly.
Rithmic accounts (Bulenox, some Apex and TPT accounts) connect through a single Rithmic login with multiple account IDs. NinjaTrader handles this natively — you add each account under the same Rithmic connection and the copier addresses them individually.
CQG accounts (some TPT and Topstep accounts) use a different connection type. You can run both Rithmic and CQG connections simultaneously in a single NinjaTrader instance. The copier sees all connected accounts regardless of data feed provider.
Tradovate accounts connect through their own integration. If you mix Tradovate-connected accounts with Rithmic-connected accounts, verify that your copier supports cross-connection copying. Not all copiers do. Some only copy between accounts on the same data feed.
The practical limit is not the number of accounts but the RAM and CPU on your VPS. Each connected account consumes resources for order management, position tracking, and data feed processing. With 20+ accounts across multiple data feeds, 8 GB RAM is the realistic minimum. With 40+ accounts, go to 16 GB and consider whether you need a second NinjaTrader instance or VPS to distribute the load.
Here is what a realistic VPS budget looks like for different scales of operation.
| Setup | VPS spec | Monthly cost | Context |
|---|---|---|---|
| Starter (5-10 accounts) | 4 GB RAM, 2 vCPU, 60 GB SSD | $50-$80/mo | Solo trader with one firm, basic copier setup |
| Growth (10-25 accounts) | 8 GB RAM, 4 vCPU, 80 GB SSD | $80-$150/mo | Multi-firm trader with copier + monitoring |
| Professional (25-50+ accounts) | 16 GB RAM, 4-6 vCPU, 120 GB SSD | $150-$300/mo | Heavy multi-firm operation, may need 2 VPS instances |
Compare the VPS cost to the value it protects. If you run 10 funded accounts averaging $50K each, those accounts represent thousands of dollars in evaluation fees, activation fees, and months of effort. A $100/month VPS that prevents one blown account per year pays for itself many times over.
Some traders try to save money by running NinjaTrader on their home computer and only using a VPS for backup. This defeats the purpose. The VPS is not a backup — it is the primary system. Your home computer is the backup. The copier should run on the VPS 24/5, and you should only connect from home to manage settings or monitor positions.
A VPS running unattended needs a monitoring layer. If NinjaTrader crashes at 9:35 AM and you do not notice until 10:30 AM, every follower account has been sitting unmanaged for 55 minutes during the most volatile period of the trading session.
UptimeRobot (free tier): Monitors your VPS's internet connectivity. If the VPS goes offline, you get an email or SMS alert within minutes. This covers VPS-level failures but does not detect NinjaTrader application crashes.
Watchdog scripts: A simple PowerShell or batch script that checks whether the NinjaTrader process is running every 60 seconds. If the process is not found, the script relaunches NinjaTrader and sends an alert (email, Discord webhook, or SMS via a service like Pushover). This is the single most valuable monitoring tool for copier traders — it catches application crashes that UptimeRobot would miss.
Daily position reconciliation: At the end of each trading day, compare the positions tab in NinjaTrader with the positions shown in each broker's web portal (Rithmic R|Trader, Tradovate dashboard, etc.). If there is a mismatch, you have a ghost order or a missed copy. Catching this daily prevents compounding errors across multiple sessions.
Remote Desktop on mobile: Both Microsoft Remote Desktop (iOS/Android) and third-party clients like Parsec let you check your VPS from your phone. Get in the habit of checking once before the open and once after the close. A 30-second visual inspection catches most issues before they become expensive.
NinjaTrader freezes after overnight session. NinjaTrader occasionally hangs when the data feed reconnects at the start of a new trading day (5:00 PM CT Sunday or after a daily reset). The fix is a scheduled task that restarts NinjaTrader 5 minutes before the session open — kill the process, wait 30 seconds, relaunch. This prevents the freeze and ensures a clean startup.
Remote Desktop session disconnects kill NinjaTrader. By default, disconnecting from a Remote Desktop session may suspend processes on some VPS configurations. Ensure your VPS is configured to keep all processes running when the RDP session is disconnected. On Windows Server, this is controlled through Group Policy settings for session time limits. Trading-specific VPS providers typically configure this correctly out of the box.
Rithmic connection drops during high-volume periods. The first 5 minutes of the US open (9:30 AM ET) generates the highest message volume on Rithmic's servers. Connection drops during this period are more common than at any other time. If your copier misses a fill during a Rithmic reconnection, the leader will have a position that the followers do not. Monitor the Rithmic connection status icon in NinjaTrader's Control Center and have a procedure for manually reconciling positions if a disconnect occurs during the open.
Disk space fills up with NinjaTrader logs. NinjaTrader writes logs continuously. Over weeks and months, the log folder can grow to several gigabytes. Schedule a monthly cleanup of the NinjaTrader log directory (Documents/NinjaTrader 8/log/) to prevent the SSD from filling up. A full disk causes NinjaTrader to behave unpredictably — from slow performance to crashes.
Time zone mismatch. Set your VPS's system time zone to match the exchange time zone (US Central for CME) or your local time zone — whichever you are more comfortable reading. NinjaTrader displays chart times based on the system clock. If your VPS is set to UTC and you are used to reading Central Time, every timestamp will be off by 5-6 hours. This does not affect trade execution but causes confusion when reviewing session times and log entries.
Bandwidth usage is minimal. NinjaTrader consumes very little bandwidth — the data feed is a low-volume stream of tick data and order updates. Even with 20+ connected accounts, total bandwidth usage rarely exceeds 10 Mbps sustained. This means you do not need a VPS with expensive high-bandwidth plans. The minimum bandwidth offered by any reputable VPS provider (100 Mbps or 1 Gbps shared) is more than sufficient. The priority is latency and stability, not raw throughput.