Published September 18, 2026 · Updated September 18, 2026

Rithmic vs CQG: Futures Data, Routing, and Platforms Compared

Rithmic vs CQG for futures: market depth and MBO, server-side orders, platform compatibility, and published costs, from vendor pages checked September 2026.

Rithmic and CQG both provide market-data and order-routing infrastructure for futures, and both also ship their own trading front ends: Rithmic’s R | Trader Pro (Windows desktop, web, and mobile) and CQG’s Integrated Client, QTrader, One, Desktop, and Mobile.12 Neither is only backend plumbing, and neither holds your account. Rithmic says it is not a broker, and CQG’s One, Desktop, and QTrader require a trading account through an FCM.32 Five layers are easy to blur together:

  • Data provider: receives exchange data and delivers quotes, depth, and history.
  • Order-routing gateway: validates orders and routes them to the exchange.
  • Broker or FCM: holds the account, clears the trades, and decides which gateways, data entitlements, and logins you get.
  • Exchange: matches orders and sets market-data entitlements and fees.
  • Trading front end: the software you click in, whether vendor-built or third-party.

Rithmic and CQG each cover the first two layers and sell a front end for the fifth. Your FCM controls what reaches you, and your front end limits how much of the data and gateway you can use, so broker, platform, and gateway selection depend on one another. This comparison treats them that way: what each vendor documents, what depends on your configuration, and what to confirm before you pay.

It uses vendor-published pages read in September 2026 and third-party platform documentation where noted. It is not hands-on testing, and it does not measure fills, latency, or reliability. Vendor statements are reported as vendor statements. Fees change and are often set by the broker, so confirm current terms before you commit.

Quick answer: Rithmic or CQG?

  • Rithmic first if your required front end explicitly supports its MBO integration, your broker provides the needed entitlement, or another documented Rithmic-specific requirement rules it in.1456
  • CQG first if the available CQG configuration supports a required contract that the alternative does not, you require a CQG-specific front end, or you need CQG’s documented spread-management capability.728
  • Neither by default. Confirm the actual broker, gateway, platform, order behavior, data entitlement, and total fees before choosing.

Commission tiers and platform costs across futures brokers and platforms are covered in Best Futures Broker in 2026 and Best Futures Trading Platform. This article stays on the data-and-gateway layer.

What do Rithmic and CQG actually provide?

Rithmic describes direct market access trade execution software with separate systems for market data (its “Ticker Plant”), order routing (the “Order Plant”), and historical data (the “History Plant”), running since 2006, plus a server-side risk management system for account rules.93 It connects to CME Group, SMFE, Nasdaq (top-of-book only), and EUREX for customers of select FCMs.13 Traders reach it through a broker, funding evaluator, or FCM, which supplies the credentials.1 Its own front end is R | Trader Pro.

CQG describes connections to more than 85 market data sources, 45 tradable exchanges, and more than 100 broker environments, and it is now part of Broadridge Financial Solutions.710 It sells its front ends at their own monthly prices, with trade routing an add-on on Integrated Client.211

The practical consequence is that “Rithmic vs CQG” is usually decided one layer up. If your broker or evaluator offers only one, the choice is already made. If it offers both, the decision turns on your front end and what your tools need from the data. Who holds your funds and clears your trades is a separate question, covered in the broker comparison.

Rithmic vs CQG at a glance

Labels: Documented means the vendor’s own pages state it (nothing here was tested hands-on). Depends means it varies by front end, exchange, entitlement, or FCM. Not offered means the vendor states it is unavailable. Not verified means it could not be established from the sources checked, which is not the same as unavailable.

