WebhookTrade is a cloud order-routing service for MT4 and MT5: it hosts the terminal connection for you, in exchange for your MetaTrader credentials, at a per-connection price. Here is how it compares with a bridge whose risk engine runs where the order lands.
SignalForge against WebhookTrade, line by line. Their quotes are from their own pages, dated.
WebhookTrade prices from webhooktrade.com docs (subscription plans page) on October 29, 2026. Their quotes are from their own pages on that date.
A terminal drops for a few seconds now and then: a broker reconnect, a settings reload, an EA update. This is what each bridge does with an alert that arrives in that gap.
Their cloud hosts the MetaTrader connection for you, but a disconnect is on you: if the account goes down, orders fail in the dashboard and the fix is manual - "Go to the 'Connect to MetaTrader' page and re-establish" the connection (provisioning takes 1-2 minutes). They market "24/7 signal reception", yet no delivery queue or retry policy is documented, and duplicate orders are not handled server-side ("almost always caused by your TradingView setup").
If your EA checked in during the last 15 minutes, the alert is stored and handed over as soon as the EA is back, by push or by polling if the push channel is down. We hold it for 120 seconds; after that it expires without executing, so a late reconnect never fires a stale entry. Silent for longer, but seen in the last 2 hours? We answer TradingView with a retryable error and it resends the alert up to 3 times, 5 seconds apart. Past that, the alert is rejected and the reason goes to your signal log.
Their wording comes from webhooktrade.com (home and docs, including the subscription plans appendix), checked on October 29, 2026. Ours describes production behavior on the same date.
Reliability and the risk engine. Alerts that arrive during a reconnect are held and delivered with ack, duplicates are handled server-side, and the EA v4.09 checks risk before every order (stop inside the spread rejected, passed stop never opens, no naked positions, multi-TP by R, news filter, Prop Firm Shield). The trial is 14 days without a card against their 3, the latency figure is measured and published with its method, the terminal is visible in SFCloud, and everything exists in Spanish too.
Price per connection and simplicity. On annual terms the cost drops to $7.49-9.79 per MetaTrader connection, it supports MT4 AND MT5 from day one, setup is paste-your-credentials simple, and they also support Capital.com via API - a broker we do not cover. Their "how to connect TradingView to X" guides cover many brokers; if you just want the cheapest hosted pipe, that math matters.
Checked on webhooktrade.com (subscription plans appendix in their docs) on October 29, 2026. Their model is per MetaTrader connection; annual terms lower the per-connection price.
Their docs say the order fails in the dashboard and you re-establish the connection manually on the "Connect to MetaTrader" page. No delivery queue or retry policy is documented. Ours holds the alert for 120 seconds, delivers it when the EA is back, and confirms with ack.
No. They market "24/7 signal reception" without numbers. We publish measured medians (~180 ms webhook-to-EA, ~0.5 s to the broker-confirmed order) with the method, plus the caveat about broker queues that neither vendor controls.
Both hosted paths need MT5 credentials: WebhookTrade asks for the login and master password (stating they encrypt them before storage), and SFCloud hosts your terminal with credentials too - but shows you the live terminal in exchange. The EA-only path on your own MT5 or VPS needs no broker password from us at all, just a SignalForge token.
Two weeks on demo tells you more than any comparison table. Set your alerts, watch the executions, then decide.
Start the free trial →