How to Set Up NinjaTrader for Gold, Silver & Oil Futures on a Chicago VPS

NinjaTrader is widely used for trading CME futures because it combines charting, order entry, DOM tools, custom indicators, NinjaScript strategies, automation, and support for multiple futures connectivity providers in one desktop platform.

For traders following Gold, Silver, and WTI Crude Oil futures, one NinjaTrader workspace may contain GC, MGC, SI, SIL, CL, MCL, multiple charts, SuperDOM windows, order-flow tools, custom indicators, trade copiers, and automated strategies at the same time.

That can place very different demands on a computer than simply opening one chart.

CPU performance matters because NinjaTrader has to process incoming market data and calculate indicators or strategy logic.

RAM matters as the number of charts, instruments, workspaces, data series, and applications increases.

Storage performance affects local databases, historical data, logs, NinjaScript files, platform startup, and workspace loading.

Network quality matters because the platform has to maintain its connection to the broker or market-data gateway.

And uptime matters if alerts, strategies, or other permitted automated processes need to keep running after the trader turns off a laptop.

A Chicago VPS for NinjaTrader moves this environment from a home computer into a remote data center. That can be especially relevant for CME futures because CME’s current Aurora, Illinois co-location facility houses the trade matching engines for Globex products.

The benefit is not that a VPS magically improves a trading strategy.

It does not guarantee faster fills, prevent slippage, eliminate broker outages, or make Gold, Silver, and Oil easier to predict.

The benefit is infrastructure: a persistent Windows environment with appropriate CPU, memory, storage, connectivity, and proximity to the futures ecosystem.

This guide walks through how to set up NinjaTrader for Gold, Silver, and Oil futures on a Chicago VPS, from choosing server resources and installing NinjaTrader to connecting market data, adding GC/SI/CL contracts, configuring workspaces, managing rollovers, improving reliability, and preparing automated strategies for unattended operation.

Why Use a Chicago VPS for NinjaTrader Futures Trading?

NinjaTrader can run perfectly well on a normal desktop computer. A VPS becomes useful when the trader wants the platform to remain available independently of that computer.

Imagine a NinjaTrader workspace running GC, SI, and CL.

The trader has several charts open, a SuperDOM for each market, alerts on key levels, and one NinjaScript strategy monitoring Micro Gold.

If everything is running on a laptop at home, the entire environment depends on that laptop remaining powered on.

It also depends on residential electricity.

The router needs to remain online.

The home Internet provider needs to remain connected.

Windows must avoid sleep or hibernation.

NinjaTrader itself needs to stay running.

A VPS moves the software to a server hosted in a data center.

The trader can disconnect Remote Desktop or shut down the local laptop while NinjaTrader remains running on the remote machine.

For CME markets, Chicago has another advantage.

CME states that its Aurora, Illinois facility houses the matching engines for all Globex products, along with customer co-location infrastructure.

That does not mean every retail NinjaTrader order travels directly from a VPS to the matching engine.

A typical route may involve:

NinjaTrader → connectivity provider/broker → risk systems → exchange infrastructure

Rithmic, CQG/Continuum, Tradovate, Interactive Brokers, and other environments can follow different paths.

Therefore, the most useful latency test is not simply “ping CME.”

It is the connection from the VPS to the actual gateway or service used by the trading account.

This distinction matters because Chicago is a good geographic starting point, but routing ultimately determines the real network path.

Gold, Silver & Oil Contracts You Can Run in NinjaTrader

Before configuring the platform, it helps to understand which contracts belong in the workspace.

For Gold, the major products include:

GC — Gold futures
100 troy ounces.

MGC — Micro Gold futures
10 troy ounces, or one-tenth of GC. CME lists a $0.10-per-ounce minimum movement; with a 10-ounce multiplier, that corresponds to $1 per contract.

1OZ — 1-Ounce Gold futures
One ounce and one-hundredth the size of GC. This contract now trades 24/7 except for scheduled maintenance windows.

For Silver:

SI — Silver futures
5,000 troy ounces.

SIL — Micro Silver futures
1,000 ounces, or one-fifth of SI. CME currently lists a $0.01-per-ounce minimum move, which produces a $10 minimum tick value.

