TradingView alerts do not need your computer or a VPS to remain open: they run on TradingView’s servers. A VPS becomes relevant when a separate part of your workflow—such as a Windows bridge, local copier, or companion application—must keep running.
TradingView confirms that alerts continue after you close the application or chart. Keeping TradingView Desktop open on a server is therefore not a requirement for alert continuity.
Locate the software after the alert#
| Workflow | What you need to host |
|---|---|
| TradingView alert notification | No additional desktop solely for the alert |
| Webhook sent to a vendor’s hosted integration | Check whether that integration also requires a local connector |
| Webhook followed by a Windows bridge or platform plug-in | The required Windows applications, wherever the vendor supports them |
| Your own webhook receiver | An internet-reachable application endpoint; it need not be a Windows desktop |
A common chain is TradingView alert → webhook receiver → bridge or trading platform → broker. These may be separate services. Ask the bridge vendor where each component runs before buying hosting.
Confirm that your broker or funded-account program permits the chosen bridge and automation method.
A webhook delivers a message to an application#
TradingView sends an HTTP POST to the configured URL when the alert triggers. Valid JSON messages use the JSON content type; other messages are sent as plain text. The receiving application’s required format determines what belongs in the message.
TradingView’s webhook documentation currently requires two-factor authentication, accepts ports 80 and 443, and cancels requests that take longer than three seconds. It also notes that delivery can fail. Do not put broker passwords or login credentials in the alert body.
A remote desktop address is not a webhook receiver. If you host a receiver yourself, it needs a properly configured endpoint and the integration’s authentication method. For custom receivers, TradingView documents certificate-based webhook authentication over HTTPS.
Separate alert delivery from an accepted order#
The alert log can show that a condition fired, and its webhook-status column can help investigate delivery. Neither proves that the bridge submitted an order or that the broker accepted it.
In a demo or simulation setup, follow the same event through the receiver and platform records. If the webhook arrived but the platform rejected the action, inspect the account, symbol mapping, permissions, and bridge message format. A faster VPS does not correct an invalid message or an unsupported integration.
When a Windows VPS is useful#
Choose a Windows VPS when the downstream tool requires a Windows application that must remain available after your personal device disconnects. Size it for that platform, its charts, and the bridge or copier running beside it.
If the entire integration is already hosted by its provider, a second desktop may add no useful component. For remote access to the TradingView application itself, see TradingView Desktop on mobile; that is a separate reason to host a desktop.
For a workflow with confirmed Windows dependencies, compare trading server plans. Hosting supports the applications you install; it does not turn an alert into a guaranteed trade.