RithmicCQG
What it providesDocumented: market data, order routing, history, and server-side risk management, plus its own front end, R | Trader Pro931Documented: consolidated data from 85+ sources, routing to 45 tradable exchanges, and its own front ends; part of Broadridge1072
How you get accessDocumented: through a broker, funding evaluator, or FCM that supplies credentials1Documented: One, Desktop, and QTrader need a trading account through an FCM; Integrated Client is subscribed through CQG2
Own front endsDocumented: R | Trader Pro on Windows, plus a web app and iOS/Android apps. Not offered: a macOS desktop app15Documented: Integrated Client and QTrader (Windows), One and Desktop (browser), Mobile (iOS/Android)12131415
Order-level depth (MBO)Documented; depends on account entitlement and platform. Coverage is not itemized by exchange, and Nasdaq is top-of-book only136Documented: order-level features in CQG front ends and order-level structures in its Web API. Not verified: retail access, exchange coverage, or delivery to third-party platforms13161718
Feed handlingDocumented: un-throttled, un-aggregated feed, per the vendor3Not verified: the pages checked make no comparable statement7
Server-side ordersDocumented: trailing stops, brackets, and OCOs on Rithmic’s servers. Depends on the front end4519Documented: brackets on CQG’s servers (Integrated Client, Desktop, Mobile) and server-side smart orders (One). Depends on order type, exchange, and front end820151321
Exchanges namedCME Group (CME, CBOT, NYMEX, COMEX), SMFE, Nasdaq (top-of-book), EUREX at select FCMs1345 tradable exchanges; the pages name CME Group, ICE Futures U.S., and LME among them7
Latency figuresVendor figures at different boundaries: sub-microsecond order routing, about 1 ms for API+ order handling, under 250 µs tick-to-trade for Diamond922Spreader-specific: under 1 ms for order modifications and second legs; no general figure. Not comparable7
Historical dataTick data back to December 2011, 40 GB weekly limit per user3Archives with decades of daily and years of intraday data; limits inside a front end vary232
APIsR | API+, R | Protocol API, R | Diamond API; conformance testing required for production4Client APIs (an Integrated Client add-on); Enterprise APIs limited to enterprise systems2411
Published costNot published: pricing comes from Rithmic sales, your broker, or your evaluator325Documented: list prices per front end; the final price is set per FCM211
Third-party platformsDirectory of more than 30 platforms, with connection guides for several25Documented by platform vendors (ATAS, MotiveWave, MultiCharts, and others), often needing broker enablement262728

How do their market data feeds differ?

Depth data comes in different forms, and the one your tools need should drive the choice:

  • Market by price (MBP): total size at each price level. CQG’s API documentation describes an aggregate book of this kind, offered as multiple-depth or top-of-book.29
  • Market by order (MBO): individual anonymous resting orders, their sizes, and priority or queue information where the exchange disseminates it. Exchange MBO does not reveal customer identities; the gateway, entitlement, and front end determine what a trader actually receives.30
  • DOM display: a price ladder in a front end. A ladder can be drawn from either kind of data, so a DOM by itself does not show whether order-level data sits underneath.
  • Order-level data inside an API or algorithm: CQG’s Web API documents DetailedDOM messages for separate orders at price levels, with order IDs, order indices, volumes, and updates. CQG supports only a limited number of prices for DetailedDOM and warns that market-data updates may be lost, so consumers must handle updates robustly. This documents an API structure; it does not establish normal retail access, full-depth MBO, or pass-through to every platform.1718
  • Pass-through: a third-party platform receives only what your gateway login and exchange entitlements supply. Bookmap, for example, tells Rithmic users who see a “permission denied” message to ask their broker to enable Level 2 market-depth data on the account.6

Rithmic. Its pages describe market depth with MBO “down to the individual order level” in R | Trader Pro, on an un-throttled feed, and Bookmap’s documentation says Rithmic provides MBO for CME futures.1226 Quantower documents a Market by Order setting on its Rithmic connection that shows MBO data in its DOM panel.31 Rithmic does not itemize MBO by exchange and lists Nasdaq as top-of-book only, so do not assume the same functionality across every exchange, account entitlement, and platform.

CQG. CQG’s product pages document order-level features in its own front ends. The CQG One page lists “Detailed DOM/Market-by-Order,” and Integrated Client’s Detailed DOM tool shows the working-order queues at the best bid and ask and the number of orders ahead of yours, estimated where the exchange does not supply actual queue position.1316 CQG also documents order-level market-data structures through its Web API: DetailedDOM describes separate orders at price levels, while DetailedDOMOrder includes an order ID, index, volume, and updates. CQG limits the supported prices and warns that market-data updates may be lost.1718 This is distinct from the Integrated Client’s COM-based Client API, and neither document establishes that a normal retail Client API subscription includes Web API DetailedDOM access. Bookmap documents CQG Continuum full-depth data for CL crude oil, but does not establish MBO availability through that connection and does not support other CQG products such as CQG IC.6 Retail MBO through CQG’s data connections to third-party tools is therefore configuration-dependent or unverified. That is not a statement that CQG lacks MBO. If your software depends on order-level depth, get the answer in writing from CQG or your FCM for your exchange and platform.

