What Is Rithmic? The Data Feed Behind Most Futures Prop Firms

Open almost any futures prop account and your prices and orders quietly flow through a company most traders have never heard of. That company is Rithmic, the low-latency backbone under NinjaTrader, Quantower and a long list of prop firms. Understanding it explains why your fills, your platform options and even your choice of firm are what they are. This guide is dated June 2026, and the moving parts (firm platform lists, rail licensing, exchange coverage) change fast, so treat any specific name or number here as something to verify against rithmic.com and your firm's current platform page.

What Rithmic is

Rithmic is a futures market-data and order-routing infrastructure provider built for low latency. Its own positioning is blunt: "Trading Infrastructure for Futures." That is the cleanest way to think about it. Rithmic is not a broker, and it is not a prop firm. It is the plumbing that carries prices to your screen and orders to the exchange.

The company runs both a developer interface and its own front-end software. R | API is the developer layer that third-party platforms build on. R | Trader and R | Trader Pro are Rithmic's own trading applications. The pipe styling in those names (R | Trader, R | API) is Rithmic's house convention, not a typo.

On the data side, Rithmic delivers real-time Level 1 and Level 2 market data plus order execution and routing. It markets the feed as exchange-direct, with language like "no aggregation, no conflation, no artificial delays," and offers Market-By-Order (MBO) depth that resolves the book down to individual orders rather than just aggregated price levels. That phrasing is Rithmic's own and can change, so confirm the current wording on rithmic.com if you plan to quote it.

The gateway model

The architecture is simple and durable. The chain runs from your platform, to a Rithmic gateway, to the exchange matching engine. The gateway does double duty. It carries market data inbound (exchange to you) and order execution outbound (you to exchange) over the same Rithmic rail. One pipe, both directions.

This is why connecting a Rithmic-based platform always involves two small but real choices. First you select a "System," which is roughly the environment you are connecting to (the live trading system versus a paper or simulation system). Then you pick a gateway, and the standard advice in NinjaTrader, Topstep and Earn2Trade connection guides is to choose the gateway closest to you. That nearest-gateway step is not cosmetic. It is the user-visible knob that shortens the physical network path.

Rithmic positions its gateways near major exchange matching engines and operates multiple global connection points. Chicago, sitting next to CME, is the marquee location. You may see a specific count of connection points cited around the web, but that figure does not come from Rithmic's own page, so do not anchor on a number. "Multiple global connection points" is the honest framing.

One gateway carries both your prices and your orders. Pick the one nearest you, and you have shortened the entire round trip in a single setup step.

R Trader Pro vs R API

People conflate these two constantly, so pin down the difference. R | Trader Pro is the platform you click. R | API is the plumbing that third-party platforms, copiers and bots talk to.

R | Trader Pro is a full desktop trading application. You get a DOM and price ladder, one-click order entry, live charting, server-side risk controls, and a genuinely useful two-way real-time Microsoft Excel interface that streams quotes, P&L and orders into a spreadsheet (with roughly 100 studies available). It is typically provided free with your Rithmic credentials through a broker or firm. "Typically" is the operative word. Whether it is bundled is firm and broker specific, and you still pay exchange market-data fees separately on top. Confirm both with your own firm.

R | API is the licensed software side: libraries (C++ and/or .NET) plus interface definitions distributed to professional customers. It exposes un-throttled real-time market data, historical tick data, historical one-minute bars, and order execution and management. R | API+ extends the R | Trade Execution Platform with custom time, tick, volume and range bars, symbol look-ups, and server-side trailing stops, OCOs and brackets. Server-side is the key word there, because the exit logic lives on Rithmic's infrastructure rather than only inside your local app.

Why prop firms use Rithmic

Low latency, reliability, broad platform support, and direct CME Group connectivity have combined to make Rithmic a standard backbone for futures prop firms. That status is stable and well established. The specific roster of firms is not, because firms add and drop rails over time.

