CQG vs Rithmic vs dxFeed: Best Futures Broker Automation Feeds

Stop losing ticks to slow data. Compare CQG, Rithmic, and dxFeed to find the fastest, most cost-effective data feed for your automated futures trading strategy.

CQG, Rithmic, and dxFeed are the three dominant data feed providers for futures broker automation. CQG offers the widest broker compatibility and institutional-grade market data. Rithmic provides the lowest latency for order routing at 3-5ms. dxFeed delivers cost-effective tick data suitable for retail automated strategies. Your choice depends on your broker, strategy speed requirements, and budget.

Key Takeaways

CQG connects to 40+ futures brokers and averages 5-10ms data latency, making it the most widely supported feed for automation platforms
Rithmic's direct exchange connections deliver 3-5ms latency with full depth-of-market data, preferred by scalpers and high-frequency strategies
dxFeed costs roughly 30-50% less than CQG or Rithmic for equivalent market data packages and supports most retail automation needs
Data feed selection directly affects order routing speed, fill quality, and whether your broker even supports your automation platform
Switching data feeds mid-strategy can create tick discrepancies that break backtested results, so choose carefully before going live

What Are Futures Data Feeds and Why Do They Matter?

A futures data feed is the real-time stream of price, volume, and order book information that flows from exchanges like CME Group to your trading platform. Every automated trading decision your system makes depends on this data arriving accurately and on time. A delayed or inaccurate feed means your algorithm acts on stale prices, which directly translates to worse fills and unexpected slippage.

Data Feed: A real-time connection that delivers price quotes, trade prints, and depth-of-market information from futures exchanges to your trading software. The quality of this feed determines whether your automation platform sees the same prices the exchange is actually trading at.

When comparing a futures broker data feed like CQG, Rithmic, or dxFeed, you're evaluating three things: latency (how fast data arrives), accuracy (whether ticks are complete and sequenced correctly), and compatibility (whether your broker and platform support it). For traders running automated strategies through TradingView automation setups, the data feed also affects how closely your chart-based signals match actual execution prices.

Here's the thing most traders overlook: your data feed and your order routing feed don't have to be the same provider. Some brokers use CQG for market data but Rithmic for order execution, or vice versa. This matters because latency between your data feed and your order feed can create discrepancies between what your strategy sees and what price you actually get filled at.

CQG vs Rithmic vs dxFeed: Quick Comparison

The three major futures data feed providers each target different trader profiles. Here's how they compare across the metrics that matter most for automated trading infrastructure setup.

FeatureCQGRithmicdxFeedTypical Data Latency5-10ms3-5ms8-15msBroker Compatibility40+ brokers25+ brokers15+ brokersDepth of Market (DOM)10 levels standardFull depth available10 levels standardMonthly Data Cost$10-75/mo (broker dependent)$15-80/mo (broker dependent)$0-25/mo (often bundled)CME Exchange Fees$3-14/mo per exchange$3-14/mo per exchange$3-14/mo per exchangeAPI QualityCQG Integrated Client, FIXR | Protocol APIREST, WebSocketBest ForBroad compatibility, institutional useLow-latency scalping, DOM tradingCost-conscious retail tradersHistorical DataYes (additional cost)Yes (included with some brokers)Yes (extensive archive)Uptime (reported)99.9%+99.9%+99.5%+

CME exchange fees apply regardless of which data feed provider you use. Those fees ($3-14 per month per exchange for non-professional traders) go directly to CME Group, NYMEX, COMEX, or CBOT. The data feed provider fee sits on top of exchange fees [1].

CQG: The Institutional Standard

CQG (Continuum) is the most widely supported data feed in the futures industry, connecting to over 40 brokers and serving as the default feed for many retail platforms including TradeStation and several NinjaTrader configurations. If your broker supports CQG, your broker integration for automation will likely work without extra configuration.

CQG operates three tiers of service. CQG Integrated Client is the full charting and trading platform, primarily used by institutional desks. CQG QTrader is the mid-tier product with advanced charting. CQG Continuum is the data and routing API that most retail brokers connect through. When your broker says they "use CQG," they typically mean Continuum handles the data feed and order routing behind the scenes.

CQG Continuum: An API-level data and order routing service that brokers integrate into their platforms. Traders typically don't interact with it directly but benefit from its exchange connectivity and data normalization.

For automated strategies, CQG's main advantage is reliability and compatibility. The data is clean, timestamps are accurate, and most automation platforms have pre-built CQG connections. The tradeoff is that CQG's latency runs 5-10ms in typical conditions, which is fine for swing automation and most intraday strategies but may cost you on ultra-fast scalping entries. According to CQG's own technical documentation, their hosted infrastructure processes data at sub-millisecond speeds internally, but last-mile delivery to your platform adds the remaining latency [2].