Exchanges and aggregation. Rithmic’s pages list CME Group, SMFE, Nasdaq (top-of-book), and EUREX at select FCMs.13 CQG describes 45 tradable exchanges and server-side aggregation for trading similar instruments on more than one exchange.7 If you trade only CME Group products, the extra reach may not matter. Check that your exact contracts are covered.

History. Rithmic states tick-level history back to December 2011, with a 40 GB weekly limit per user. Its pages do not break coverage down by contract, exchange, or subscription.93 CQG separates provider-level archives from what a front end includes. Its historical-data page describes decades of daily data and many years of intraday data, including tick and best bid/ask, available for download through separate products (Data Factory and Portara), and its data page cites nearly 50 years for many agricultural products.237 Inside a front end the limits are narrower. On the comparison page, CQG Desktop’s daily charting is limited to three years, and extended intraday history is a paid add-on on some front ends.2 Neither history is a substitute for testing a strategy against live conditions; see backtest vs. forward test.

How do order routing and server-side orders differ?

A protective order raises five separate questions: where the instruction is stored, where its trigger is monitored, which system routes the resulting order, whether the exchange accepts it, and whether and at what price it fills. Holding a stop on a vendor’s server can change the first three answers. It does not settle the last two. A triggered stop becomes a market or limit order that the exchange can reject, that can fill well past the stop price in a fast or thin market, or, for a stop-limit, may not fill at all. A server-held order is not guaranteed protection against a disconnect, an exchange outage, a rejected order, a liquidity gap, or a failure inside the gateway or your FCM’s systems.

Rithmic. Its API pages say trailing stops, brackets, and OCOs “execute on Rithmic’s servers” and continue to fire if the client connection drops, and its web and mobile app lists server-side brackets with trailing bracket stops.45 Its risk management system, which enforces account-level rules such as loss limits and auto-liquidation, is described as running in the order path independent of the client, and auto-liquidation attempts to flatten positions.3 Rithmic markets that system to funding evaluators, FCMs, and brokers, so whether rules are configured on your account is that firm’s decision.32 The pages checked do not say whether plain stop and stop-limit orders are held at Rithmic or sent to the exchange as native orders.

CQG. Integrated Client’s help says brackets have resided on CQG’s co-located servers since version 19.6 and are not cancelled if your screen crashes or loses connection to the server. Using them requires enablement from CQG and from you in Smart Order Preferences.8 CQG describes server-side smart orders in CQG One, server-side bracket orders in CQG Desktop and CQG Mobile, and server-side spreading and aggregation.1320157 A 2018 release note describes orders continuing to work after you exit CQG Desktop 3.2; it dates the behavior and does not confirm today’s release.33 Separately, CQG’s synthetic order manager holds order types an exchange does not support natively, including CQG’s own DOM-triggered stops, “on the CQG side” until their conditions are met, then sends an order the exchange supports. The trigger uses bid, ask, and trade data from CQG’s feed. CQG warns that if an exchange publishes prices while matching is inactive, a triggered order can fill later at a price far from the trigger.21 Which order types are native and which are synthetic varies by exchange, so how a given stop, stop-limit, trailing, or OCO order persists by product, front end, and FCM is not established by the pages checked.

The front end matters. Sierra Chart’s documentation lists server-managed OCO as supported for both gateways and server-managed brackets as unsupported for both. Its Rithmic page was last modified in December 2025 and its CQG page in August 2025, so the same gateway can behave differently in different platforms.1934

How to verify before relying on it.

  1. Get the order-hosting behavior in writing for your exact order type, exchange, front end, and FCM: exchange-native, held on the gateway’s server, or held by your client.
  2. Place a protective order and confirm its status from an independent connection where one is supported, such as the vendor’s web or mobile app or your FCM’s own platform. Some setups allow one login per platform at a time, as ATAS notes for CQG, so ask your FCM for a second login if you need one.26
  3. Read your FCM’s emergency order-management process: how to reach the trade desk to cancel or flatten, and during what hours. Optimus, for example, lists an Emergency Trade Desk.35
  4. Treat simulation as limited. It can show whether an order type is accepted and reported as hosted, but it cannot prove how a live exchange, your FCM’s risk system, or a fast market will handle every failure.

