Cloud Trade Copier: When You Really Can Trade Without a VPS
A cloud dashboard does not always remove the execution platform. Learn what must stay online for NinjaTrader 8 and Tradovate trade-copying workflows.
You want to close the laptop without wondering whether the next follower order will disappear with it. That is the promise behind a cloud trade copier.
The problem is that “cloud” can describe several different parts of the workflow. The dashboard may be hosted. The account map may be stored on a server. The routing service may run in a data center. The execution platform can still depend on a desktop application.
That distinction decides whether you really can trade without a VPS.
The direct answer
A trade copier can run without your own VPS when the broker or execution platform exposes an API that a hosted service can use directly.
Tradovate is an example of an API-native path. After you link an eligible Tradovate account, CrossTrade can receive a TradingView webhook and route a supported order through the hosted connection. NinjaTrader 8 does not need to be part of that workflow.
NinjaTrader 8 is different. If NT8 is the execution platform, NinjaTrader must remain running and connected somewhere. CrossTrade also needs its XT Add-On connected inside NT8. That machine can be your desktop or a Windows VPS, but there is still a machine in the path.
A browser dashboard does not make NinjaTrader 8 cloud-native.
Four parts of a copier workflow
Most confusion disappears when you separate the workflow into four parts.
1. The signal
The signal may come from a manual order, a NinjaScript strategy, a TradingView alert, an application, or an AI client.
2. The configuration
This is the account map, copy mode, sizing rule, instrument replacement, inversion setting, and other copier logic. A vendor can store this configuration in the cloud.
3. The routing service
The routing service receives an event and determines what should happen on each mapped account. It may also run in the cloud.
4. The execution connection
This is the component that can actually submit, change, or cancel an order on the destination account. It may be a broker API or a desktop platform such as NinjaTrader 8.
A vendor can honestly describe parts two and three as cloud-hosted while part four still requires a running desktop platform.
The NinjaTrader 8 path
A CrossTrade NinjaTrader workflow looks like this:
- A supported signal reaches CrossTrade or occurs in the source NT8 account.
- The CrossTrade service and Trade Copier apply the configured workflow.
- The CrossTrade XT Add-On communicates with NinjaTrader 8.
- NinjaTrader submits the supported action through the account connection.
The important operational fact is step three. If NinjaTrader or the add-on is disconnected, the execution path is not fully available.
This is why a Windows VPS is common for NT8 automation. The VPS is not the copier. It is a continuously available Windows machine that keeps NinjaTrader, its connections, and required add-ons running when your personal computer is off.
Read the CrossTrade connection resilience guide before deciding where to run NT8.
The Tradovate path
An eligible CrossTrade Tradovate workflow can look like this:
- TradingView sends a valid webhook alert to CrossTrade.
- CrossTrade validates the request and selects the linked Tradovate destination.
- CrossTrade routes the supported order through the hosted Tradovate connection.
- The result appears in CrossTrade Alert History and the linked account state.
There is no NinjaTrader installation in that path. You do not need to keep your own desktop or VPS online for CrossTrade to route the supported Tradovate webhook workflow.
Start with Automate Tradovate from TradingView and the NinjaTrader and Tradovate destination guide.
Cloud-native does not mean risk-free. You still need to confirm the account, contract, quantity, order type, and result. Test the complete route in Demo before using an eligible live account.
What a VPS solves
A VPS can solve availability problems for a desktop execution platform:
- Your personal computer can shut down without shutting down NT8.
- The Windows environment can stay closer to a stable network connection.
- Scheduled updates and restarts can be managed as part of an operating process.
- The same known environment can run the required NT8 add-ons.
A VPS does not guarantee:
- Identical fills across accounts
- Zero slippage
- A permanent broker connection
- A strategy without defects
- Prop-firm compliance
- Recovery from every unknown account state
You still need monitoring, logs, reconciliation, and a rollback procedure.
Questions to ask any cloud copier vendor
Do not stop at “Do I need a VPS?” Ask the questions that define the path.
What submits the follower order?
Is it a broker API, a hosted platform API, NinjaTrader 8, or another desktop application?
What must stay online?
Ask about the trading platform, connector, add-on, browser, phone, and vendor service separately.
What happens during a disconnect?
Does the system pause, queue, retry, reject, or attempt to reconcile? What state can the trader inspect?
Can I see a follower rejection?
A clean dashboard is not enough. You need an order or event trail that explains whether the follower action was dispatched and accepted.
Which order types and lifecycle events are supported?
Test entry, stop, target, change, cancel, flatten, and partial fills when available. A copied entry alone is not a complete copier test.
How are account and instrument mappings verified?
A typo in an account or contract can defeat a technically healthy connection.
What evidence can support use?
Save timestamps, order identifiers, source and follower accounts, expected behavior, actual behavior, and logs.
How to test the architecture before going live
Use one simulation source account and one simulation follower.
- Confirm the execution connection.
- Use one-to-one sizing.
- Place or trigger the smallest useful test order.
- Verify the source action.
- Verify the follower action.
- Test the stop and target.
- Test change, cancel, and flatten behavior.
- Interrupt the relevant connection in a controlled simulation test.
- Restore the connection and compare positions and working orders.
- Add only one follower or rule at a time.
Use the pre-live Trade Copier checklist and Trade Copier troubleshooting during the test.
Where CrossTrade fits
CrossTrade supports two distinct paths:
- NinjaTrader 8: TradingView, API, MCP, and copier workflows through the CrossTrade XT Add-On. NT8 and the add-on must remain connected.
- Tradovate: Eligible hosted webhook and API workflows through a linked Tradovate connection. Your own NT8 installation or VPS is not required for that route.
The CrossTrade Trade Copier is part of a broader system that also includes webhook automation, account controls, REST, WebSocket, MCP, signal history, logs, and diagnostic tools.
That does not make CrossTrade the right choice for every platform. If another vendor supports a connection CrossTrade does not, that may decide the comparison. Read the CrossTrade vs TradeSyncer comparison for the workflow differences.
The useful definition of cloud
“Cloud” is useful only when it tells you which responsibility moved off your machine.
For Tradovate, the execution connection can be hosted. For NinjaTrader 8, the configuration and routing can be hosted while NT8 still runs on a Windows machine.
Once you know that, the decision becomes practical. Choose the platform route that fits your accounts. Keep the required component available. Test the full lifecycle. Save enough evidence to understand a mismatch.
CrossTrade is not affiliated with or endorsed by NinjaTrader, TradingView, Tradovate, or TradeSyncer. Product and trademark names belong to their respective owners. Platform support and prop-firm rules can change.
