What happens if Botely is down

Botely's SaaS (botely.trade) handles dashboard, signals delivery, wizard, settings. The trading bot is a separate Node.js process that runs on the same VPS (or wherever you host it for self-managed setups).

If the SaaS web is unreachable (deploy failure, DDoS, Vercel issue), the bot keeps running. If the bot is down (process crash, deploy failure), the SaaS still works but new positions aren't opened.

TP and SL orders are placed ON-CHAIN at position open time. They fire from the chain itself, not from the bot — meaning even if both Botely systems are down for hours, your positions still close at their TP or SL when the price moves there.

Max-hold is bot-side, not on-chain. If the bot is down, max-hold won't fire — your position stays open until TP, SL, or the bot comes back.

New signals won't be acted on. If the strategy fires an ETH long signal while the bot is down, that trade simply doesn't happen. No retroactive entry on restart.

Soft exits (early-loss, flat-exit, regime-exit) won't fire — they're bot-side logic. Position stays open until TP or SL, or until the bot comes back and re-evaluates.

The /app dashboard shows the bot's last heartbeat in the bottom-right corner of the open-positions panel (live indicator). If it's stale, the bot is down.

The /admin/logs panel (admin-gated) shows pm2 log tail of the bot process. If you don't have admin access, ask the founder.