It supports two deployment styles: you can use the hosted cloud platform, or run everything on your own server, VPN, proxy, firewall, or private network so the Gunbot instance itself does not need to be exposed publicly.
What This Feature Means
You can use Gunbot Live as a cloud platform when you want hosted access. You can also run the stack on your own infrastructure when you want private network control. Private deployment can keep Gunbot behind a VPN, proxy, firewall, or private server instead of exposing the bot directly to the public internet. Use the crypto trading bot hosting checklist to review access, uptime, monitoring, updates, backups, and recovery.
Why Private Deployment Matters
Trading bots can expose strategy, balances, exchange usage, order behavior, local URLs, and access patterns. A cloud or private deployment model lets you choose the exposure level that fits your security requirements.
Good Practices
You can use least-privilege exchange API permissions. You can use VPN, proxy, firewall, or private server rules when self-hosting.
Trading Reality
It gives Gunbot a browser workspace for monitoring, strategy work, backtesting, risk review, history, and exchange-connected operations. These pages explain what the product does. Your account data stays on your local trading bot, behind login.
Operational Limits
The dashboard depends on the connected Gunbot instance, the exchange API, and the network between them. It can make problems easier to notice, but it does not remove market risk or take responsibility away from you: exchange permissions, strategy settings, open orders, and capital allocation still need your review.
Plain Definition
Cloud or private deployment means you can choose the operating model. You may want a hosted cloud platform for convenience, or you may want to run everything on your own server, VPN, proxy, firewall, or private network so the bot itself is not exposed to the public internet.
Deployment Models
| Model | Best fit | Main responsibility |
|---|---|---|
| Hosted cloud platform | Browser access without managing the whole stack. | Account security, permissions, and understanding connected setup behavior. |
| Private server | Infrastructure control. | Server maintenance, firewall, updates, backups, and access control. |
| VPN or proxy | Controlled access to a private bot endpoint. | Network routing, authentication, TLS, and who can reach the service. |
| Hybrid operation | Public docs or cloud access with private bot infrastructure. | Knowing which data is public, logged-in, local, or privately routed. |
Privacy Model
The important privacy claim is choice: you can use the cloud platform, or keep sensitive trading infrastructure behind your own network boundary without exposing the Gunbot instance publicly.
What Not To Expose
Do not expose exchange API keys, secrets, bot URLs with control access, raw config files with sensitive values, private strategy code, full history exports when one pair is enough, or admin routes without authentication and network controls.
External references
- official Gunbot local bot overview: Official context for local bot operation and user-controlled infrastructure.
- official Gunbot headless mode guide: Official guidance for VPS, detached GUI, private network, and resource-use considerations.
FAQ
Do I have to use the cloud platform?
No. The product can support hosted cloud usage or private deployment patterns depending on how you want to run and expose your Gunbot setup.
Can I run behind a VPN or proxy?
Yes. The private deployment concept is that you can keep sensitive Gunbot access behind your own server, VPN, proxy, firewall, or private network boundary.
Does private deployment mean nothing is exposed?
The goal is to avoid exposing the Gunbot instance publicly. You still need to configure your own network, credentials, DNS, proxy, and firewall rules correctly.
What is the difference between cloud access and private deployment?
Cloud access prioritizes convenience through a hosted platform. Private deployment prioritizes infrastructure control by keeping the bot behind your own server, VPN, proxy, firewall, or private network.
Does private deployment make exchange API keys safe automatically?
No. You still need least-privilege keys, secure storage, restricted access, backups, and careful sharing habits.
Last updated: