CQG: trading platforms, exchange connectivity, APIs and software pricing

CQG supplies trading interfaces, analytics, data and exchange-routing technology. The institutional buyer can be a futures commission merchant (FCM), broker or trading firm; a trader may access the software through an FCM relationship. CQG’s operating network and the customer’s brokerage account are different parts of that service. The provider’s company description identifies Colorado as its headquarters and describes its international market-data and hosted-gateway business.[1]

A broker comparing these products should first define whether it is buying a trader workstation, a connection for its own front end, or a broader institutional implementation. A familiar screen is not evidence that all downstream accounts have the same exchange access, order limits, data entitlements or commercial terms. Those distinctions also determine who can resolve a failed order: the application vendor can investigate a technical fault, while the executing firm controls account permissions and the trade record.

The published API family separates data and analytics delivery, order routing through hosted gateways, and publication of custom studies or indicators into CQG interfaces. This is not a single unrestricted feed-and-trade licence. A broker needs to identify the particular API, authentication arrangement, permitted data use and enabled destinations.[8]

An API deployment needs reconciliation between the submitted order, acknowledged order and final fill. The same logic applies when a front end disconnects: a lost display connection is not proof that an order has been cancelled. Before production, the broker should document the server-held orders, kill or cancellation procedures and authoritative position source.

For One or QTrader, 100, 4,000 and 5,000 filled contracts give software charges of $125, $1,100 and $1,130 respectively for one monthly per-FCM calculation. The method is $100 plus $0.25 for each of the first 4,000 contracts and $0.03 thereafter. These examples exclude exchange fees, brokerage and other options; count filled contracts, rather than order tickets.[13][6][7]

For procurement, count separately the licensed workstations, environments, order-routing charges, APIs and exchange permissions. An advertised base price does not establish a negotiated enterprise tariff or the broker’s final resale price.

Integrated Client offers a two-week trial. Its development tools support historical analysis and testing; automated execution is described through AutoTrader. A trial demonstrates access to a software environment, not that a trading strategy is profitable or that the customer’s live exchange permissions have been approved.[2]

For a broker rollout, acceptance testing should use the exact production account groups and risk limits in a controlled environment. Reconcile symbols, contract expiries, tick values, time zones and session calendars. Test partial fills, rejected amendments and reconnection while orders remain working. The resulting evidence is more useful than a claim that every application with the CQG name has identical behaviour.

The One comparison marks some functions as forthcoming. A roadmap entry should not become a promised deliverable in an implementation schedule without written confirmation. Existing server-side or browser capabilities should likewise be tested in the purchased product rather than transferred from another CQG application.[7]

CQG publishes technical assistance through chat in supported applications, remote-assistance arrangements and specialist product help. Its normal support window is Sunday 14:30 through Friday 17:00 US Central time. This is a stated staffed window, not a contractual guarantee of resolution time.[9]

During an incident, retain the application version, account reference, order identifiers, instrument and timestamps. Do not send credentials through an informal channel. A broker should agree its own emergency dealing process with the FCM; technical support availability alone does not establish an emergency execution mandate.

CQG’s QTrader material explicitly places the trading account with an FCM partner. The provider profile therefore describes technology and market access infrastructure, not a substitute deposit-taking or custody relationship. No customer-money protection, exchange membership or compensation entitlement is inferred from using CQG software.[4]

Market-data access and redistribution also need their own permissions. The correct comparison is between the licensed user, exchange entitlements and agreed application use—not merely between the number of markets mentioned in a marketing overview. A software integration does not confer a right to republish every received price.

Broadridge’s regulatory filing records completion of the CQG acquisition on 30 April 2026; its public announcement followed on 1 May. The completed transaction expands Broadridge’s trading and connectivity offering. Proposed technology integrations remain separate from the legal completion date.[14][11]

CQG’s client notice says customers can continue using their usual contacts and existing technology while integration proceeds. For an established broker, that is evidence of intended operational continuity, not a waiver of the need to check a new contract, invoice entity or product migration notice.[12]

Operator

CQG business within Broadridge Financial Solutions; confirm the contracting affiliate in the order form

Service scope

CQG combines trading workstations, data, analytics and routing infrastructure. The profile compares product scope, public software charges, FCM relationships, support and the completed Broadridge acquisition.

Customer types

FCMs and brokers; Institutional trading firms; Professional traders and hedgers

Delivery

Hosted; API; Hybrid

Pricing publication

Public and quoted pricing

Platforms

Integrated Client; CQG One; QTrader; CQG Desktop

Implementation

Product-specific workstation or API implementation; brokerage permissions and exchange entitlements remain separate.

Support

Published technical support window: Sunday 14:30 to Friday 17:00 US Central time.

Permissions and regulatory scope

Technology profile; the FCM relationship governs the trading account. No blanket custody or regulatory protection inferred.

Provider metadata checked 20 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 7Source 8Source 9Source 10Source 11Source 12

The product decision can be separated into three tests. First, does the interface support the operator’s actual order workflow? Second, can the broker reconcile its order and position state through a failure? Third, is the complete monthly cost understood at the relevant filled-contract volume and FCM count? Passing one of those tests does not settle the other two.

A migration plan should preserve exported layouts, custom studies and the entitlement inventory where the contract allows it. Historical data availability, saved workspace portability and live order continuity are separate requirements.