Sized per account
A whole-number multiplier each. Contracts are indivisible, so there is no 0.5× that has to round somewhere and size you wrong without saying so.
Applied before dispatchNinjaTrader
Automated NinjaTrader, without writing NinjaScript.
NinjaTrader automates well if you write NinjaScript and keep a machine running. If your strategy already lives somewhere else — a TradingView chart, a Python script — then rewriting it in C# to get it executing is a strange amount of work for a translation job.
Two routes to automated NinjaTrader
NinjaScript. The native path. You write your strategy in C# inside NinjaTrader, and it runs inside the platform on your machine. Full access to the platform's internals, and full responsibility for the machine staying awake and connected.
A signal from outside. Your strategy stays where it is — a PineScript alert, a script, anything that can send an HTTP request — and something else turns its output into live NinjaTrader orders. No C#, and nothing running at your desk.
Quanify is the second. It is not better than NinjaScript; it is the right answer to a different question. If your logic needs the order book, the platform's indicators or bar-by-bar internals, write NinjaScript. If your logic already exists and you just want it placing orders, translating it into C# buys you nothing.
Strategy needs platform internalsOrder book, native indicators, bar-by-bar state. Write NinjaScript.Native
Strategy already exists elsewherePineScript, Python, your own service. Send the signal instead.Webhook
You do not write C#Rewriting a working rule in a new language to execute it is a poor trade.Webhook
Nothing can stay runningA NinjaScript strategy needs the platform open. A webhook does not.Webhook
What the outside route looks like
A strategy in Quanify is a URL that accepts a POST. You paste it into a TradingView alert's webhook field with a short JSON body — the panel builds the exact body for you, already matching that strategy's settings — and that is the integration.
There is no add-on to install in NinjaTrader, no bridge process, no SDK and no C#. The receiver accepts any content type, which matters more than it sounds: TradingView posts as text/plain, and receivers that insist on application/json are why so many first attempts return "no response".
{
"action": "{{strategy.order.action}}",
"ticker": "{{ticker}}",
"contracts": "{{strategy.order.contracts}}",
"market_position": "{{strategy.market_position}}"
}The token in the URL is the credential — treat it like a password, and set a webhook password on the strategy if you want a second factor.
The part that is not about NinjaTrader at all
Automating one account is the easy half. The reason most people end up here is that they have several.
Every account you attach carries its own whole-number multiplier, applied server-side before the order is sent. One signal becomes correctly-sized orders on a personal account, a funded account and an evaluation, without any of them being sized for the others.
And nothing arms itself. A new strategy is created powered off, every account you attach lands disabled, and a trader will not report itself armed until the engine has confirmed the routing. Configuring is not arming — that is two separate decisions on purpose, because the expensive failure in automation is a strategy that was live when you thought it was not.
Never flattens you
Powering a strategy off stops new orders reaching your accounts. It never closes a position on your behalf, under any circumstance.
Open positions stay yoursWhere it runs
This is the practical difference. A NinjaScript strategy runs inside NinjaTrader, so NinjaTrader has to be open, connected and on a machine that is awake — which is what a VPS is usually rented for.
Quanify holds the broker connection itself, server-side. The alert that fires at 3am reaches your accounts whether or not your laptop is open, and there is no desktop process whose crash you find out about from a position you did not expect — or from one you expected and do not have.
Common questions
Can I automate NinjaTrader without NinjaScript?
Yes. Quanify connects to your NinjaTrader account and places orders from a webhook, so a TradingView alert or any HTTP request can drive it. There is no C# to write and no add-on to install in the platform.
Do I need NinjaTrader open for automated trading?
With NinjaScript, yes — the strategy runs inside the platform. With Quanify, no: the broker connection is held server-side, so orders are placed with your machine off.
Can I send TradingView alerts to NinjaTrader?
Yes. Create a strategy in Quanify, put its webhook URL in the TradingView alert, and paste the JSON body the setup panel generates. TradingView fires from its own servers, so nothing in the path depends on your computer.
Do I need a VPS to automate NinjaTrader?
Only for the NinjaScript route, where the platform has to stay running. The webhook route has nothing of yours in the path, so there is no machine to keep awake.
Should I use NinjaScript or a webhook?
NinjaScript if your logic needs platform internals — the order book, native indicators, bar-by-bar state. A webhook if your strategy already exists somewhere else and you simply want it placing real orders. Rewriting a working rule in C# just to execute it buys you nothing.
Can one alert trade several NinjaTrader accounts?
Yes. Each account you attach applies its own whole-number multiplier, so one signal becomes correctly-sized orders across a personal account, a funded account and an evaluation.
More on automation
Automated futures trading, on accounts you already have.Automate a futures strategy on your own broker accounts. A webhook fires, Quanify risk-checks and sizes it, and the order reaches your broker.Your strategy, executed on your live accounts.Automate any futures strategy on Tradovate, NinjaTrader or TopstepX. Send a webhook; Quanify risk-checks, sizes and routes it. No VPS, no glue code.The bot is your strategy. This is the part that trades it.A trading bot is a strategy plus an executor. Quanify is the executor: your rule fires a webhook, it is risk-checked and sized, the order goes out.Automating TopstepX, without writing the layer underneath.What automating a TopstepX account actually requires, what the hard parts are, and how to route a strategy to it without writing an execution layer.Your strategy, or one you can inspect.Run your own futures strategy through a webhook, or add a published Quanify strategy with its full forward record. How strategies work and are measured.Turn a TradingView alert into a live order.Send a TradingView alert to one webhook. Quanify resolves the contract, sizes the order, applies your risk rules and routes it to your broker.The Tradovate API, and what building on it really costs.What building on the Tradovate API actually costs you: OAuth, WebSocket sessions, contract resolution, reconnects. And what you get if you skip it.
Start on a simulated account.
Connect a sim or evaluation account and run the whole product against it before you point anything at live money. Nothing about the setup changes when you do.