SIC — 100-Ounce Silver futures
100 ounces, cash-settled to the benchmark Silver contract, with a minimum move of $0.01 per ounce, or $1 per contract.

CME scheduled SIC to begin continuous weekend trading on September 11, 2026, with the first production weekend session opening at 4:30 p.m. CT because of a one-time extended maintenance period. Subsequent Friday sessions are scheduled to reopen at 4:02 p.m. CT.

For WTI Crude Oil:

CL — WTI Crude Oil futures
1,000 barrels.

MCL — Micro WTI Crude Oil futures
100 barrels, one-tenth of CL. The minimum move is $0.01 per barrel, producing a $1 minimum tick compared with $10 for CL.

These contracts allow a single NinjaTrader environment to cover benchmark and smaller-sized versions of all three commodity markets.

Step 1: Choose the Right VPS Resources for NinjaTrader

The first decision is server size.

NinjaTrader’s published recommended specifications include a 2 GHz-or-faster quad-core 64-bit processor, 8 GB RAM, an SSD, and a DirectX-compatible graphics environment. NinjaTrader also notes that resource requirements vary with actual usage and that additional memory can help with strategy optimization and heavier workloads.

Those specifications are a starting point, not necessarily the ideal configuration for a serious multi-market trading setup.

A practical VPS sizing guide looks more like this:

NinjaTrader workload	Practical VPS starting point
1–2 simple charts	2 fast CPU cores, 8 GB RAM
GC + SI + CL basic workspace	4 fast CPU cores, 16 GB RAM
Several charts + SuperDOM + indicators	4–6 fast cores, 16–24 GB RAM
Order flow + multiple workspaces	6+ fast cores, 24–32 GB RAM
Multiple strategies / trade copier / several platform instances	8+ cores, 32 GB+ RAM

High clock speed is particularly valuable.

A common mistake is assuming that a large number of slow server cores automatically makes a better NinjaTrader VPS.

NinjaTrader can use multiple CPU resources, but specific charts, NinjaScript processes, indicators, user-interface operations, and data-processing tasks can still be sensitive to per-core performance.

For that reason, high-frequency desktop-class processors can be useful for trading applications.

TradingVPS’s current Chicago Ryzen plans use AMD Ryzen 9 9950X CPU resources at approximately 4.3–5.7 GHz, DDR5-5200 RAM, NVMe storage, dedicated IPv4 addresses, and Windows Server 2022. Plans currently range from 1 core/4 GB through larger 16-core/64 GB environments.

For a combined Gold, Silver, and Oil NinjaTrader setup, a 4-core/16 GB configuration is a reasonable middle starting point if the trader expects to run several charts and indicators.

Heavier order-flow or automated environments can benefit from more headroom.

The important principle is not to size the VPS so tightly that normal market activity already pushes CPU or RAM close to 100%.

Commodity futures can become extremely active during major releases. Gold may experience large bursts of updates around CPI or the FOMC. Oil can accelerate around EIA inventory data. Silver can become highly active during precious-metals momentum.

The server should have spare capacity for those periods.

Step 2: Use Windows Server for NinjaTrader

NinjaTrader Desktop requires Windows.

The current NinjaTrader minimum requirements support Windows 10, Windows 11, and Windows Server 2016 or later in 64-bit form.

For a VPS, Windows Server 2022 is therefore a practical choice.

Once the VPS is provisioned, the provider will normally supply:

• the server IP address,
• the Windows administrator username,
• and an initial password.

From a Windows computer, connect using Remote Desktop Connection.

On macOS, iPhone, iPad, or Android, a compatible Microsoft Remote Desktop client can be used.

The important idea is that Remote Desktop is only the control interface.

When the RDP window is closed, the VPS itself continues running.

Do not shut down Windows when you simply want to disconnect from the server.

Use Disconnect, not Shut down.

Otherwise, the purpose of an always-on trading server is defeated.

Step 3: Update and Secure Windows Before Installing NinjaTrader

Before installing trading software, complete basic server housekeeping.

Use a strong administrator password.

Keep Windows Defender or another appropriate security system enabled.