Rithmic: Built for Speed

Rithmic delivers the lowest data latency among the three providers, averaging 3-5ms for market data delivery and order acknowledgment. It connects directly to CME's co-located servers, and many prop firms and active day traders prefer Rithmic specifically for its order routing speed and full depth-of-market data.

Where CQG dominates broker compatibility, Rithmic focuses on execution quality. The R | Protocol API gives developers raw access to order flow data, time and sales, and full market depth without the abstraction layers that other feeds add. For traders building or using broker API futures trading connections, Rithmic's protocol provides more granular control over order types and routing preferences.

Rithmic is the default data feed for several popular broker-platform combinations: NinjaTrader with AMP Futures, for example, commonly routes through Rithmic. Prop firms like Topstep, Apex Trader Funding, and several others use Rithmic infrastructure for their evaluation and funded accounts. If you're running prop firm automation, there's a good chance you're already on Rithmic whether you realize it or not.

The downside: Rithmic's broker list is smaller than CQG's, and some traders report that Rithmic's data connections can be more sensitive to network issues. If your internet connection has jitter or packet loss, Rithmic's tight tolerances mean you may experience more disconnects than with CQG's more forgiving protocol [3].

dxFeed: The Budget-Friendly Option

dxFeed offers market data at a lower cost than CQG or Rithmic, often bundled into broker packages at no additional charge. TradingView uses dxFeed as one of its data sources for futures charting, which means many traders already view dxFeed data without knowing it.

dxFeed: A market data provider that aggregates exchange data and delivers it through REST and WebSocket APIs. Originally strong in equities and options, dxFeed has expanded into futures data for retail and mid-tier institutional clients.

dxFeed's latency runs 8-15ms in typical conditions, which places it behind CQG and Rithmic for raw speed. For strategies that trade on 1-minute bars or longer, this difference won't affect performance meaningfully. For tick-by-tick scalping strategies running on ES or NQ futures, the extra 5-10ms of latency compared to Rithmic can mean the difference between getting filled at your target price or one tick worse.

The historical data offering is where dxFeed stands out. Their archive includes tick-level data going back years for many futures contracts, and access is priced lower than comparable CQG or Rithmic historical data packages. If your backtesting workflow requires extensive historical tick data, dxFeed may save you hundreds of dollars annually.

Broker support for dxFeed is more limited in the futures space. TastyTrade (formerly Tastyworks) and a few other brokers use dxFeed, but it's less common among the brokers that cater specifically to futures automation. Check your broker's supported data feeds before assuming dxFeed will work with your setup.

How Do You Choose the Right Data Feed for Your Strategy?

Your data feed choice should match three things: your broker, your strategy's time sensitivity, and your budget. In many cases, your broker will narrow the choice to one or two options automatically.

If your broker only supports one feed: The decision is made. Most brokers connect through either CQG or Rithmic. Switching data feeds usually means switching brokers, which involves account transfers, new margin agreements, and potential downtime. Don't underestimate the friction involved.

If your broker supports multiple feeds: Match the feed to your strategy type.

Scalping (under 2-minute holds): Rithmic. The 3-5ms latency and full DOM data give you the best chance at price-sensitive fills on ES and NQ. Execution quality matters more than data cost when you're targeting 2-4 ticks of profit per trade.
Intraday swing (5-minute to 4-hour holds): CQG or Rithmic. At this timeframe, 5-10ms vs 3-5ms latency rarely affects outcomes. Choose based on broker compatibility and cost.
Overnight/multi-day automation: Any of the three. When your hold time is measured in hours or days, data feed latency is irrelevant to fill quality. Choose the cheapest option your broker supports.

For traders automating TradingView webhooks to broker execution, the data feed powering your chart (often dxFeed through TradingView) may differ from the data feed your broker uses for execution. This is normal and usually not a problem, but be aware that slight tick differences between feeds can cause your TradingView alert to fire at a slightly different price than what your broker sees. The difference is typically 1 tick or less on liquid contracts like ES.

Which Brokers Support Which Data Feeds?

Broker connectivity automation starts with knowing which data feed your broker uses. Here's a breakdown of common futures brokers and their data feed support as of 2025.

BrokerCQGRithmicdxFeedAMP FuturesYesYesNoNinjaTrader BrokerageYesYesNoTradeStationYes (default)NoNoTradovateYes (CQG routing)NoNoInteractive BrokersNo (proprietary)NoNoTastyTradeNoNoYesIronbeamYesYesNoOptimus FuturesYesYesNoEdge ClearYesYesNo

Note: Interactive Brokers uses a proprietary data feed and API. It doesn't fit neatly into the CQG/Rithmic/dxFeed comparison, but it's worth mentioning because it's one of the most popular futures brokers. If you're on IB, data feed selection isn't really a choice you get to make.

