Where the bot runs
Cloud products such as Altrady and Bitsgap run provider-managed services. Gunbot runs locally. HaasOnline and OctoBot expose hybrid choices, so the same brand can present different boundaries by deployment.
Credential handling
A cloud bot needs usable trading authority. A self-hosted bot can keep secrets on the user's machine, but logs, configuration files, malware, backups and remote dashboards become part of the threat model.
Availability and maintenance
Providers manage cloud patches and uptime. Self-hosted users must monitor processes, apply updates, secure network access and recover from hardware failure. Delayed patching can erase the theoretical benefit of local control.
A practical choice
Choose cloud if you can verify provider controls and value managed operations. Choose self-hosted only if you can maintain the host, secrets and observability. In both cases use withdrawal-disabled keys and conservative limits.
Related product research
These profiles illustrate different architectures and evidence limits discussed in this guide.
Sources
TradeServer Cloud requirements — HaasOnline Documentation, accessed August 19, 2026.
OctoBot source code — Drakkar-Software, accessed August 19, 2026.
Gunbot security and privacy basics — Gunbot, accessed August 19, 2026.
Educational disclaimerThis guide is informational, not financial, investment, legal or security advice. Product and exchange controls change; verify current settings directly.