Latency figures. Rithmic’s pages give several figures with different boundaries: a homepage “sub-microsecond” order-routing figure, about 1 millisecond for R | API+ order handling, under 1 millisecond for Protocol API order routing, and under 250 microseconds tick-to-trade for the Linux-only, co-located Diamond API.9422 These are vendor figures, the pages do not define the measurement points, and the API page rates jitter as variable for the first two. CQG publishes a different kind of figure: under one millisecond for order modifications and second-leg execution in its server-side spreader, attributed to the Spreader Core’s proximity to the exchange.713 These are product-internal numbers, they are not comparable, and neither is end-to-end. Your fill time also includes network latency, front-end processing, order routing, exchange acknowledgment, and the fill itself, and slippage depends on the market. Unthrottled data is not proof of faster fills. To compare gateways on outcomes, measure your own fills, which How to Evaluate Broker Execution Quality walks through.

Which platforms and front ends work with each?

Separate documented integration (a vendor publishes a connection guide) from availability on your account, which can require your FCM to enable the platform on your login.

PlatformRithmicCQG
ATASConnection guide in Rithmic’s directory25ATAS documents a CQG connection; your broker must add ATAS to your CQG login26
QuantowerConnection guide in Rithmic’s directory; Quantower documents an MBO mode2531Quantower’s CQG documentation is written for AMP Futures accounts36
BookmapMBO and full depth for CME futures, subject to the connection and permissions6CQG Continuum full-depth data is documented for CL crude oil; MBO is not established through that connection, and other CQG products such as CQG IC are not supported6
MultiChartsGuide in Rithmic’s directory25Listed among MultiCharts’ providers28
MotiveWaveGuide in Rithmic’s directory25Listed among MotiveWave’s gateways27
Sierra ChartRithmic lists Service Package 10 or higher as required25Same package requirement37

Sierra Chart’s base packages cannot connect to external services such as CQG or Rithmic, so the Integrated packages (10, 11, or 12) are required. Package 12 adds Sierra Chart’s own MBO functionality, which does not establish that either gateway supplies MBO to it.37 Sierra Chart also sells a separate real-time feed, Denali. Its Rithmic page says it provides no technical support for Rithmic market data or trading and recommends Denali, and its CQG page says CME Group and EUREX data are supported only through Denali.1934 For Sierra Chart users on Denali, the gateway is then mainly the order route, so gateway data claims apply less.

Rithmic offers a free 14-day paper-trading trial with live market data, one per user, and its web and mobile apps are not available in the trial.3

APIs. These matter only if you build your own tools. Rithmic offers R | API+ (C++ on Windows, macOS, and Linux; .NET on Windows), R | Protocol API (WebSockets and Protocol Buffers, any language), and R | Diamond API (Linux, co-located server, and FCM support required). All need a dev kit request and passing conformance testing before production access, then live credentials through your FCM, which may charge fees.43 CQG’s COM-based Client APIs run on the same machine as Integrated Client and are available to individual users; CQG says they require an Integrated Client subscription plus applicable API services, exchange approvals, and possible licensing.3811 Separately, CQG’s Web API documentation defines DetailedDOM messages, but it does not establish that Web API MBO access is included with a normal retail Client API subscription. CQG’s other Enterprise APIs (Web API, FIX Connect, Quotes Direct, CMS API, Custom Algo SDK) are limited to enterprise systems.173924 Neither vendor’s API access should be assumed to be included with an ordinary retail gateway subscription.

What does each one cost?

The two vendors present cost differently. Rithmic does not publish a price list on the pages checked. Its FAQ says fees are paid in advance and that software and market-data pricing comes from Rithmic sales, and its directory tells new users to talk to their broker or funding evaluator or contact Rithmic.325 CQG publishes monthly list prices:112

CQG front endMonthly baseTradingPublished transaction charge
Integrated Client$595+$250 for CQG Trading, or $1,400 for CQG Spreader, which includes tradingNone listed
QTrader$100Live trading login required$0.25 per filled contract up to $1,000, then $0.03 per filled contract
One$100Live trading login required$0.25 per filled contract up to $1,000, then $0.03 per filled contract
Desktop$25Live trading login required$0.25 per filled contract, capped at $695