Restrict unnecessary firewall ports.

Do not use the trading VPS as a general-purpose browsing computer.

Avoid installing random utilities, games, browser extensions, or unrelated software.

A trading VPS works best when it remains a focused environment.

The fewer unnecessary processes running in the background, the easier it is to diagnose CPU, RAM, or connection problems later.

You should also check the server’s time and time zone.

For futures traders, Central Time can be convenient because CME schedules are usually published in CT.

However, NinjaTrader charts and strategy logic may use platform or computer time settings depending on configuration, so avoid changing time zones casually after strategies have already been designed around a specific session template.

Step 4: Install NinjaTrader 8

NinjaTrader’s current installation process begins by logging into the NinjaTrader account, accessing the Download area, installing the platform, and then configuring the appropriate broker or data connection. NinjaTrader also requires .NET Framework 4.8 where it is not already installed.

But using our TradingVPS, you can skip this step because our VPS is pre-installed some trading platforms like Ninjatrader.

The basic workflow is:

1. Open the browser on the VPS.

Go to the official NinjaTrader site and sign into the account.

2. Download NinjaTrader Desktop.

Use the current installer rather than copying an old NinjaTrader installation from another machine.

3. Install NinjaTrader.

Use the default platform directory unless there is a specific reason to change it.

4. Launch NinjaTrader and sign in.

Choose Simulation first when testing a new server environment.

5. Confirm that the Control Center opens correctly.

The NinjaTrader Control Center becomes the primary place for connections, accounts, orders, strategies, instruments, logs, and platform configuration.

NinjaTrader specifically warns that its DocumentsNinjaTrader 8 folder should not be synchronized through systems such as OneDrive or Dropbox because file-access conflicts can occur.

That warning is especially relevant on a VPS.

Avoid enabling cloud-folder synchronization on the live NinjaTrader data directory.

Use proper backups instead.

Step 5: Connect Your Broker and Market Data

Installing NinjaTrader does not automatically give the platform permission to trade GC, SI, or CL.

The platform needs an account connection to a supported broker or data provider.

NinjaTrader currently manages connections from the Connections menu in the Control Center. Additional providers can be configured when Multi-provider mode is enabled.

Depending on the trading setup, connectivity may involve:

• NinjaTrader Brokerage / Continuum,
• Rithmic,
• CQG-based infrastructure,
• Interactive Brokers,
• or another supported provider.

The exact credentials and configuration differ.

Follow the specific NinjaTrader connection guide for the broker or technology being used rather than copying settings from an unrelated provider.

A standard connection workflow is:

Control Center → Connections → Configure

Select the connectivity provider.

Add it.

Enter the credentials supplied by the broker or provider.

Give the connection an identifiable name.

Test the connection.

Only after it is working reliably should Connect on startup be enabled.

NinjaTrader itself recommends testing the connection first because incorrect credentials or settings can interfere with automatic startup.

Market Data Entitlements Still Matter

A Chicago VPS does not provide futures market data by itself.

The brokerage or data subscription must include the required exchange entitlements.

For these markets that can include COMEX and NYMEX data, depending on the products being traded.

If GC loads but shows no live data, the first question should not automatically be “Is the VPS broken?”

Check:

• broker connection status,
• data-feed connection,
• exchange subscription,
• selected contract month,
• market hours,
• and whether the current contract is active.

Step 6: Add GC, SI and CL to NinjaTrader

NinjaTrader maintains a predefined database of many common instruments, and the local instrument database is updated from NinjaTrader’s server.

In most cases, manually creating GC, SI, or CL from scratch should not be necessary.

To open a chart:

Control Center → New → Chart

Search for the desired futures contract.

The symbol alone is not enough for standard futures because an expiry month needs to be selected.

For example, the platform may display a contract using a format similar to:

GC 12-26

SI 12-26

CL 11-26

The exact active contract changes over time.

Do not blindly copy an expiry from an old tutorial.

Choose the currently appropriate contract based on market activity, volume, your broker, and the normal rollover cycle.

NinjaTrader supports changing chart instruments directly using the instrument selector and contract month.

A useful workspace might contain:

Gold workspace

