Rithmic vs Tradovate for NinjaTrader: what actually differs

August 11, 2026·8 min read

If you trade with a futures prop firm, your account reaches NinjaTrader over one of two technologies: Rithmic or Tradovate. Most traders never choose. The firm issues one, the setup guide names it, and that is that.

It still pays to know which one you are on, because they behave differently in ways that only show up when something goes wrong — when you try to connect a second firm, when your charts freeze, or when your orders suddenly stop being accepted for no visible reason.

This is a plain comparison of the two, and what each one means for you inside NinjaTrader 8.

How to tell which one you are on

Your username usually gives it away.

A hyphen means Rithmic. Apex-123456, or something in that shape.
An underscore means Tradovate. Apex_123456.

The connection type you were told to set up in NinjaTrader confirms it. “Rithmic” and “Rithmic for NinjaTrader Brokerage” are both Rithmic — firms issue both and both are normal. The plain “NinjaTrader” connection is Tradovate-backed, which surprises people: a connection whose name says NinjaTrader is running on Tradovate underneath.

Some firms issue both and let you pick. Some have moved from one to the other and left old setup guides online. If your firm’s instructions and your username disagree, trust the username.

The one NinjaTrader restricts

Here is the difference most traders meet first.

NinjaTrader allows one Rithmic connection at a time. Try to log into a second Rithmic prop firm and the platform refuses, saying the provider already has a running connection. You disconnect one firm to reach the other, all day.

NinjaTrader has never limited Tradovate connections. Several Tradovate accounts run side by side with nothing installed and no configuration.

This catches people out, which is why the usual advice you will find on forums — buy a second computer, rent a VPS, run NinjaTrader 7 alongside NinjaTrader 8 — treats a software setting as a hardware problem.

So on raw connection count, Tradovate wins outright, and it is worth saying plainly: if every firm you trade is on Tradovate, there is nothing here you need to buy.

The one with a request budget

Tradovate wins on connections. Rithmic wins on headroom, and this is the difference that costs people money.

Tradovate meters your API activity. On a rolling 60-minute window you can initiate up to 5,000 unique actions. Placing an order, modifying an order, and cancelling an order each count as a separate action. Reach the ceiling and the server starts returning 429: Too Many Requests — at which point no further actions are accepted at all until it resets, or until Tradovate support resets it for you.

Five thousand sounds like a lot. It is a lot, for one account traded by hand.

It stops being a lot the moment you trade more than one account, and Apex spells out why on its own help pages: when you trade with groups, every trade on each account is a separate action, so placing an order on 20 accounts counts as 20 distinct actions.

Run the arithmetic and the ceiling arrives faster than anyone expects. One entry across 20 accounts is 20 actions. Give that entry a stop and a target and you are at 60 before the trade is even working. Move the stop once on every account — which any trailing logic does routinely — and that is another 20. A scalper taking thirty trades in a session across twenty accounts is not near the limit; they are through it.

Apex is also explicit that this is not their rule to bend: it is a Tradovate rule, and the firm cannot control it.

Rithmic publishes no equivalent cap. That is not a promise that you can send infinite orders — every broker protects itself somehow — but there is no documented per-hour action budget of the kind Tradovate operates, and hitting one is not a failure mode Rithmic traders spend their time working around.

What a penalty ticket is

When you cross the line, Tradovate does not simply reject the request. It issues a penalty response carrying two fields: a p-ticket and a p-time. The p-time is how many seconds you are expected to wait; the p-ticket is what you resend with once you have waited.

Flood it hard enough — a burst of reconnections is a common way — and the penalty escalates to a longer lockout, during which your API access is severely reduced or blocked entirely. That is the state where a trader discovers they cannot flatten a position through the platform, which is a considerably worse afternoon than a slow one.

Sessions, and why your first connection keeps dying

Rithmic has its own ceiling, and it is a different shape: sessions, not requests.

Every Rithmic login carries a maximum session count set by your firm. You can see yours in R|Trader Pro under File, then User Profile — and there is a separate number for market data and for orders.

When you go over it, Rithmic does not refuse the new session. It drops the oldest one. That behaviour produces one of the most confusing symptoms in futures trading: you open a second connection and your first one silently dies, over and over, with nothing anywhere explaining why.

Two different firms never do this to each other, because they issue different logins. It happens when the same login is open in more than one place at once — a second PC, a VPS, R|Trader Pro itself, or your firm’s own web platform sitting forgotten in a browser tab.

There is a way to conserve that budget. R|Trader Pro can hold one market data session and let other applications share it as plug-ins, so several NinjaTrader connections draw on a single feed instead of each opening their own. It is Rithmic’s own supported mechanism, not a workaround.

Gateways, and the latency nobody mentions

Rithmic runs its systems out of several physical locations — Chicago, Europe, Singapore, Tokyo, US East, US West, and a colocation point — and most carry a separate aggregated-data variant alongside the standard one.

Your firm names one. Almost nobody explains that the name is geographic, and that connecting to Chicago from Europe means every order crosses the Atlantic twice. If you are far from the gateway your firm defaults to, that is worth a conversation with them.

There is a second trap in the same dropdown. Live brokerage accounts and evaluation accounts do not use the same entry. Live accounts generally use “Rithmic 01 (Chicago)”; demo and evaluation accounts use “Rithmic Paper Trading (Chicago)”. Choosing the wrong one is the single most common Rithmic setup mistake there is, and the error it produces does not tell you that is what happened.

Two connections, two ways to fail

Whichever technology you are on, NinjaTrader tracks two separate things for every connection, and they fail independently:

The order session, which decides whether you can route an order.
The market data feed, which decides whether your charts are alive.

The platform gives you one indicator for both. That is why “am I connected?” has no single answer, and why a frozen chart gets mistaken for a dead broker so often. Your data feed can drop while your orders would route perfectly well — and the reverse, which is the dangerous direction: prices moving on screen while nothing you send can reach the market.

This is worth knowing regardless of which technology you use, because it is a NinjaTrader behaviour rather than a broker one.

So which is better?

Neither, and anyone telling you otherwise is selling something.

Choose Tradovate if you want several accounts connected with zero setup and you do not trade in a way that generates heavy order traffic.
Choose Rithmic if you copy trades across many accounts, move stops frequently, or scalp — the request budget is the thing most likely to interrupt your day on Tradovate, and Rithmic does not have one.

In practice you will rarely get to choose. Most prop firms issue Rithmic accounts, plenty issue Tradovate, and a few issue both. The useful thing is knowing which you have and what its failure mode looks like, so that when something goes wrong you are debugging the right problem.

If you are on Rithmic and need more than one firm

The one-connection-at-a-time limit is a flag NinjaTrader sets on its own adapter, and it can be cleared. That is what our Unlimited Prop Firm Connections add-on does: several Rithmic prop firms logged in simultaneously, in one copy of NinjaTrader, on the computer you already have — plus the exact System entry each firm needs, and connection health tracking for every connection you run, Rithmic or not.

If your firms are all on Tradovate, you do not need it, and the add-on itself has a Tradovate tab that tells you so.

Your Cart 0