The same price sheet lists CQG Mobile at $25 per month when subscribed to separately. Its bundle notes say Integrated Client, QTrader, and One include Desktop and Mobile, while Desktop includes Mobile. Do not add those bundled products to the base prices above.11

The caps apply to transaction fees, not the monthly base price. Exchange fees are not included. These are list prices, and CQG’s comparison page notes pricing is per FCM: Optimus, for one, lists CQG Desktop as free to its customers cleared through AMP Clearing (regular $25 per month).240 Units matter. A side is one buy or one sell, and a round trip is an entry and an exit, so two sides. An order can fill in several fills, and one fill can cover several contracts. CQG’s comparison page says “per fill” while its price sheet says “per filled contract.” Because those billing terms are not interchangeable for multi-contract orders, ask your FCM which unit applies to your account.

Broker-specific charges. Optimus’s published schedule lists Rithmic and CQG routing at $0.10 per side each, and monthly connection fees of $25 for Rithmic and $10 for CQG.35 Its support page says routing is billed per side by the data feed you select, for Optimus Flow.41 These are one broker’s figures, not provider rates, and the schedule does not say which accounts pay the connection fee. Optimus’s pricing FAQ also says active accounts have no additional monthly data fees, so whether the connection fee is charged to a given account is unconfirmed.42

What to request in an itemized quote:

  • Exchange market-data entitlements, with Level 1 and depth priced separately. Optimus lists the non-professional CME Group bundle at $9 for Level 1 and $41 for Level 2 depth, and lists only those two tiers. Ask whether MBO needs its own entitlement and whether professional status changes the price.35
  • Platform subscription: a CQG front-end fee, or your third-party platform’s own fee.
  • Gateway connection fee (monthly) and routing fee (per side, contract, or order).
  • Brokerage commission per side.
  • Exchange, clearing, and regulatory fees per side. Optimus lists the NFA fee at $0.02 per side, with clearing fees that depend on the FCM.35

For each item, ask whether it is charged per month, side, contract, or order, and whether it is waived at any volume.

One CQG list-price illustration is safe only under an explicit assumption: 20 one-contract round trips per month, with one filled contract on each side, means 40 filled contracts. Using the price sheet’s per-filled-contract wording, CQG One or QTrader would be $100 + (40 × $0.25) = $110 before exchange fees and other charges.11 This is not an all-in quote, and it must not be combined automatically with Optimus’s separate routing or connection figures. Optimus publishes Rithmic and CQG routing at $0.10 per side and monthly connection figures of $25 and $10, but the schedule does not establish the relevant account scope or whether its routing unit matches the CQG subscription unit.35

Other possible costs include exchange data entitlements (Level 1 versus depth), platform subscriptions, gateway connection fees, routing fees, brokerage commissions, and exchange, clearing, and regulatory fees. Ask whether each item is charged per month, side, contract, fill, execution, or order, and whether a volume waiver or bundle already includes it.

Which one fits which need?

If your requirement is…What the documents supportVerify before choosing
Order-level depth in a heatmap or order-flow toolRithmic MBO is documented, including in Bookmap and Quantower docs. CQG documents front-end and Web API order-level structures, but delivery to a particular third-party tool is unverified16311718That your account has the MBO entitlement and your platform’s guide lists the gateway; get CQG’s answer in writing
A browser-based vendor front endBoth: R | Trader Pro’s web app and CQG One or Desktop51314That your FCM enables it, and how CQG’s per-contract fees behave at your volume
Protective orders that persist without your clientBoth document server-side brackets in some products48Order type, exchange, front end, and FCM, using the steps above
Markets beyond CME GroupCQG names ICE Futures U.S. and LME; Rithmic lists CME Group, SMFE, Nasdaq (top-of-book), and EUREX at select FCMs73Your exact contracts, and the data entitlement for each
Spreads with server-side legs or cross-exchange aggregationCQG documents Spreader and aggregation. For Rithmic, not verified: the pages checked describe no comparable spread product713The Spreader price ($1,400 on Integrated Client) and exchange support
Your own applicationRithmic’s three APIs; CQG Client APIs with Integrated Client424Conformance testing or enterprise access, questionnaires, and who supplies live credentials
A MacR | Trader Pro’s desktop app is not supported on macOS. Its web and mobile apps work, and Rithmic marks Bookmap and MotiveWave Mac compatible. CQG’s Integrated Client and QTrader list Windows12512Your platform’s macOS support for your gateway
A funding evaluatorWhichever gateway the evaluator supportsThat choice is usually the evaluator’s, not yours