• GC chart
• MGC chart
• optional 1OZ monitoring

Silver workspace

• SI chart
• SIL or SIC chart

Oil workspace

• CL chart
• MCL chart

This allows comparison between benchmark and smaller products without repeatedly rebuilding windows.

Step 7: Build a Clean Multi-Market Workspace

Once the instruments are available, avoid immediately opening dozens of charts.

A clean workspace is easier to maintain and generally uses fewer resources.

One practical layout could include:

GC: one primary execution chart + one higher-timeframe chart
SI: one primary chart
CL: one primary chart
Market Analyzer: GC, MGC, SI, SIL, SIC, CL, MCL
SuperDOM: only for the instrument currently being actively traded

This is usually more efficient than keeping a SuperDOM and several highly detailed order-flow charts open for every instrument continuously.

If order flow is central to the strategy, resources can be added later.

Save the workspace once it is stable.

NinjaTrader workspaces preserve window layouts and platform configuration, but traders should still keep backups of important custom indicators, strategy source code, templates, and configuration files outside the VPS.

Step 8: Configure Real-Time and Historical Data Correctly

NinjaTrader can use more than one connection simultaneously.

For example, a trader could use one provider for real-time order routing and another source for historical data.

When multiple connections are active, NinjaTrader can use preferred connections for real-time and historical data separately. Connection order can also influence which feed is selected if preferences are not configured.

This matters because an apparently simple setup can behave unexpectedly when several providers are connected.

Suppose a trader expects real-time GC data from one provider but NinjaTrader is actually sourcing futures data from another connection that does not have the required entitlement.

The chart may appear delayed or fail to load even though the trading account itself is connected.

If using multiple providers, explicitly configure the preferred real-time futures connection and historical futures connection.

Then confirm data by watching the chart timestamps and market activity.

Step 9: Understand Futures Contract Rollovers

Gold, Silver, and Oil are futures contracts, not perpetual symbols.

They expire.

Trading activity moves from one contract month to another.

This is particularly important for CL, where active trading commonly shifts monthly.

If NinjaTrader remains pointed at an old contract after liquidity has migrated, the trader may see a chart that appears unusually quiet or a DOM with very little activity.

NinjaTrader provides a batch rollover function under:

Tools → Database Management → Rollover futures instruments

Eligible instruments can then be updated to the next expiry across open workspaces.

One important detail: NinjaScript strategies are not automatically rolled forward with the normal batch rollover process. NinjaTrader’s documentation says strategy instruments must be rolled manually.

That is extremely important for automated traders.

A chart may have been updated from one CL contract to the next while an automated strategy is still attached to the previous expiry.

Always verify:

• current contract month,
• chart instrument,
• SuperDOM instrument,
• strategy instrument,
• broker position,
• and open orders

after a rollover.

Step 10: Configure NinjaTrader for Reliable VPS Operation

The next stage is not about charts.

It is about making the platform behave properly when no one is watching it.

First, prevent unnecessary Windows sleep behavior.

A VPS normally does not use power management in the same way as a laptop, but verify that Windows is not configured to suspend important processes.

Second, decide whether NinjaTrader should connect automatically after startup.

Only enable automatic connection after confirming the credentials and connection behavior are reliable.

Third, understand what happens after a disconnect.

A trading connection can drop even when the VPS remains online.

NinjaTrader can reconnect, but the exact behavior of orders depends on the connectivity provider and order type.

This is especially important with Rithmic.

NinjaTrader’s documentation states that accepted or working Rithmic orders reside at the brokerage or exchange when supported, but OCO functionality is simulated locally on the PC for Rithmic.

That makes continuous platform availability particularly important for strategies that rely on locally simulated functionality.

It is a good example of why “my order is at the exchange” does not always mean every part of the trade-management logic can survive the local platform disappearing.

Before running a strategy unattended, understand where each order type, stop, target, OCO relationship, and simulated condition resides.

Step 11: Test GC, SI and CL in Simulation Before Going Live

A new VPS should not immediately become the live trading environment simply because NinjaTrader launches successfully.

Use Simulation first.

Open GC, SI, and CL.

Confirm that data arrives properly.

