IBKR vs Tradovate vs NinjaTrader: which to pick, and why two are the same company

The comparison is usually framed as three independent houses competing for the same trader. They are not, and that is the first thing worth knowing before you choose: two of the three are the same company.

Who owns whom?

NinjaTrader Group acquired Tradovate Holdings in 2022 for $115 million. In March 2025 Kraken announced it was buying NinjaTrader for $1.5 billion, a deal that closed in May 2025. So NinjaTrader and Tradovate sit under the same CFTC-registered FCM, and that group now belongs to a crypto exchange. They still run as separate brands, with different platforms and different accounts, but clearing, order routing and the corporate structure are behind the same counter.

Interactive Brokers has nothing to do with that group. It is a publicly listed multi-asset broker with access to exchanges worldwide: stocks, options, futures, FX, bonds and funds from a single account.

Practical consequence: comparing NinjaTrader with Tradovate compares two interfaces over related infrastructure. Comparing either of them with IBKR compares two different business models.

What each one is, in a sentence

The difference that actually decides: where your automation lives

If you are going to build something — automatic sizing, a trade journal, a risk dashboard — the useful question is not which has nicer charts, but what each one lets you do from outside its own interface.

• NinjaTrader runs your code INSIDE the platform: NinjaScript, which is C#, compiled against its own engine. Very powerful for strategies that live glued to the chart, and tied to a Windows machine being on.
• Tradovate exposes REST and WebSocket APIs, with per-second request limits and documentation carrying samples in several languages. Your code runs wherever you want and talks to the Tradovate cloud.
• IBKR offers three different surfaces depending on the job: the TWS API over a TCP socket (needs TWS or IB Gateway open), the REST Web API, and the Flex Web Service for pulling position and execution reports on a schedule.

That third IBKR route is the one almost nobody mentions and the one that saves the most trouble: a Flex report needs no open session and no process running on your machine. If all you want is to read your portfolio every night to compute risk, you do not need to keep a TWS running.

IBKR is unifying its APIs

IBKR is merging the Client Portal Web API, digital account management and the Flex Web Service into a single IBKR Web API with shared OAuth 2.0 authorization. Existing endpoints are not deprecated and keep receiving updates, so there is no rush to migrate — but if you are choosing today what to build on, it is worth knowing the direction.

Which one should you pick?

• You only trade futures and want the most direct environment: Tradovate if you prefer a browser and zero install, NinjaTrader if you want a heavy desktop and do not mind depending on Windows.
• You trade futures but also stocks, options or non-US markets: IBKR, because anything else forces a second account.
• You are going to automate and want your code to live outside the platform: Tradovate or IBKR. NinjaScript is excellent, but it is code that only runs inside NinjaTrader.
• You care who custodies the money and under what structure: all three are regulated, but it is worth knowing two of them are now part of a group owned by a crypto exchange.

What you will not find here: commissions, data fees or intraday margins. They change without notice, and any figure we wrote today would mislead someone six months from now. Check them on each broker's site the day you open the account.