These are starting points, not a ranking.

Choose the gateway last

A workable order is: pick the broker or FCM you trust, pick the front end you can operate under pressure, then check which gateway that combination uses and whether it meets a requirement in the table above. Record the reason and a condition for revisiting it, such as a change in the data your tools need, a fee change, or a move to a new front end. The trading decision-making framework is a way to do that. It keeps an infrastructure choice inspectable instead of an assumption you stop questioning after the first week. Run the order verification steps above before you rely on any protective order.

Where Costante fits, and where it does not

Costante is not a data feed, gateway, broker, exchange, or trading platform, and it is not a candidate in this comparison. It does not connect to brokers or exchanges, execute or route orders, block trades, or backtest strategies.

Costante is relevant after these choices are made. It supports the behavioral-performance layer around whatever data and execution stack you use: session planning, self-defined guardrails, in-session checks, low-friction logging, and structured review of execution drift. Because it does not connect to your broker or platform, it is not tied to a gateway choice. The trader remains responsible for acting on the plan.

Frequently asked questions

Are Rithmic and CQG brokers?

Not according to their own pages. Rithmic states it is not a broker and that live trading needs an account with an FCM that supports it.3 CQG’s One, Desktop, and QTrader require a trading account through an FCM, and its pages describe connections to more than 100 broker environments.27 Both also offer their own front ends, so neither is only backend infrastructure.

Which offers market-by-order data, Rithmic or CQG?

Rithmic documents MBO in its market depth feed and R | Trader Pro, and Bookmap and Quantower document using it, subject to account entitlement and platform.1631 CQG documents order-level detail in its own front ends, such as the “Detailed DOM/Market-by-Order” listed for CQG One, and order-level structures through its Web API.131718 Whether a particular retail account, exchange, entitlement, or third-party platform receives that data remains configuration-dependent or unverified.

Do my orders stay working if my connection drops?

It depends on the order type, exchange, front end, and FCM. Rithmic documents server-side trailing stops, brackets, and OCOs, and CQG documents server-side brackets in Integrated Client and other front ends.4813 Neither vendor’s pages promise an exit price or a fill, and a triggered stop can still be rejected or fill far from its trigger. Confirm the hosting behavior for your exact setup, as described above.

Which has lower latency, Rithmic or CQG?

The pages checked do not answer that fairly. Rithmic publishes vendor figures with different measurement boundaries, and CQG publishes a spreader-specific figure.227 What you experience depends on your connection, front end, order type, and broker. Measure your own fills instead of relying on a vendor figure.

Can I use Rithmic with any trading platform?

No, but with many. Rithmic’s directory lists more than 30 platforms and publishes connection guides for several, including ATAS, Quantower, Bookmap, MultiCharts, and MotiveWave.25 Confirm your platform, gateway, and broker combination before you fund an account.

Do I need Rithmic or CQG to trade futures?

No. They are two of several data and routing options; the broker page cited below also lists other feeds, including Trading Technologies, CTS, and Firetip.43 The choice usually follows your broker and front end rather than driving it.

Sources

Vendor pages were read in September 2026 unless a date is given. Nothing here was independently tested.

Costante provides educational workflow tools, not financial advice. Trading involves risk.

