TradingView automation without a VPS or always-on PC means removing the extra infrastructure used only to receive and relay alerts. NRUNO hosts that routing layer while your execution environment remains separate.
A DIY bridge usually needs a public HTTPS endpoint, a running server process, certificates, firewall rules, updates and monitoring. NRUNO hosts the webhook and routing layer, so TradingView sends the alert to a managed endpoint instead of to infrastructure you maintain.
Your personal desktop or laptop does not need to stay online just to receive a TradingView alert. You also do not need an additional Windows VPS only for NRUNO’s cloud routing. This is useful for overnight Forex, crypto and strategies that trigger while you are away from the computer.
Cloud routing does not replace cTrader or the broker environment. The connected cTrader side must still be available, and normal conditions such as market hours, maintenance, spread, liquidity and broker rejection continue to apply.
A webhook can arrive successfully while execution later fails. A useful setup therefore separates signal, webhook receipt, connector processing, cBot connectivity and the final cTrader result. This makes an overnight system diagnosable instead of simply 'always on'.
Start in Paper Mode. Trigger the same alert repeatedly, verify symbol and volume mapping, then check the final cTrader-side result. Only move to Live after the complete chain is predictable and you understand the availability requirements of your cTrader environment.
Primary sources: TradingView webhooks · Webhook security
Yes for the NRUNO webhook/routing layer. The connected cTrader execution environment still needs to be available.
No, not for NRUNO’s hosted webhook and routing layer.
No. Platform maintenance, broker conditions, market hours and liquidity still matter.