As of this writing, major firms widely reported to run on Rithmic include Apex Trader Funding, Topstep, Bulenox and MyFundedFutures. Treat that list as a snapshot, not gospel. A firm can switch rails between the time this is published and the time you read it, so check the firm's current platform page before you buy. The platforms that speak Rithmic are a steadier signal. NinjaTrader, Quantower, Sierra Chart, MotiveWave and ATAS all connect over Rithmic, alongside Rithmic's own R | Trader and R | Trader Pro. NinjaTrader and Rithmic in particular have a long-standing direct integration. Sierra Chart connects too, but it requires its own paid subscription on top.

You will also see a precise count like "dozens of platforms connect to Rithmic," sometimes pinned to an exact number. Those exact figures tend to come from third-party blogs rather than Rithmic, so "dozens" is the safe phrasing. On exchange coverage, the reliable anchor is CME Group in full: CME, CBOT, NYMEX and COMEX. Other venues sometimes appear in coverage descriptions, but those mentions are secondary-sourced, so verify them directly if they matter to what you trade. For the deeper comparison of Rithmic against the platform layer that reshaped this space, see our breakdown of Rithmic vs ProjectX data feeds.

Rithmic vs CQG and Tradovate

Rithmic is not alone. The two main competing rails are CQG and Tradovate, and each runs its own data and execution infrastructure. One idea saves you grief here: a prop firm picks one or more rails, and the platforms it can offer you follow from the rail or rails it exposes. The platform menu is downstream of the rail.

NinjaTrader is the clean illustration. It can connect via Rithmic, CQG or Tradovate, because it is a front-end, not a rail. That is exactly why the question "which platform can I use" always resolves to "which rail did my firm turn on." If your firm exposes Rithmic, your NinjaTrader connects over Rithmic. If it exposes Tradovate, it connects over Tradovate.

The positioning differences are directional. CQG is generally framed as the premium, most-expensive option, with institutional-grade reliability and exchange fees billed directly. Tradovate is a cloud-native broker and platform that runs its own rail. You will find specific monthly dollar figures quoted for CQG data tiers in various blogs, but those are time-sensitive and worth omitting unless you confirm current pricing, because data-fee schedules move. If you copy across mixed setups, our guides on Tradovate vs NinjaTrader for prop firms and copying trades across Tradovate, NinjaTrader, Rithmic and ProjectX go deeper on the cross-rail mechanics.

Latency and reliability

Latency is real, but it matters to a specific audience. It matters most to scalpers and to copiers and automation, where a master fill has to be mirrored to followers quickly and reliably. For a swing trader or a low-frequency discretionary trader, the rail's latency edge is largely irrelevant. If you hold for hours, 80 milliseconds is noise.

One thing to be careful about: do not treat any specific Rithmic latency number as a spec. Round-trip times depend on your location and your VPS far more than on Rithmic alone. Co-location near the exchange shortens the round trip. Trading from home over residential internet lengthens it. The honest statement is that co-location reduces round-trip latency, and your mileage depends on your VPS and location.

To make the stakes concrete, here is a fully worked, illustrative example. The inputs are assumptions for the arithmetic, not measured Rithmic figures, so plug in your own numbers before drawing conclusions.

Suppose you scalp MES and run a copier mirroring your fills to 4 funded accounts. Assume the end-to-end time from "see the master fill" to "follower order acknowledged at the exchange" is 8 ms on a low-latency Rithmic path from a Chicago VPS, versus 90 ms on a high-latency path from home internet through a distant gateway. The extra delay per copied order is 90 minus 8, which is 82 ms before the follower's order reaches the book.

Now translate that delay into slippage on a fast tick. MES moves in 0.25 index-point ticks worth $1.25 per contract per tick. Assume that in a fast move the market travels about 1 tick every 50 ms. The extra 82 ms divided by 50 ms per tick is 1.64 ticks of additional adverse travel before the follower fills. At $1.25 per tick, that is 1.64 times $1.25, or $2.05 of extra slippage per follower contract.

Scale it across the operation. With 4 follower accounts trading 1 contract each, that is 4 contracts, so 4 times $2.05 equals $8.20 of extra slippage per copied entry. Trade 30 round-trip scalps a day and you generate 60 fills (entries plus exits) that can each slip: 60 times $8.20 is $492.00 of extra slippage per day attributable to the slower path. Over a 20-trading-day month, 20 times $492.00 is $9,840.00.

