You started a bot on a Docker runner three weeks ago, forgot about it, and now your credit balance is lower than expected. Was it CPU? Was it the OHLCV cache filling up disk? Was it just running longer than you thought? A flat "$0.08/hour" line item can't answer that — you need to see what the container actually consumed.
Your bot closes a winning trade at 3 AM. The exchange confirms the fill. Freqtrade logs it. And then the Kubernetes node gets recycled during a cluster upgrade — and the trade disappears. No history. No PnL record. No data for the next backtest.
A bot that misses a stop-loss because its container restarted is not just an inconvenience — it can convert a -3% planned exit into a -12% surprise. The hosting model under your bot is the second-most consequential decision in algorithmic trading after the strategy itself, and most traders pick it by accident on day one. This guide compares the shared public runner with a runner on infrastructure you own, and shows how self-hosting actually works on VolatiCloud: there is no agent to install. You give VolatiCloud a TLS-protected connection to your own Docker host or Kubernetes cluster, and it deploys bots there.