Best VPS for TradingView Alerts & Webhooks

What runs where when an alert fires

Knowing which part lives on TradingView's servers and which lives on yours is the key to automation that doesn't silently break.

1. TradingView servers

   1.Alert condition triggers

   Your Pine Script strategy or indicator alert fires on TradingView's side, even with your browser closed.

   →
2. TradingView servers

   2.Webhook is sent

   TradingView POSTs your alert message as JSON to the webhook URL you set on the alert.

   →
3. Your MarginVPS server

   3.Receiver validates it

   Your always-on webhook app checks a shared secret, logs the alert, and turns it into an order.

   →
4. Your broker

   4.Order executes

   The order leaves from a data center next to your broker, not from your home connection.

A minimal webhook receiver you can run today

Install Python on your VPS, save these two snippets, and point a TradingView alert at http://YOUR-VPS-IP/tradingview. Swap the logging line for your bridge or broker API call.

# webhook.py: receives TradingView alerts on your VPS
from flask import Flask, abort, request
import json, logging

SECRET = "change-me"  # must match the "secret" in your alert message

app = Flask(__name__)
logging.basicConfig(filename="alerts.log", level=logging.INFO)

@app.post("/tradingview")
def tradingview():
    alert = request.get_json(force=True, silent=True) or {}
    if alert.get("secret") != SECRET:
        abort(403)
    logging.info(json.dumps(alert))
    # Forward the alert to your bridge or broker API here.
    return {"ok": True}

if __name__ == "__main__":
    app.run(host="0.0.0.0", port=80)

{
  "secret": "change-me",
  "symbol": "{{ticker}}",
  "action": "{{strategy.order.action}}",
  "contracts": "{{strategy.order.contracts}}",
  "price": "{{close}}"
}

TradingView only sends webhooks to ports 80 and 443, so allow port 80 in Windows Defender Firewall. For production, put the receiver behind HTTPS and keep the secret out of source control.