The takeaway is directional, not a promise. For high-frequency copying and scalping, latency is a measurable cost you can buy down with co-location. For everyone else, it is money spent on speed you cannot use. This is also why a server-based copier matters more than the rail's raw number for replication work. Thor, the copier we build at Phoenix Technologies, runs server-side at roughly 17 ms copy latency precisely so the mirroring step is not the bottleneck. Our deeper look at NinjaTrader vs Quantower for futures charting covers the front-end side of the same trade-off.

Rithmic and your prop account

So how does this actually touch your account? Your firm hands you Rithmic credentials, which amount to a username, a System and a gateway. Any Rithmic-compatible platform you log into with those credentials trades the same account. Log into NinjaTrader and R | Trader Pro with the same credentials and they drive one account, not two.

A trade copier rides the same rail. It authenticates as a Rithmic client, either via R | API and R | API+ or by driving a Rithmic-connected platform, watches the master account for fills, and routes mirrored orders to the follower accounts over Rithmic. The catch is rail-matching. If your firm or account sits on a different rail, the copier has to speak that rail. A Rithmic copier will not copy a Tradovate-only account, and per-copier capability varies, so check your copier's supported rails before assuming it works.

This leads to the point most "which firm is best" debates miss. You do not really choose Rithmic. Your firm chooses it for you, and that choice silently fixes your platform menu, your copier compatibility, and how your fills behave. The smarter sequence is to ask "what rail is this account on?" first, and treat the platform list as a downstream consequence rather than a feature. A firm bragging that it "supports NinjaTrader and Quantower" is really telling you it exposes Rithmic. The ProjectX upheaval through late 2025 and into 2026, when ProjectX moved toward Topstep exclusivity (now living on as TopstepX) and other firms fell back largely to Rithmic- or Tradovate-based platforms, is the proof. Traders thought they were choosing platforms, but they were exposed to infrastructure and licensing politics they never signed up for. Those specifics are fast-moving and prop-firm-blog sourced, so verify the current state before acting on them.

Before you commit to a firm or a copier, run this checklist:

1. Identify the rail. Ask the firm directly whether the account is Rithmic, CQG, Tradovate or TopstepX/ProjectX. Do not infer it from the logo wall.
2. Match your platform. Confirm your preferred platform (NinjaTrader, Quantower, Sierra Chart, MotiveWave, ATAS or R | Trader Pro) actually connects to that rail. Remember Sierra Chart needs its own paid subscription.
3. Match your copier. Confirm your trade copier supports that exact rail. A Rithmic copier will not mirror a Tradovate-only or TopstepX-only account.
4. Right-size the latency spend. If you scalp or copy, prioritize a low-latency setup (co-located or Chicago VPS, nearest gateway). If you swing-trade, do not pay up for speed you cannot use.
5. Know your free fallback. R | Trader Pro is usually included with Rithmic credentials, so you can trade before buying a third-party platform. Verify with your firm.
6. Budget data fees separately. Exchange market-data fees are charged on top of the platform regardless of rail.
7. Check your resilience. Do not single-thread your whole operation on one firm's one rail. Know your migration path if licensing changes, the way ProjectX forced in 2025 and 2026.

And the honest tradeoffs, because Rithmic and copiers are not always the answer. A copier is the wrong tool when you trade a single account (nothing to mirror), when you are discretionary and low-frequency (the latency edge is wasted and the copier adds failure points), or when your accounts span different rails (one Rithmic copier cannot cleanly bridge Rithmic, Tradovate and TopstepX at once). Low-latency infrastructure is not a universal win either. For swing and position traders it is a monthly cost with no payoff, because the bottleneck is your edge, not 80 ms. "Rithmic equals best fills" is overstated. The rail moves your order to the exchange. It does not improve your slippage on a thin contract or rescue a bad entry, and CQG and Tradovate are production-grade rails too. Standardizing on one rail simplifies life right up until a licensing shock forces a migration. The convenience and the fragility are the same coin.

Frequently asked questions