FXVPS
Get Started
vps sierra-chart futures denali teton cme chicago

Sierra Chart on a VPS: Complete Setup Guide for Futures and FX Traders

person
FXVPS
Share
Sierra Chart on a VPS: Complete Setup Guide for Futures and FX Traders

Sierra Chart is the platform serious futures traders end up on after they have tried the pretty ones. It is written in C++, it looks like it was designed in 2004, and it will run a twenty-chart workspace with full order-flow rendering on hardware that makes NinjaTrader 8 stall. That efficiency is not an accident — it is the product of a development philosophy that treats every millisecond of rendering time and every megabyte of memory as something to be argued over.

It is also Windows-only. Mac and Linux traders reach it through Parallels, VMware Fusion, or — far more commonly and far more sensibly — a Windows VPS. And since Sierra Chart’s own Teton order-routing servers are colocated in Aurora, Illinois with the CME matching engine, where you host it turns out to matter as much as how.

This is the complete setup guide.

Why Sierra Chart and a VPS Fit Together Unusually Well

Most trading platforms are hosted on a VPS despite being resource-hungry. Sierra Chart is hosted on a VPS because the pairing is genuinely optimal:

  • It is Windows-native and Windows-only. If you are on macOS or Linux, a VPS is the cleanest path — better than a local virtualisation layer, because it also solves the location and uptime problems at the same time.
  • It is light enough that a modest instance is genuinely sufficient. Where NinjaTrader users are forced into 4GB and two cores, a Sierra Chart trader with a reasonable workspace often runs comfortably on 2GB and one core. The VPS is cheap precisely because the platform is well-built.
  • Its routing terminates in Aurora. Sierra Chart’s Teton service maintains order-routing servers colocated with the CME order-matching computers. Hosting your client in Chicago rather than at home is the difference between a few milliseconds and several tens of them.
  • It holds persistent data connections. Denali, CQG, Rithmic and Interactive Brokers all stream continuously. Home broadband drops connections for boring reasons; a datacenter connection does not.

📊 Key Stat: Sierra Chart with a typical eight-chart workspace and standard studies commonly runs in 400–800MB of RAM. The equivalent NinjaTrader 8 workspace routinely uses 1.5–2.5GB. That difference is why Sierra Chart traders can often run one plan tier lower than users of any comparable platform.

Understanding the Data Feed and Routing Options

Sierra Chart’s service-package structure confuses newcomers, so it is worth being explicit about what the pieces are.

Denali Exchange Data Feed

Denali is Sierra Chart’s own real-time exchange data feed. It integrates with all supported trading services, and provides real-time data for any symbol the exchange publishes, independently of which symbol naming your trading service happens to use. For most Sierra Chart users trading CME products, Denali is the straightforward answer for market data.

Teton Order Routing

Teton is Sierra Chart’s direct order-routing service for CME Group markets. Its servers are located in Aurora, Illinois, colocated with the CME order-matching computers. Teton can be used with any service package, including the base packages — it is not gated behind the highest tier.

The Aurora colocation is the specific fact that makes Chicago the right VPS choice for a Teton user. Your client talks to Teton’s Aurora servers; putting your client in Chicago rather than in your living room removes most of the network distance in that path.

Third-Party Feeds and Routing

Sierra Chart also connects to CQG, Rithmic, Interactive Brokers and others, both for data and for routing, depending on your broker. If your broker requires you to route through their Rithmic or CQG relationship, that works — Sierra Chart is a first-class client for both. Our Rithmic vs CQG comparison covers how those two differ and what each implies for sizing.

💡 Tip: Sort out your service package, data feed and routing service before you provision the VPS. Sierra Chart’s package structure gates certain features — the exact combination determines whether you can use the studies and order types you are planning around. Discovering a gap after you have built a workspace is a bad afternoon.

Choosing Your VPS Location

