Rithmic vs Tradovate vs CQG: Fees & Latency Measured (2026)

Ping Tradovate’s API from a Chicago VPS and you’ll typically get a reply in 0 to 1 millisecond. Ping Rithmic from the same machine and the number barely moves. So is the Rithmic vs Tradovate speed question a tie?

Not quite. When we tested where each hostname resolves, only one of those replies came from the vendor’s own Chicago servers. The other came from Google’s network edge, a different measurement wearing the same number.

Most figures in this debate work the same way: real, but not measuring the same thing. So on September 11, 2026, we pulled fees from live rate cards, ran our own DNS lookups and took latency figures from vendor specs, public ping data or our own math. We placed no live orders.

Key Takeaways

• At Apex, an ES round turn costs $3.98 on Rithmic and $3.10 on Tradovate, yet micro index contracts cost 2 cents less on Rithmic.
• NinjaTrader charges $0.25 more per contract to route through Rithmic or CQG Desktop.
• A 0-1 ms ping to Tradovate’s API measures Google’s edge, not Tradovate’s servers.
• Evaluation fills come from each vendor’s simulator, not the exchange.

Our earlier Rithmic vs CQG vs Sterling platform comparison covers the software on top of these connections. This piece stays underneath it, on cost, speed and fills.

Rithmic vs Tradovate vs CQG: What Are You Choosing Between?

You’re choosing a pipe. Only one of the three is also the broker, and Rithmic and CQG reach you through brokers that bill their technology at $0.10 to $0.25 per contract. Tradovate folds its technology into a plan commission of $0.09 to $0.39 per micro side.

Rithmic is order-routing and market-data technology sold through brokers and prop firms. That’s why a Rithmic fee can sit next to somebody else’s commission on your statement. CQG is built the same way.

Tradovate is the odd one out: a futures broker with its own cloud platform, and a trade name of NinjaTrader Clearing, LLC. That’s the same firm behind NinjaTrader’s brokerage.

Where does CQG fit in 2026?

Mostly on the broker side. CQG runs and maintains its own distributed network of exchange gateways, so brokers don’t install anything. Traders connect to whichever gateway sits closest to them.

Our DNS lookups fit: CQG’s demo API sits on CQG’s Chicago network, and its production name is a regional alias. Retail traders reach CQG through brokers, and AMP’s CQG credentials work on every TradingView plan.

Prop firms are messier. Take Profit Trader sells “CQG” accounts that log in with a Tradovate username and password. Elite Trader Funding calls its Tradovate logins “Tradovate (CQG)” credentials, so ask what your firm’s CQG option logs into.

Which Connection Costs Less Per Round Turn?

NinjaTrader’s own connection costs the least. It sells all three routes side by side, publishes the same plans as Tradovate, and adds $0.25 per contract whenever you route through Rithmic or CQG Desktop. That’s $0.50 on every round turn.

We read “per contract” as per fill, the way AMP spells out its Rithmic fee, so a round turn pays twice. Here’s what that does to one micro contract, bought and sold, on each plan:

Standard contracts follow the same pattern: $2.58 becomes $3.08 a round turn on Free, and $1.18 becomes $1.68 on Lifetime. These are commission plus routing only, since exchange, NFA and NinjaTrader’s $0.19 clearing fees land the same on every route.

Where does that hurt most? On the Lifetime plan, a trader who paid $1,499 to get micros down to $0.18 a round turn gives most of that saving back through Rithmic. At NinjaTrader, the $0.50 routing charge is nearly three times the commission it rides on.

What do AMP and EdgeClear charge instead?

Other brokers price the same technology differently. AMP charges $25 a month per Rithmic user ID plus $0.10 per contract filled. EdgeClear charges $20 a month plus $0.10 per contract, and that $20 includes API access and R|Trader Pro.

CQG pricing splits by front end. EdgeClear lists CQG Desktop at $25 a month plus $0.25 per contract, with that charge capped at $495. CQG through TradingView costs $10 a month plus $0.10 per contract.

Does a fee cap matter to you? Only if you trade a lot.

Below roughly 2,475 micro round turns a month, Rithmic through AMP is the smaller technology bill of these two. Past that point, EdgeClear’s CQG Desktop fee has stopped at $520 while the Rithmic line keeps climbing. That’s about 118 round turns a trading day, within reach for a strategy copied across several funded accounts.

Keep in mind this compares technology fees at two different brokers. It’s a volume check, not an all-in price, since each broker also charges its own commission.

What does API access add?

Writing your own code? AMP’s Rithmic API add-on costs $100 a month on top of the $25 user fee, while EdgeClear’s $20 a month already covers it. Tradovate charges $25 a month for API access and won’t issue a key until a live account holds $1,000.

