Best VPS for NinjaTrader 8: Setup Checklist, Server Sizing, and Remote Access

For NinjaTrader 8, choose a hosted Windows workspace with enough capacity for your charts, NinjaScript indicators and companion tools. Ninja Mobile Trader VPS specializes in hosting NinjaTrader Desktop, with included Windows licensing, 24/7 support and the same workspace accessible from your PC, Mac or phone. Our Medium, High Performance and Pro options let you match the resources to the way you actually use the platform.

Match your NinjaTrader workspace to an NMT plan#

Our published allocations, checked October 9, 2026, include Windows Server 2022. The current plan specifications also list processor allocations and pricing.

Medium provides 8 GB, High Performance doubles that to 16 GB, and Pro provides 32 GB. Start by comparing those options for a full NinjaTrader Desktop workspace. When your required indicators, chart history and other applications need more working memory, High Performance and Pro give you larger allocations within NMT.

Use the workload checks below to select capacity. Windows and your companion applications need resources alongside NinjaTrader; a plan’s RAM figure does not guarantee a particular chart or account count. Small’s 3.5 GB allocation is below NinjaTrader’s recommended 8 GB memory profile.

NinjaTrader system requirements: minimum versus recommended#

NinjaTrader’s official system requirements list Windows 11 or Windows Server 2016 or later, a 64-bit processor of at least 1 GHz, 2 GB RAM, .NET Framework 4.8 and a 1024 × 768 display as the minimum. Its recommended specifications include a 2 GHz or faster quad-core processor, 8 GB RAM, DirectX 10 graphics and SSD storage.

The recommended RAM figure is a baseline for comparison, not a complete workload specification. Record your platform version, indicators, instruments, chart history and companion tools before choosing resources. Processor count alone does not establish equivalent performance for a particular script.

Check the complete workspace, not an empty desktop#

Open your normal charts, connections and add-ons together in a suitable simulation environment. Use Task Manager inside the VPS to inspect CPU and available memory during loading and while charts update. Include the session conditions you normally use.

An isolated spike or a high memory reading alone does not establish a bottleneck. NinjaTrader’s performance guidance identifies chart history, open workspaces and third-party scripts as important load factors. If a required workload repeatedly needs more sustained resources, our VPS versus dedicated server guide covers the upgrade decision and controlled migration.

Include Tick Replay in the sizing check#

Tick Replay processes historical tick events for indicators and strategies designed to use them. That adds calculation work; loading a short ordinary chart does not represent a history-heavy Tick Replay workspace.

Check the indicator developer’s requirements first. In NinjaTrader, Tools > Options > Market data > Show Tick Replay exposes the option; enable Tick Replay in the intended chart’s Data Series settings when supported. Built-in Renko and Line Break bars do not support it.

Tick Replay calculates historical NinjaScript events. The separate Playback connection replays market data for simulation. Tick Replay is not an order-fill accuracy setting and does not make a backtest equivalent to live execution; NinjaTrader also documents that it cannot be combined with High Order Fill Resolution. See the Tick Replay development notes.

Run a controlled comparison#

Use a separate simulation workspace, with live order-producing strategies, copiers and automatic recovery stopped for the test.

1. Record the conditions. Note the NMT plan, Windows/platform and indicator versions, instrument, bar type, trading hours, Days to load and indicator settings. Keep them the same between runs.
2. Record the ordinary load. Load the test chart with Tick Replay off. Note whether historical data is downloading or already cached, and when chart loading finishes.
3. Repeat with Tick Replay on. Use the same conditions and observe Task Manager inside the VPS. Keep first-time downloads separate from cached reloads so network time is not mistaken for calculation time.
4. Check the required full workspace. Add back the other charts and tools you need, still in simulation. Record both loading behavior and responsiveness after loading.

If an indicator requires Tick Replay, the off run is only a diagnostic baseline; it is not a substitute for that indicator’s correct configuration. Do not remove a required setting just to obtain a faster result.

Use this blank worksheet for your own observations:

NinjaTrader notes that Tick Replay can generate many events per bar and is limited by the historical tick data your provider supplies. Use only the history your workflow requires. When the necessary full workspace shows a memory constraint, compare NMT’s 16 GB and 32 GB options; if calculations are the constraint, review the responsible script and processor requirements. Bring the worksheet to our support team so the plan discussion is about your actual workload.

Set up the platform, data feed, and copier tools#

1. Install the supported NinjaTrader release. Confirm your indicators and add-ons support that version before moving them.
2. Restore your workspace. Use NinjaTrader’s backup and restore procedures, then check charts, templates and external dependencies.
3. Connect the correct account. Use your broker’s or prop firm’s connection instructions and confirm the account and environment displayed in NinjaTrader.
4. Add the copier or strategy. Check licensing, follower mapping and startup behavior in simulation before enabling it on a live account. The NinjaTrader copier guide covers these checks.

For disconnected NinjaTrader broker or data feeds, we recommend Ninja Watchdog. It reconnects supported connections, including Rithmic and Tradovate, and waits for live data before restoring interrupted strategies. See our recovery overview for setup and limitations. Recovery software cannot make an unavailable provider respond.

Check the broker route separately from remote desktop speed#

Your device reaches the VPS over one connection; the VPS reaches your broker or data provider over another. A responsive remote desktop does not measure the broker route, and a network ping is not an order-execution measurement.

Use the provider’s actual endpoint when comparing locations. Our VPS latency testing guide explains the measurements and their limits.

Reconnect from a backup device before you need it#

Remote Desktop lets a Mac, phone or tablet reach the Windows installation of NinjaTrader Desktop and its add-ons. It does not run them natively on that device; NinjaTrader’s separate web and mobile products serve different needs.

Disconnect from a test session and reconnect from your backup device. Confirm that you reach the same desktop and can read the account selector and order controls. Disconnecting can leave Windows applications running; signing out closes them. Microsoft’s Remote Desktop session guidance explains the distinction. Session policies, restarts and application failures can still interrupt a disconnected session.