Footnotes

  1. Rithmic. R | Trader Pro. Accessed September 2026. ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11 ↩12 ↩13 ↩14

  2. CQG. Product Comparison. Accessed September 2026. ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11 ↩12

  3. Rithmic. Frequently Asked Questions. Accessed September 2026. ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11 ↩12 ↩13 ↩14 ↩15 ↩16 ↩17

  4. Rithmic. R | API+ and trading APIs. Accessed September 2026. ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9

  5. Rithmic. R | Trader Pro Web & Mobile. Accessed September 2026. ↩ ↩2 ↩3 ↩4 ↩5

  6. Bookmap. Connectivity. Third-party platform documentation; accessed September 2026. ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9

  7. CQG. Market Data. Accessed September 2026. ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11 ↩12 ↩13 ↩14

  8. CQG. Entering Bracket Orders (Integrated Client help, version 25 documentation). Accessed September 2026. ↩ ↩2 ↩3 ↩4 ↩5

  9. Rithmic. Trading Infrastructure for Futures. Accessed September 2026. ↩ ↩2 ↩3 ↩4 ↩5

  10. CQG. Homepage. Accessed September 2026. ↩ ↩2

  11. CQG. Monthly Price Sheet (partner site). Accessed September 2026. ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7

  12. CQG. System Specifications. Accessed September 2026. ↩ ↩2

  13. CQG. CQG One. Accessed September 2026. ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10

  14. CQG. CQG Desktop. Accessed September 2026. ↩ ↩2

  15. CQG. CQG Mobile. Accessed September 2026. ↩ ↩2 ↩3

  16. CQG. Detailed DOM Tool Including Show Place in Queue (Integrated Client help, version 25 documentation). Accessed September 2026. ↩ ↩2

  17. CQG. DetailedDOM (Web API help). Accessed September 2026. ↩ ↩2 ↩3 ↩4 ↩5 ↩6

  18. CQG. DetailedDOMOrder (Web API help). Accessed September 2026. ↩ ↩2 ↩3 ↩4 ↩5

  19. Sierra Chart. Rithmic Trading Service. Page states last modified December 19, 2025; accessed September 2026. ↩ ↩2 ↩3

  20. CQG. CQG Desktop trading help: Bracket Orders & OCOs. Accessed September 2026. ↩ ↩2

  21. CQG. Synthetic Order Manager (SOM) (FCM help). Accessed September 2026. ↩ ↩2

  22. Rithmic. Technology. Accessed September 2026. ↩ ↩2 ↩3 ↩4

  23. CQG. Historical Data. Accessed September 2026. ↩ ↩2

  24. CQG. CQG APIs. Accessed September 2026. ↩ ↩2 ↩3

  25. Rithmic. Compatible Trading Platforms. Accessed September 2026. ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10

  26. ATAS. Connecting to CQG/Continuum. Third-party platform documentation; page states modified June 2, 2025; accessed September 2026. ↩ ↩2 ↩3

  27. MotiveWave. Data and broker connections. Third-party platform documentation; accessed September 2026. ↩ ↩2

  28. MultiCharts. List of supported providers. Third-party platform documentation; accessed September 2026. ↩ ↩2

  29. CQG. Incremental Book Management (API help). Accessed September 2026. ↩

  30. CME Group. Market by Order (MBO). Accessed September 2026. ↩

  31. Quantower. Connection to Rithmic. Third-party platform documentation; accessed September 2026. ↩ ↩2 ↩3 ↩4

  32. Rithmic. Risk Management. Accessed September 2026. ↩

  33. CQG. What’s New in CQG Desktop Version 3.2. Published May 15, 2018; historical release note, not current documentation. ↩

  34. Sierra Chart. CQG Trading Service. Page states last modified August 7, 2025; accessed September 2026. ↩ ↩2

  35. Optimus Futures. Common Futures Trading Costs. Broker-published fee schedule; accessed September 2026. ↩ ↩2 ↩3 ↩4 ↩5

  36. Quantower. Connection to CQG (AMP Futures). Third-party platform documentation; accessed September 2026. ↩

  37. Sierra Chart. Description of Service Packages and Pricing. Page states last modified September 8, 2026; accessed September 2026. ↩ ↩2

  38. CQG. Client APIs. Accessed September 2026. ↩

  39. CQG. Enterprise API Questionnaire. Accessed September 2026. ↩

  40. Optimus Futures. What is the pricing for CQG Desktop? Broker support page; accessed September 2026. ↩

  41. Optimus Futures. Are there any routing fees associated with trading on your platform? Broker support page; accessed September 2026. ↩

  42. Optimus Futures. Futures Trading Commissions and pricing FAQ. Broker page; accessed September 2026. ↩

  43. Optimus Futures. Futures Market Data Feeds. Broker page; accessed September 2026. ↩