CQG’s own price schedule, effective October 2026, lists API trading at $245 a month. That sits on top of a $250 trading package and a $595 base package, which makes it institutional pricing rather than a retail line item. A webhook bridge avoids most of this, as the automation section explains.

Rithmic vs Tradovate at Apex: Where the Commission Gap Flips

Apex’s two fee schedules diverge. An E-mini S&P 500 or Nasdaq-100 round turn costs $3.98 on Rithmic against $3.10 on Tradovate, which is 28% more. The Micro E-mini versions flip it, at $1.02 a round turn on Rithmic and $1.04 on Tradovate.

Micro crude flips harder still, at $1.02 on Rithmic against $1.34 on Tradovate.

Put a monthly number on it. Ten ES round turns a day for 20 trading days costs $796 on Rithmic and $620 on Tradovate, a $176 gap every month. Run the same count on MNQ and Rithmic comes out $4 cheaper.

Same firm, same account, and the “expensive” platform depends entirely on what you trade. Which contract makes up most of your volume? It matters during an evaluation too: Apex charges the same Rithmic schedule on evaluation and funded accounts, and commissions come out of the balance your drawdown tracks.

Choose carefully, because you can’t change your mind later. Apex won’t convert an account between Rithmic, Tradovate and WealthCharts, so a switch means a new plan with no refund for a wrong pick. Mac users face one more catch: Rithmic doesn’t run natively on a Mac and needs a Windows virtual machine.

Our Apex Rithmic setup guide covers that side of it.

How Much Latency Does Each Connection Add?

Very little, compared with almost everything else in your setup. From a Chicago VPS, pings to both Rithmic and Tradovate typically return in 0 to 1 millisecond. A TradingView webhook needs roughly 22 to 111 ms just to cross from Oregon, so the connection is rarely where your time goes.

Rithmic publishes its own specs, too: its R|Protocol API is rated at under 1 millisecond typical. R|Diamond API, which connects straight to Rithmic’s exchange-facing gateways, is marketed at under 250 microseconds from reading market data to releasing an order. Tradovate doesn’t publish an order-latency figure that we could find, and neither does CQG in a form comparable for retail traders.

Where does the rest of the time go? The chart below puts every figure, from Rithmic’s fastest API to TradingView’s 3-second timeout, on one log scale.

Shopping for that Chicago box? Our low-latency VPS rankings compare the options. Check your prop firm’s IP-address rule first, though, because some firms ban trading from a VPS outright.

Why doesn’t a 0 to 1 ms ping settle it?

Because the two pings stop in different places. Anycast is a routing method that announces one IP address from many locations at once. Whichever site is nearest answers each packet.

Tradovate’s live API hostname resolved to a single Google Cloud anycast address. We got that same address back whether we asked as a client in Chicago, New York, London or Mumbai. A ping to it stops at Google’s closest edge, so it can’t show how far your order travels inside Google’s network to reach Tradovate’s servers.

Rithmic’s R|Protocol hostname returned 20 Chicago addresses spread across Hurricane Electric, Cogent, GTT and Zayo. Ping those and you’re timing the full trip to Rithmic’s own servers in Chicago, not a stop along the way.

None of this makes Tradovate slow; Google’s backbone is fast. It does mean a ping-based Rithmic vs Tradovate speed test compares a finish line with a waypoint. Don’t pick a platform off that number.

What does a TradingView webhook add before any of this?

Tens of milliseconds, at minimum. TradingView sends webhooks from four published IP addresses, and when we looked them up, all four sat in Amazon’s US West region in Oregon. Public ping logs put the Seattle-to-Chicago round trip at 44.5 ms on September 11, 2026, the closest pair we found.

Now the handshake math. If TradingView opens a fresh HTTPS connection for each alert, TCP needs one round trip and a TLS 1.3 handshake needs another. The alert then lands about 2.5 round trips after TradingView starts, roughly 111 ms at a Chicago server.

On a warm, reused connection it’s closer to 22 ms. We don’t know which one TradingView does, so treat 22 to 111 ms as the range. Either end of it is 20 to 110 times the most the two connections differ in a Chicago ping test.

Want to cut latency on webhook automation? Start with where your alert and your bridge live, not with which connection carries the last mile.

Does the Connection Change Your Fills?

On a live account, less than people assume. The exchange’s matching engine fills live orders by price and arrival time, not by vendor. A connection shapes your fill through its speed, under 250 microseconds on Rithmic’s fastest API, and through where your exits wait.

Exits are where the connections look alike. Rithmic runs brackets, OCOs and trailing stops on its own servers, so they stay active if your connection drops. Tradovate holds brackets and trailing stops on its servers the same way.

How do evaluation simulators fill orders?

On an evaluation account, there’s no exchange in the loop, and your fills come from the vendor’s simulator. What exactly are you testing when you pass one?

