NinjaTrader client
One strategy on the chart. The server decides what it may do.
The Bridge shows everything and arms nothing on its own.
Pair once
Read the Machine ID from NinjaTrader (Help → About), register it in Forge, and ConnectQ approves it. Unknown machines are listed as pending and receive nothing.
Deploy per chart slot
Each chart runs one slot. From Forge you assign a proven setup to a slot; the Bridge picks it up within a poll cycle. Remove it and the chart stops arming just as fast.
Nothing arms from the chart
The strategy has no parameter that enables trading. Enablement is a server decision per machine and setup, with a global kill switch that disarms every client within one poll.
Trading a funded account takes a second grant, separate from the first and off by default: a newly paired machine can trade simulation and Playback only until ConnectQ turns it on for that machine. Revoke the machine, withdraw the grant, or let the configuration go stale, and it returns to simulation on its own.
Fail-safe by default
If the Bridge cannot reach ConnectQ beyond its time-to-live, it arms nothing new. Live trading requires a fresh, signed configuration.
It reads your setup, not a summary
The Bridge parses the blocks and the nested gate tree you built and evaluates them on every bar. How much NinjaTrader reconciliation sits behind each block differs, and the chart and the setup screen both say which.
Full context on the chart
Bias, levels, swing-failure state, order flow and the reasoning panel — the same picture the model used — drawn on your chart so you can watch it work.
On the chart
What the panels tell you
Your setup, read back by the strategy that trades it — the same nested tree, evaluated every bar. Each row says what it reads, what it needs and how far off it is, so a condition about to turn looks nothing like one that is nowhere near.
Standing down, and saying why. Lose the server for longer than the configuration’s time-to-live and the client disarms itself rather than trading on a stale copy — then it tells you the tape is too thin to trade by hand either.
Afterwards
And a record of what it actually did.
The panels above show what the Bridge is thinking. The journal shows what it did. Every trade is written the moment the order fills — direction, size, the price it got, where the stop and target went — and completed when the position closes, with which bracket closed which leg.
Trades are grouped by the run that took them: one session per enable-to-disable of a chart. A chart that armed all day and fired nothing leaves no group behind, so the list is what happened and not a log of what did not. Simulation and Playback sessions are kept and labelled rather than hidden.
It is a record, not a verdict. A handful of live trades cannot grade a setup — that is what the holdout is for — so the journal carries no stamp and says so on its own screen.
Every trade the Bridge took, grouped by the run that took it — and a run appears only if it traded. The row is written when the order fills and completed when the position closes, so a trade still running shows no result rather than a zero.
Requirements
- Platform
- NinjaTrader 8 on Windows. Any data feed NinjaTrader supports; tick data recommended.
- Markets
- NQ futures at launch. Other CME index futures follow once their datasets are curated.
- Accounts
- Sim, playback and live accounts. Prop-firm accounts supported where the firm allows automated strategies.
- Connectivity
- Outbound HTTPS to ConnectQ. No inbound ports. No credentials stored on the chart other than your API token.