Signals vs non-custodial autotrade

A signal is a structured event: "strategy v6.4 opened ETH long at $3,420 with TP at $4,172 (+22%) and SL at $3,078 (-10%), max hold 144h". You receive it via the delivery channel you configured (in-app, Telegram, email, webhook).

What you do with it is your choice: execute manually on your own broker, auto-execute via a script you wrote against the webhook, ignore it, or watch the paper trail accumulate to build conviction.

If you enable autotrade, the Botely bot runs ON your behalf using a agent wallet (Hyperliquid agent wallet) you authorise via the in-app wizard. You keep your seed phrase, main account stays under your owner wallet, and the agent wallet's scope is hard-limited to ETH/SOL/BNB perpetuals + the order-placement / cancel message types. The bot cannot withdraw funds, transfer between accounts, or trade other markets.

You hold three independent kill-switches: a per-strategy toggle, a master switch in /app/settings, and an agent wallet revoke that takes effect immediately. You can also close positions manually from the dashboard at any time — the bot picks up the new state on the next tick.

Botely's SaaS is then one of several execution paths you can use. If you'd rather run the bot on your own infrastructure, the code is open in the same repo as this site — clone it, configure your own Hyperliquid wallet, and you are the only consumer of the signals.

The signal is the IP. The bot is the execution layer. Many users want one without the other.

Some want fully manual trading on their own discretion. Some want fully automated execution with no daily attention. By keeping them separate, we let you choose.

Today: paid tiers ship signals + HMAC webhook + optional non-custodial autotrade. The Free tier is closed-trades-only as a verifiable track record. Public signups are still gated as we onboard friends-and-family first.

Tomorrow: open-public signups, a bigger fleet, and ongoing transparency reports. The signal feed and the autotrade model do not change — same payload, same permissioned-key scope, same kill-switches.