Create charts.

Open the DOM.

Submit simulated orders.

Cancel them.

Test stop and target behavior.

Switch between standard and Micro contracts.

Disconnect Remote Desktop.

Reconnect after several minutes and confirm NinjaTrader remains open.

Restart NinjaTrader and verify that connections and workspaces behave as expected.

Then test an actual Windows restart.

After reboot:

Does NinjaTrader launch?

Does the connection restore?

Does the workspace load?

Do strategies remain disabled or re-enable according to the intended configuration?

Can NinjaTrader reconcile account positions?

These tests reveal infrastructure problems before real money is involved.

Step 12: Set Up Automated Strategies Carefully

NinjaTrader is popular partly because NinjaScript allows automated strategies to run inside the desktop platform.

A VPS can make this more practical because the strategy is no longer dependent on a home PC.

But an always-on VPS does not automatically make an automated strategy safe.

Before relying on unattended execution, define what should happen when:

• NinjaTrader restarts,
• Windows reboots,
• the broker connection disconnects,
• market data becomes stale,
• an order is partially filled,
• the strategy and account position disagree,
• a contract rolls,
• CME enters maintenance,
• or a strategy throws an exception.

Position reconciliation is especially important.

Suppose a Gold strategy is long one MGC contract.

NinjaTrader closes unexpectedly.

The broker still has the position.

When NinjaTrader restarts, the strategy must correctly understand the real account state before issuing any new order.

Otherwise, software that thinks it is flat could accidentally create an additional position.

Always test strategy restart and synchronization behavior before unattended live use.

Step 13: Monitor More Than VPS Uptime

A provider can report the server as online while NinjaTrader itself has stopped receiving data.

That means VPS uptime and trading-system uptime are different things.

A serious monitoring checklist should include:

Server level

• CPU usage
• RAM usage
• disk space
• network connectivity
• Windows uptime

Platform level

• NinjaTrader process running
• broker connection status
• market-data freshness
• strategy state
• log errors
• order-rejection messages

Trading level

• account positions
• working orders
• expected vs actual strategy position
• current contract month

This distinction becomes more important as Gold and Silver products expand toward longer trading schedules.

1-Ounce Gold is already available 24/7 apart from scheduled maintenance.

CME scheduled 100-Ounce Silver for weekend expansion beginning September 11, 2026.

Traditional GC, MGC, SI, SIL, CL, and MCL continue to follow their normal futures-week schedules.

Longer market availability makes “is my application really healthy?” more important than simply checking whether Windows responds to Remote Desktop.

Why CPU, RAM and NVMe Matter for This Particular Setup

A combined Gold + Silver + Oil NinjaTrader workspace can create a meaningful workload.

Incoming ticks need to be processed.

Indicators recalculate.

DOM depth changes.

Historical bars remain in memory.

NinjaScript executes.

Logs and local databases update.

Additional tools may run alongside NinjaTrader.

This is why CPU, RAM, and storage should be viewed as separate performance layers.

CPU

CPU speed affects calculations and platform responsiveness.

High single-core performance is useful for chart-heavy and strategy-heavy workloads.

A high-clock Ryzen processor can therefore be more relevant to NinjaTrader than simply choosing the VPS with the highest advertised number of slow virtual CPUs.

RAM

RAM determines how comfortably several charts, datasets, indicators, and applications can coexist.

8 GB may work for a lightweight setup.

For GC, SI, and CL together, 16 GB is a more comfortable starting point.

For multiple order-flow workspaces or automated strategies, 24–32 GB may provide better headroom.

NVMe Storage

NVMe does not reduce the physical network distance to the broker.

It improves local tasks such as:

• NinjaTrader startup,
• historical-data access,
• local database work,
• log writing,
• strategy compilation,
• Market Replay files,
• and workspace loading.

Network

A futures platform does not normally need several gigabits per second of sustained bandwidth.

Quality matters more than raw capacity.

A stable, well-routed data-center connection with low packet loss is generally more valuable than a huge advertised port on a poor network route.

TradingVPS’s Chicago environment currently publishes test destinations for Rithmic, Tradovate, and Interactive Brokers, making it possible to test routes relevant to the actual trading stack.