The answer follows the market you actually trade:

  • Chicago — for CME Group futures (ES, NQ, CL, GC, ZB, 6E and the rest). This is where the exchange’s matching engine lives, where Teton’s routing servers are, and where Rithmic and CQG concentrate their infrastructure. If you are a futures trader, this is your location and there is no second choice worth discussing.
  • New York — if you use Sierra Chart primarily for spot FX through a broker whose servers sit in Equinix NY4, or for US equities and equity options through Interactive Brokers.
  • London — if you trade FX against an LD4-hosted broker, or European instruments where the liquidity centre of gravity is European.

⚠️ Warning: Chicago and New York are different execution geographies serving different markets, separated by roughly 700 miles of network distance and 15–20ms of round trip. Picking New York for CME futures because it “feels closer to finance” is a real and common mistake. Pick the metro your exchange is in, not the one with the better reputation.

Sizing Your Instance

Sierra Chart’s efficiency means the honest answer is “less than you expect,” but the range across use cases is still wide.

Core Plan ($29/mo — 2GB RAM, 1 vCPU) genuinely works for a large share of Sierra Chart users. A workspace of five to ten charts with standard studies — moving averages, volume, VWAP, a DOM — fits comfortably. This is the plan for a trader running one or two instruments with conventional charting, and it is not a compromise choice the way it would be on a heavier platform.

Pro Plan ($39/mo — 4GB RAM, 2 vCPUs) is the right pick once you add complexity: a larger workspace, multiple instruments, custom ACSIL studies, or Sierra Chart running alongside another application. Two cores also help meaningfully because Sierra Chart can parallelise some chart processing, and it keeps your studies from competing with the data-feed thread.

Scaling Plan ($79/mo — 8GB RAM, 4 vCPUs) is for the heavy end: large volumetric and footprint workspaces, market-depth historical recording (which is genuinely storage- and memory-intensive), automated ACSIL trading systems, or multiple Sierra Chart instances against different brokers.

✅ Best Practice: If you record market depth data — Sierra Chart’s depth-of-market historical recording is one of the platform’s genuinely distinctive features — budget for both RAM and disk deliberately. Full-depth recording on active instruments generates substantial data volume continuously, and running out of disk mid-session is a self-inflicted outage.

🚀 Try FXVPS free for $1.99 — get 7 days on the Core VPS risk-free and see how little Sierra Chart actually needs. No long-term commitment, cancel anytime.

Setting Up Sierra Chart on Your FXVPS

  1. Provision in the right metro. Chicago for CME futures; New York or London if you are using Sierra Chart against an FX broker in NY4 or LD4. Everything else on this list is secondary to this step.

  2. Connect via RDP using the credentials FXVPS issues. Microsoft Remote Desktop works from Windows, macOS, iOS and Android — which is how Mac users end up running a Windows-only platform without owning a Windows machine.

  3. Download Sierra Chart from sierrachart.com directly. Install to the default path unless you have a specific reason not to; a nonstandard install directory complicates support and some third-party study installers.

  4. Log in with your Sierra Chart account and let it download the current version. Sierra Chart updates frequently, and running a stale build is a common cause of connection problems with data services.

  5. Configure your data feed. Under Global Settings → Data/Trade Service Settings, select your service — Denali, CQG, Rithmic or your broker’s specific option — and enter the credentials issued for that service. These are service-specific; a Rithmic login from one broker will not authenticate against another.

  6. Configure order routing. If you are using Teton for CME routing, enable it and confirm your broker relationship supports it. Otherwise select the routing your broker requires.

  7. Verify on sim first. Sierra Chart has an excellent simulation mode. Confirm data is streaming, historical charts populate correctly, and simulated orders behave as expected before you enable live trading. Sierra Chart’s trade-mode safety toggle exists for a reason — leave it in sim until you have verified everything.

  8. Build or import your workspace. If you are migrating from a local install, copy your Data folder and your chartbook (.Cht) files across via RDP drive redirection or a cloud sync folder. This preserves your studies, settings and layouts rather than rebuilding them by hand.

  9. Set Sierra Chart to auto-start. Place a shortcut in the Windows Startup folder and enable auto-login on the Windows account so a reboot restores your environment unattended.

  10. Confirm your stops rest at the exchange. Sierra Chart can simulate stops locally, which is useful in some contexts and dangerous in others — a locally-held stop does not exist if the application is not running. Verify explicitly which mode each of your order types uses.

  11. Synchronise the clock via NTP. Sierra Chart timestamps everything, and session boundaries, the CME daily maintenance break and any time-gated study logic all depend on an accurate clock. See our time synchronisation guide.

  12. Schedule Windows updates outside market hours. An unscheduled reboot during the RTH open is avoidable. Our Windows updates guide covers the configuration.

