How automation on NinjaTrader actually works

A NinjaTrader strategy is compiled code. It watches incoming price data, applies rules, and when those rules are satisfied it sends an order to your broker. No part of that requires you to be present, which is the entire point and also the entire risk.

The mechanism is not complicated. What people underestimate is everything around it — where the code runs, what happens when something interrupts it, and who is responsible for noticing.

Where the code runs

There are two arrangements, and almost every practical difference between products in this category follows from which one they use.

• On your machine. The strategy is installed into your NinjaTrader and executes there. Your computer is doing the watching and the order sending, so it needs to be awake, connected and left alone. This needs a paid platform licence — see the licence article — and in practice a rented always-on machine.
• On the vendor’s servers. The strategy runs on their infrastructure and the resulting orders route to your broker account. Nothing of yours needs to stay awake, the free platform tier covers it, and there is no machine to maintain. Access ends when the subscription does.

What happens when something breaks

This is the part the sales pages skip, and it is where automated trading actually goes wrong. Not dramatic blow-ups — dull interruptions:

• The data feed drops mid-session. The strategy is now blind. Does it flatten, hold, or resume when data returns? A well-built one has a defined answer; a poorly-built one does whatever happens to occur.
• The platform restarts. Windows updates, a crash, a power cut. Does the strategy come back up by itself, and does it know about positions it had open before?
• The broker connection drops. Orders may be rejected silently. Something has to notice and retry, or you find out hours later.
• A position is open and nobody is watching. Stops attached at the exchange behave differently from stops held locally by the platform — if the local software is gone, so is a local stop.

With local execution, every one of those is yours to handle. With server-side execution, most of them are the vendor’s. That is the single most useful thing to understand about the two models, and it is worth far more attention than the difference in subscription price.

Backtests are not the same as executed orders

NinjaTrader can run a strategy against historical data and report what it would have done. That is genuinely useful for development and genuinely misleading in marketing, because a backtest is a strategy’s performance against history it already knows.

Fills are assumed rather than real. Slippage is modelled rather than suffered. A strategy tuned until it looks good on a particular stretch of history has learned that history, not the market. None of that makes backtests worthless — it makes the label essential. A vendor that badges backtested records as backtests, rather than mixing them into a list of executed orders, is doing something most do not.

What automation does and does not change

It changes consistency and attendance. A rule executed identically every time, including at 3am and on the day you are in a meeting, is a different thing from the same rule executed when you happen to be watching. For a trader who knows their rules are sound but their discipline is not, that is worth real money.

It does not change whether the rules work. Automation is an execution technology, not a source of edge, and no amount of consistency rescues logic that does not hold up. Marketing in this category regularly implies otherwise, and that implication is the single most reliable signal that a vendor is selling to optimism rather than to traders.

What this means in practice

Before subscribing to anything, get four answers: which platform version, which contracts, where execution happens, and what the recovery behaviour is when a feed drops. The first two are usually on the sales page. The third and fourth usually are not, and they are the ones that decide your monthly cost and your risk while you are asleep.

The product reviewed on this site runs server-side, on NinjaTrader 8 only, trading NQ, ES, YM, RTY — full-size and micro, with 1% per position, with stop losses as the shipped default. The full review carries every figure with its source and check date, and the pre-purchase checklist covers what to have ready before day one.