Published latency is still not an execution guarantee.

Broker processing, routing, exchange conditions, order type, and liquidity all remain outside the VPS.

A Practical Chicago VPS Configuration for GC, SI and CL

For a trader who wants all three markets visible in NinjaTrader, a practical middle configuration could be:

Component	Suggested configuration
Operating system	Windows Server 2022
CPU	4 high-clock cores
RAM	16 GB
Storage	200–300 GB NVMe
IP	Dedicated IPv4
Location	Chicago
Platform	NinjaTrader 8
Markets	GC/MGC, SI/SIL/SIC, CL/MCL
Connectivity	Broker/data provider appropriate to the account
Monitoring	CPU, RAM, platform process, data/broker connection

This is not a universal requirement.

A single MGC chart with one simple indicator may need substantially less.

A setup containing multiple footprint charts, Market Replay databases, strategy optimizations, Bookmap, trade copiers, and several NinjaTrader instances may need much more.

Resource monitoring should determine when to scale.

If normal market activity regularly pushes CPU near maximum or RAM becomes almost completely occupied, increase resources before adding more automation.

Frequently Asked Questions About NinjaTrader on a Chicago VPS

Final Thoughts: Building a Reliable NinjaTrader Setup for Gold, Silver & Oil

Setting up NinjaTrader for Gold, Silver, and Oil futures on a Chicago VPS is not complicated, but a reliable configuration requires more than installing the platform and opening three charts.

Start with appropriate Windows infrastructure.

Choose enough CPU and RAM for the real workload rather than the smallest server that can technically launch NinjaTrader.

Use NVMe storage for responsive local platform operations.

Connect the broker and data feed correctly.

Confirm exchange data entitlements.

Add the correct GC, SI, and CL contract months.

Build a clean workspace.

Understand how NinjaTrader chooses between multiple data connections.

Manage contract rollover carefully.

And test every part of the environment in Simulation before relying on it for live trading.

For futures, Chicago is a particularly logical server region because CME’s current Aurora facility houses the matching engines for Globex products.

But location is only one part of the system.

A fast Chicago connection does not help if NinjaTrader is overloaded by too many charts.

A powerful CPU does not help if the broker connection is configured incorrectly.

99.99% server availability does not mean the platform is connected 99.99% of the time.

And a persistent VPS does not guarantee that an automated strategy will recover correctly after a connection interruption.

The most reliable configuration treats the trading stack as several layers:

hardware → Windows → NinjaTrader → market data → broker connection → strategy/order management → monitoring

Every layer needs to work.

For many multi-market NinjaTrader traders, a good starting point is a high-clock 4-core Windows VPS with 16 GB RAM, NVMe storage, a dedicated IP, and a Chicago location.

TradingVPS currently offers that type of configuration through its Chicago Ryzen lineup, using AMD Ryzen 9 9950X CPU resources, DDR5-5200 memory, NVMe storage, dedicated IPv4, and Windows Server 2022.

That hardware is not important because of the brand name.

It is useful because NinjaTrader benefits from fast processing, enough memory headroom, responsive storage, stable network connectivity, and continuous availability.

Once NinjaTrader is installed, the final step is testing the complete workflow under realistic conditions.

Watch GC during a busy macro session.

Watch SI when metals volatility rises.

Watch CL around active energy-market periods.

Monitor CPU and RAM.

Confirm connection stability.

Verify order behavior.

Test a disconnect.

Test a Windows restart.

Test a futures rollover.

If an automated strategy is involved, confirm exactly what happens to existing positions and working orders when the platform disappears and reconnects.

The goal is not simply to have NinjaTrader running on a VPS.

The goal is to build a NinjaTrader environment that you understand well enough to know how it behaves when something goes wrong.

That is what turns a remote Windows server into a useful futures trading infrastructure setup.

This article is provided for general technical and educational purposes and does not constitute financial, investment, legal, or trading advice. Futures involve substantial risk. Contract specifications, trading hours, broker support, platform features, margin requirements, and connectivity behavior can change. Always verify current information with NinjaTrader, your broker, data provider, and CME Group before trading.