An automated trading VPS hosts the desktop applications your bot, Expert Advisor (EA) or strategy needs when your own computer is off. Choose hosting by where the code runs, then check how the whole workflow recovers. A server being online does not establish that its platform, data feed and strategy are ready.
Identify what actually needs hosting#
| Workflow | What must remain available |
|---|---|
| EA in a desktop MetaTrader terminal | The terminal, EA and broker connection on its Windows host |
| NinjaTrader desktop strategy or local copier | NinjaTrader and any required companion processes and connections |
| TradingView alert with no desktop dependency | TradingView’s hosted alert service; a Windows VPS is unnecessary just for that alert |
| Alert sent through a Windows bridge | The separate receiver and required Windows connector, as specified by its vendor |
| Fully hosted bot or cloud copier | The provider’s service and authorized connections; check for any separate desktop signal source |
TradingView confirms that alerts continue after its application or chart is closed. The receiving integration has its own dependencies; our TradingView webhook guide explains that boundary.
A general Windows VPS and MetaTrader’s integrated virtual hosting are different environments. MetaQuotes’ migration rules prohibit DLL calls and exclude scripts from migration. Do not assume a separate Windows copier or bridge fits that service. The rules also say migrated EAs can trade on the virtual platform regardless of the local trading-permission setting; turning off the local button is not a remote stop control.
For a Linux bot or an API service, check its own operating-system and deployment requirements. A Windows desktop may not be the environment it needs.
Size all the processes, not just the bot#
List the terminals, charts, indicators, history, bridges and copier receivers that will run together. Observe CPU and memory inside the VPS during representative activity, including the workload after a restart. Separate sustained stalls from brief loading spikes; avoid running a heavy optimization job alongside active automation without testing their combined load.
Use the NinjaTrader sizing guide for platform requirements and the copier hosting guide for multi-account dependencies. There is no universal bots-per-gigabyte allowance. Measure the VPS-to-provider route separately from how responsive Remote Desktop feels.
Distinguish a viewing disconnect from a restart#
Closing your remote connection can leave Windows applications running in the existing session. Signing out ends session applications; server policies and restarts can also end them. Microsoft documents the disconnect/logoff distinction. Use the Remote Desktop setup guide to rehearse returning to that session.
An application launching after a reboot is only the first recovery step. In MetaTrader, platform-wide and individual EA permissions both affect whether the desktop EA may trade. In NinjaTrader, connection-loss handling can keep a strategy running, recalculate it after reconnecting or stop it. Check the actual strategy’s configuration instead of assuming every tool resumes the same way.
Define what completed recovery looks like#
Write down an observable result for each layer:
| Layer | Evidence to check after recovery |
|---|---|
| Windows and applications | Correct user/session, expected platform and required companion processes |
| Account and data | Intended account/environment, connected provider and current data when the instrument’s session is active |
| Strategy or EA | Expected enabled state, permissions and startup behavior; no unresolved error in its log |
| Orders and positions | Actual account records agree with what the automation expects to manage |
| Copier or bridge | Intended destinations remain selected and ready; each receiver’s logs and account state are checked |
Follow the vendor’s restart sequence, with a check at each dependency before automation resumes. For NinjaTrader, review startup and account synchronization: synchronization options can place or close live trades. A connection recovery does not by itself reconcile strategy and account positions.
For automatic NinjaTrader recovery, we recommend our partner Ninja Watchdog. It detects disconnects, reconnects supported accounts including Rithmic and Tradovate, waits for live data and can restore interrupted strategies. It also supports relaunch after crashes or reboots and provides recovery reports. Configure and validate it for the intended workflow; it cannot repair an unavailable provider. Verify copier and account state after recovery. See our recommended tools for the partnership disclosure and related tools.
Rehearse failure recovery in simulation#
Use a supported demo or simulation environment with live order routing excluded. This is a procedure to run on your configuration, not a claim that we tested your strategy:
- Save a baseline. Record versions, account mappings, strategy settings and the expected states in the table above. Export the workspace with the platform’s supported backup process and retain a copy outside the VPS.
- Test one interruption at a time. First disconnect only the viewing client. Separately rehearse a provider disconnect or application restart using the vendor’s test procedure. Keep these tests separate so you know what recovered.
- Inspect each layer. Record timestamps, log messages and which steps were automatic or required intervention. Check for duplicate platform instances or receivers; do not replay missed actions blindly.
- Confirm the resumed workflow. Trace a permitted simulation event through the strategy and any receiver, including the resulting account records. Retest after material platform, add-on or recovery-setting changes.
Keep logs and the recovery instructions available outside the affected machine. An alert saying a process restarted is useful evidence, but completed recovery requires checking its downstream state too.
Use the automation setup guide for account routing and connecting the components, or the NinjaTrader troubleshooting guide when a layer fails. Once the Windows dependencies and capacity are clear, compare Ninja Mobile Trader VPS plans.