Common Problems and Their Causes

Charts lag or stutter during volatile opens. Almost always CPU contention rather than network. Watch Task Manager during the next open; if a core is pinned, move up a plan tier.

Data service disconnects repeatedly. Check that you are running a current Sierra Chart build, and confirm your service credentials have not expired or been reissued. Persistent disconnects on a datacenter connection usually point at credentials or version, not the network.

Historical charts populate slowly on first load. Expected behaviour when downloading a large history for the first time. Sierra Chart caches locally, so subsequent loads are fast. Give it a full session before judging.

The application starts but does not connect after a reboot. Sierra Chart may start in a disconnected state deliberately. Configure it to auto-connect on startup, and verify the behaviour by rebooting the VPS once during a weekend and watching what happens.

Running out of disk with depth recording enabled. Full market-depth recording accumulates continuously. Set a retention policy or budget for storage.

Why FXVPS for Sierra Chart

Sierra Chart traders are, as a group, unusually resistant to being sold things. The platform’s whole appeal is that it does not waste your resources, so the pitch cannot be “buy more hardware.”

The pitch is geography. Sierra Chart’s Teton routing servers are in Aurora with the CME matching engine, and no amount of platform efficiency shortens the 700 miles between Chicago and the US East Coast, or the Atlantic between Chicago and London. FXVPS runs dedicated hardware in Chicago with pre-configured environments for Sierra Chart, NinjaTrader 8 and MultiCharts, on dedicated CPU cores rather than oversubscribed shared vCPU. Compare plans at /pricing/ or test it on a $1.99 seven-day trial.

Frequently Asked Questions

Does Sierra Chart run on Mac or Linux?

Not natively — it is a Windows application. Mac and Linux traders run it through Parallels, VMware Fusion, or a Windows VPS. The VPS route is usually better, because it also solves latency and uptime rather than just compatibility.

What VPS location should I pick for Sierra Chart?

Chicago if you trade CME futures, which is the majority use case. Sierra Chart’s Teton order-routing servers are colocated in Aurora, Illinois with the CME matching computers. Choose New York or London instead only if you are using Sierra Chart against an FX broker hosted in NY4 or LD4.

How much RAM does Sierra Chart need?

Less than most people budget. A typical eight-chart workspace with standard studies commonly runs in 400–800MB, so the 2GB Core plan is genuinely adequate for many traders. Move to 4GB if you run large workspaces, custom ACSIL studies, or full volumetric and footprint charts.

Can I use Rithmic or CQG with Sierra Chart instead of Denali and Teton?

Yes. Sierra Chart is a first-class client for both, as well as Interactive Brokers and others. Which you use is usually dictated by your broker relationship. See our Rithmic vs CQG comparison for how the two differ.

Will my chartbooks and studies transfer to a VPS?

Yes. Copy your Data folder and .Cht chartbook files from your local installation to the VPS, and Sierra Chart picks up your layouts, studies and settings. RDP drive redirection makes this a drag-and-drop operation.

Can I run Sierra Chart and another platform on the same VPS?

Yes, and it is a common setup — Sierra Chart for charting with a separate platform for order entry or automation. Size for the sum of both, which usually means the Pro plan minimum.

What happens to my orders if the VPS reboots?

Orders resting at the exchange survive; anything Sierra Chart is simulating locally does not. This is the single most important thing to verify in your configuration, because a locally-simulated stop provides exactly zero protection during an outage.