Open an account with almost any retail futures broker or funded-trader programme and, somewhere in the onboarding, you will be asked to choose between Rithmic and CQG. Most traders pick one semi-randomly, or take whichever the firm defaults to, and never revisit the decision. That is understandable — the choice is presented as a technical footnote — but it is not a footnote. Rithmic and CQG make different engineering trade-offs, and those trade-offs interact directly with how you host your platform.
Neither is “better.” They are optimised for different things, and the right answer depends on whether you are scalping the ES off a DOM or running swing positions across a dozen global markets. Here is the distinction that matters, and what each implies for your VPS.
What These Things Actually Are
Neither Rithmic nor CQG is a broker. Both are infrastructure providers that sit between your trading platform and the exchange, supplying two things: market data going one way, and order routing going the other. Your broker — AMP, NinjaTrader Brokerage, Ironbeam, Optimus, or the prop firm running your evaluation — clears the trades. Rithmic or CQG carries them.
This is why the same broker can offer both, and why the same prop firm can hand you a Rithmic login for one account and a CQG login for another. They are pipes, not counterparties.
- Rithmic is a Chicago-based technology provider best known for low-latency, tick-by-tick delivery. Its front ends are R|Trader and R|Trader Pro, and its API (R|API+) underpins a great deal of retail futures automation.
- CQG is a longer-established market-data and routing house with much broader instrument coverage — 75+ global exchanges and data sources — and its own platform family in CQG Desktop, QTrader and Integrated Client.
The Core Trade-Off: Raw Ticks vs Smart Compression
The single most important difference is what happens to the data stream between the exchange and your chart.
Rithmic pushes data through with minimal processing. You get the tick sequence as close to unmodified as a retail feed reasonably provides. For an order-flow or footprint trader, that fidelity is the entire point — a volume-profile or delta calculation built on a compressed stream is measuring something slightly different from what actually happened.
CQG applies smart compression — consolidating updates where the information content is redundant — and aggregates across a very large number of global sources. The result is a lighter, more bandwidth-efficient stream that is easier to deliver reliably over imperfect connections, and cleaner-looking charts for traders who are not counting individual prints.
📊 Key Stat: In liquid CME products like ES and NQ during an active session, price moves one to two ticks per second. A 200ms feed delay therefore means your chart is showing you prices that are roughly four to eight ticks stale. For a swing trader that is irrelevant. For a scalper working a one-tick target off the DOM, it is the whole trade.
That stat cuts both ways, and it is the reason hosting matters more than feed choice for most people: a colocated Chicago VPS on CQG will beat a residential connection on Rithmic every time.
Rithmic: Who It Suits and How to Host It
The Profile
Rithmic is the right pick if you are a DOM scalper, order-flow trader, or automation developer working primarily in CME products. Bookmap, Jigsaw, ATAS and similar order-flow tools want the least-processed stream available, and Rithmic is the standard answer among that crowd. The R|API+ is also the most common integration path for custom retail futures automation.
Prop firms lean on Rithmic heavily — Earn2Trade, Apex, Topstep and others route evaluations through it — partly for latency and partly because Rithmic’s account-management layer supports the risk controls those programmes need.
VPS Implications
- Location is non-negotiable: Chicago. Rithmic’s infrastructure is concentrated in the Chicago metro because CME’s matching engine is in Aurora, Illinois. Hosting a Rithmic connection in New York throws away roughly 15–20ms of round trip for no reason; hosting it in Europe throws away 90ms.
- Bandwidth and CPU both matter. An unconflated tick stream is more data arriving more often, and every tick has to be processed by your platform. During a CPI release or an RTH open, tick rates spike by an order of magnitude, and an undersized instance falls behind exactly when you need it not to.
- Jitter is the silent killer. A connection that averages 5ms but periodically stalls for 300ms produces a chart that catches up in a lurch. Order-flow tools that render every print are the most sensitive applications in retail trading to this failure mode.
⚠️ Warning: An order-flow platform starved of CPU does not throw an error — it keeps drawing, just behind real time. You will be looking at a confident, detailed, beautifully rendered picture of the market as it existed eight seconds ago. This is the most dangerous resource-contention failure in futures trading because it is completely silent.
CQG: Who It Suits and How to Host It
The Profile
CQG is the better fit if you trade broadly rather than deeply — multiple exchanges, international products, agricultural or energy contracts outside the CME index complex — or if you value setup simplicity and platform breadth over the last few milliseconds. Its coverage across 75+ global sources is genuinely wider than Rithmic’s, and its integration story across TradingView, web platforms, Mac and mobile is more mature.
Swing traders, spread traders, and anyone whose strategy operates on bars rather than prints will not perceive a difference in execution quality from the feed choice, and will appreciate the easier configuration.
VPS Implications
- Chicago is still the right default for CME-heavy trading, since CQG maintains Chicago-area infrastructure and the exchange is in Aurora regardless of which pipe you use. If your book is genuinely global — European energy, Asian indices — the calculus gets more nuanced, but for most retail traders CME dominates the volume and Chicago wins.
- Lower resource ceiling. Compressed data means fewer updates to process, so a CQG-based setup is typically less CPU-hungry than the equivalent Rithmic one at the same tick rate. In practice this means CQG traders can often run comfortably one plan tier lower.
- Charting stability is the selling point. If your platform choice is CQG Desktop or QTrader rather than a heavyweight order-flow tool, the resource profile is modest.
💡 Tip: If you are on a funded-trader evaluation and the firm offers both, take the feed the firm defaults to for your first evaluation. Introducing a non-default configuration variable during a paid, rule-bound assessment is a bad time to be debugging connection profiles. Optimise the feed choice once you are funded.
The Comparison, Condensed
| Rithmic | CQG | |
|---|---|---|
| Data philosophy | Minimal processing, tick-by-tick fidelity | Smart compression, consolidated across sources |
| Instrument coverage | CME-centric, deep | 75+ global exchanges and sources, broad |
| Best for | DOM scalping, order flow, automation | Swing, spread, multi-market, simpler setups |
| Front ends | R|Trader, R|Trader Pro, R|API+ | CQG Desktop, QTrader, Integrated Client |
| Platform reach | NinjaTrader, Sierra Chart, MultiCharts, Quantower, Bookmap, ATAS | The above plus stronger web, Mac and mobile support |
| VPS location | Chicago | Chicago (CME-centric); depends if genuinely global |
| Typical VPS tier | Pro or Scaling | Core or Pro |
| Sensitive to jitter | Very | Moderately |
The Part Most Traders Get Backwards
Here is the uncomfortable arithmetic. The measurable latency difference between Rithmic and CQG, hosted identically, is small — a few milliseconds in most retail configurations. The latency difference between any feed on a Chicago VPS and the same feed on home broadband from a different time zone is 30ms to 150ms.
The hosting decision is one to two orders of magnitude more consequential than the feed decision. Traders routinely spend weeks in forum threads litigating Rithmic vs CQG while routing both through a residential connection 900 miles from Aurora. That is optimising the wrong variable.
✅ Best Practice: Fix the geography first, then argue about the feed. Get onto a Chicago instance with dedicated cores, run your actual platform through a couple of live sessions, and only then evaluate whether the feed itself is a constraint. Most traders discover it never was. See dedicated cores vs shared vCPU for why the core type matters here.
🚀 Try FXVPS free for $1.99 — get 7 days on the Core VPS risk-free and test your feed from Chicago. No long-term commitment, cancel anytime.
Recommended FXVPS Plan by Feed and Platform
Core Plan ($29/mo — 2GB RAM, 1 vCPU) covers CQG on a light front end — CQG Desktop, QTrader, or R|Trader Pro on Rithmic if you trade one or two instruments off a DOM without heavy charting. Sierra Chart on either feed also fits comfortably here because of how efficient it is.
Pro Plan ($39/mo — 4GB RAM, 2 vCPUs) is the realistic default for either feed with a proper platform. NinjaTrader 8 with a multi-chart workspace, MultiCharts, or Quantower on Rithmic all want 4GB and two cores. Take this tier if you are running Rithmic with any real charting load.
Scaling Plan ($79/mo — 8GB RAM, 4 vCPUs) is where order-flow traders belong. Bookmap, ATAS, Jigsaw or a volumetric NinjaTrader workspace on a Rithmic feed processes enormous update volumes, and this is the tier that keeps rendering in real time when the market gets busy. It is also the right choice for running multiple accounts or feeds simultaneously.
Setting Up Either Feed on a VPS
-
Provision in Chicago. Both feeds and the exchange are in that metro. Nothing else on this list matters as much.
-
Connect via RDP and install your platform from the vendor directly, not a mirror.
-
Enter the credentials your broker or prop firm issued for that specific feed. Rithmic and CQG logins are not interchangeable, and a Rithmic login for one firm will not work with another. Select the correct gateway when prompted — most connection errors on day one are a wrong-gateway problem.
-
Connect to sim or demo first. Confirm data flows, charts populate historically, and orders are accepted before touching a live account.
-
Watch the feed during a real open, not a quiet afternoon. Load your actual workspace and observe it through an RTH open or a scheduled economic release. If charts lag or the DOM stutters, size up before it costs you a trade.
-
Confirm stops rest at the exchange. Some platform and feed combinations default to locally-simulated stops. A local stop does not exist if the platform is not running. Verify this explicitly.
-
Configure auto-start, auto-login and NTP time sync, and schedule Windows updates outside market hours. See our Windows updates guide and NTP synchronisation guide.
Frequently Asked Questions
Is Rithmic actually faster than CQG?
In tick-by-tick delivery, Rithmic’s minimal-processing approach generally edges out CQG’s compressed stream, and Rithmic’s Chicago concentration helps. But the gap is small relative to the gap between good and bad hosting. If you are on home broadband, the feed choice is not your bottleneck.
Which feed do prop firms use?
Rithmic is the most common for futures evaluation programmes — Earn2Trade, Apex and Topstep among others route through it — partly for latency and partly for the account-level risk controls it supports. Some firms offer CQG or Tradovate as alternatives. Check what your specific programme issues.
Can I run both feeds on the same VPS?
Yes. Traders holding accounts at several firms frequently end up with one of each. Budget resources for the sum of both platforms and both data streams, which in practice means the Pro plan minimum and Scaling if either setup is substantial.
Does the feed choice affect my fills?
Indirectly. The feed carries your order routing as well as your data, so routing latency is part of it — but the dominant term for a retail trader is the network distance between your machine and Chicago. Fix that first.
Do I need a Chicago VPS if I trade European or Asian futures?
If a genuine majority of your volume is on Eurex, ICE Europe or an Asian exchange, the geography question is worth reopening — CQG’s global coverage exists precisely for that trader. For the large majority of retail futures traders, CME products dominate the volume and Chicago is correct.
Which feed should I use with Sierra Chart?
Sierra Chart supports both, and also offers its own Denali data feed with Teton order routing, whose servers are colocated in Aurora with the CME matching engine. If you are committed to Sierra Chart, the native Denali and Teton combination is worth evaluating alongside Rithmic and CQG.
Related Reading
- Why Chicago Matters for Futures Traders — the geography that decides everything else
- Best VPS for AMP Futures — a broker offering both feeds and 50+ platforms
- Best VPS for Earn2Trade — a Rithmic-routed evaluation programme
- Latency, Jitter and Packet Loss on a Forex VPS — why variance matters more than average
- NinjaTrader 8 VPS Setup Guide — the most common platform for both feeds
- Dedicated Cores vs Shared vCPU — the spec that keeps order-flow charts in real time