• Rithmic estimates your queue position and fills a resting order once price trades through and the orders ahead clear.
• Rithmic’s simulated market orders fill against the size resting in the book, not the last trade. Its simulated accounts never affect one another.
• Tradovate approximates the exchange’s matching logic as closely as it can, though no simulator reproduces a live queue perfectly.

Most comparisons skip this: on an evaluation, fill quality is a policy the simulator vendor chose, not a network trait. Test it before you commit by resting a limit order at the bid on each platform and counting how often a touch turns into a fill. For the longer version, we broke down why Rithmic sim and live fills differ.

Which feed shows more of the order book?

Rithmic, if depth is what you trade off. It delivers unfiltered, full-depth Level 2 data, and CQG offers the full book too. Tradovate’s feed reaches Bookmap as partial depth.

CQG also screens its real-time feed for bad ticks and corrects them as soon as it finds them. Do you trade off the DOM? Then the depth gap is real, but for a TradingView strategy firing on bar closes it mostly isn’t.

Which Prop Firms Run on Rithmic, Tradovate or CQG?

Of the 5 futures firms we checked, 4 (80%) sell Tradovate-based accounts next to Rithmic. Apex and Tradeify both lock your choice in at checkout. Bulenox is the exception: it has run on Rithmic only since it stopped opening new ProjectX accounts in January 2026.

Platform is only half of it. Does your firm allow automation at the stage you’re trading? Check that before any of the fee math above, and if you’re on Tradeify, our Tradeify webhook automation guide walks through its rules.

How Do You Automate Each One From TradingView?

With a webhook bridge, whichever connection you’re on, because TradingView’s native links are built for clicking, not for running strategies. A bridge has to answer inside TradingView’s 3-second webhook window. PickMyTrade routes each alert to Rithmic or Tradovate in under 200 ms on typical setups.

Tradovate has an official TradingView integration, and CQG brokers such as AMP connect to TradingView too. Rithmic has none. At Tradeify, for example, TradingView connects through Tradovate accounts alone.

None of those native links turns a Pine Script strategy alert into an order. A webhook bridge is a cloud service that receives TradingView’s alert and places the order on your broker or prop firm account. That makes it the practical way to automate a Rithmic account from TradingView.

We don’t connect through CQG, so a CQG-only brokerage account isn’t one we can automate. Rithmic and Tradovate accounts are covered at prop firms and brokers alike, and the supported prop firms list has the current names.

In our experience, Rithmic questions mostly come from traders whose firm gave them no alternative, such as Bulenox. TradingView simply can’t see those accounts. Connecting TradingView to Rithmic takes one JSON alert and no R|API code.

One practical note before you wire anything up: TradingView posts webhooks to ports 80 and 443 and nothing else. If a firewall filters your traffic, allowlist TradingView’s four webhook IPs first.

Which One Should You Pick?

Pick the connection that matches your contracts and your firm, because the speed gaps are smaller than the fee and fill gaps. From Chicago the connections sit within a millisecond of each other. Fees at Apex, meanwhile, swing by as much as $0.88 per E-mini round turn.

Which of these sounds like you?

Ready to automate the one you picked? PickMyTrade costs $50 a month, $120 a quarter or $350 a year on the current sale. Every plan includes unlimited strategies, trades and accounts, plus a 5-day free trial.

Compare plans and pricing, meet the team behind it, or ask us which connection your firm’s accounts use before you buy an evaluation.

Frequently Asked Questions

The Short Version

Rithmic vs Tradovate isn’t a speed contest for most traders. From a Chicago VPS both connections sit within a millisecond of each other. A TradingView webhook spends 22 to 111 ms just crossing from Oregon, so pick on fees, fills and what your firm offers.

The fee gaps are real. At Apex, Tradovate saves $0.88 per E-mini round turn, while Rithmic saves 32 cents per micro crude round turn. NinjaTrader adds $0.25 per contract whenever you route through Rithmic or CQG Desktop.

Evaluation fills follow a simulator’s rules rather than the exchange’s, so test the one your firm uses. CQG remains a sound broker-side route, but find out whether your firm’s “CQG” is really Tradovate before you buy.

If your strategy lives in TradingView, the bridge matters more than the connection. Start with the free trial and forward-test on a demo before any evaluation money is on the line.

Disclaimer:
This content is for informational purposes only and does not constitute financial, investment, or trading advice. Trading and investing in financial markets involve risk, and it is possible to lose some or all of your capital. Always perform your own research and consult with a licensed financial advisor before making any trading decisions. The mention of any proprietary trading firms, brokers, does not constitute an endorsement or partnership. Ensure you understand all terms, conditions, and compliance requirements of the firms and platforms you use.

Also Checkout: Apex Copy Trading Rules: What Gets an Account Failed