Some brokers like AMP Futures let you choose between CQG and Rithmic when you open your account. This is a genuine advantage for futures broker comparison automation because you can test both feeds in a demo environment before committing. AMP even lets you run multiple platform connections simultaneously, so you could have NinjaTrader on Rithmic and a separate CQG connection for a different tool [4].

Data Feed Mistakes That Break Automated Strategies

Three common data feed errors cause the most problems for automated futures traders:

1. Backtesting on one feed, trading live on another. CQG, Rithmic, and dxFeed don't always report identical tick sequences for the same contract. Aggregation differences, timestamp precision, and how each feed handles the bid/ask at fast market conditions mean your backtest results on dxFeed historical data won't perfectly match live execution on Rithmic. The discrepancy is usually small (1-2 ticks), but for tight scalping strategies, it compounds. Always forward test on the same feed you'll trade live.

2. Ignoring exchange fee structures. CME Group charges non-professional traders around $3-14 per month per exchange for real-time data. If you trade ES (CME), NQ (CME), CL (NYMEX), and GC (COMEX), you're paying for four separate exchange data subscriptions regardless of your data feed provider. Traders new to futures sometimes see a "$0 data fee" from their broker and don't realize exchange fees still apply [1].

3. Not testing data feed reliability during high-volatility events. FOMC announcements (8x per year, 2:00 PM ET) and NFP releases (first Friday monthly, 8:30 AM ET) push extreme volume through data feeds. All three providers have experienced brief data delays during these events. If your strategy trades these windows, test your specific broker-feed combination during at least one live event before sizing up. A platform like ClearEdge Trading that connects TradingView alerts to broker execution can only be as fast as the underlying data feed allows.

Frequently Asked Questions

1. Can I use CQG data with a Rithmic broker account?

Not directly. Your data feed is tied to your broker's supported connections. If your broker uses Rithmic for order routing, your market data typically comes through Rithmic as well. Some traders use a separate CQG charting subscription alongside a Rithmic broker, but this adds cost and doesn't improve execution speed.

2. Does the data feed affect my commission rates?

Indirectly, yes. Some brokers charge different commission rates depending on the data feed and platform you select. AMP Futures, for example, lists different per-contract rates for CQG vs Rithmic connections. Always check the all-in cost including data fees, exchange fees, and commissions together.

3. Which data feed has the best uptime for automated trading?

CQG and Rithmic both report 99.9%+ uptime for their core infrastructure. Real-world reliability depends heavily on your broker's connection to the feed provider, not just the provider itself. A broker with a poorly maintained CQG gateway can still have outages even though CQG's core servers are up.

4. Is dxFeed reliable enough for futures automation?

For strategies with hold times over a few minutes, dxFeed is sufficient. Its 8-15ms typical latency won't meaningfully affect fill quality on 5-minute or longer timeframe strategies. For sub-minute scalping on liquid contracts, the latency difference versus Rithmic is worth considering.

5. How do I test data feed quality before committing?

Open a demo account with a broker that supports the feed you want to test. Run your strategy in simulation during both normal hours and at least one high-volume event like NFP or FOMC. Compare the demo fills against what you'd expect from your backtest to gauge data consistency.

6. Do prop firms let you choose your data feed?

Most prop firms assign a specific data feed, typically Rithmic. Topstep, Apex Trader Funding, and several other major firms use Rithmic infrastructure. You usually cannot switch to CQG or dxFeed on a prop firm account. This is one reason to build and test your strategy on Rithmic data if you plan to trade prop firm evaluations.

Conclusion

Choosing between CQG, Rithmic, and dxFeed for your futures broker data feed comparison comes down to broker compatibility, latency needs, and cost. CQG offers the broadest broker support, Rithmic wins on raw speed, and dxFeed saves money for traders who don't need sub-10ms data delivery. Match your data feed to your strategy's actual requirements rather than chasing the lowest latency number.

Before going live, test your specific broker-feed combination during a high-volatility event and confirm that your automation platform works with that feed. For more on connecting your broker to an automation setup, see the complete algorithmic trading guide which covers trading infrastructure setup from broker selection through live deployment.

Ready to automate your futures trading? Explore ClearEdge Trading and see how no-code automation works with your TradingView strategies across 20+ supported brokers.

References

Disclaimer: This article is for educational purposes only. It is not trading advice. ClearEdge Trading executes trades based on your rules; it does not provide signals or recommendations.

Risk Warning: Futures trading involves substantial risk. You could lose more than your initial investment. Past performance does not guarantee future results. Only trade with capital you can afford to lose.

CFTC RULE 4.41: Hypothetical results have limitations and do not represent actual trading.

By: ClearEdge Trading Team | 29+ Years CME Floor Trading Experience | About

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5

Heading 6

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.