▍ trading-bot
// docs / hosting

Where to run
your bot

The bot needs a machine that's on 24/7 with a stable internet connection. Any of these work — pick what fits your budget and comfort.

─────────────────────────────────────────────────────────────
// 01 — recommended

Cloud VPS — best choice

For €3-6/month you get a small Linux server that stays online 24/7. Set it up once, forget about it. This is what most people do.

provider plan price regions
Hetzner Cloud
EU-based, developer-friendly
 CX22 €4.15/mo DE, FI, US
Contabo
cheapest specs per €
 VPS S €4.50/mo EU, US, ASIA
DigitalOcean
easiest UI, US-focused
 Basic Droplet $6/mo US, EU, ASIA
Vultr
many locations, hourly billing
 Regular Cloud $5/mo 30+ worldwide

Prices as of Jan 2026. Any of them work — the bot uses ~200 MB RAM and negligible CPU. Choose based on location (closer to Binance's servers in AWS Tokyo = slightly lower API latency, but for our signal-based bot the difference is imperceptible).

// 02 — free tier

Free options

If you'd rather not pay for hosting, both work but come with tradeoffs.

01

Oracle Cloud Always Free

Forever-free ARM VPS. 4 vCPU / 24 GB RAM — massive overkill for a bot. Setup is more involved than paid providers, but truly free.

catch: hard to get an available instance, ARM architecture
02

AWS EC2 Free Tier

750 hours/month of t2.micro or t3.micro for 12 months — enough for one bot running 24/7. After 12 months you'll pay ~$8-10/mo.

catch: only free for a year
// 03 — home hardware

Run it at home

No monthly bill after buying hardware. Great if you already have something suitable.

▍

Raspberry Pi 4 or 5

~€60-80 one-time. Tiny, silent, sips 5W of power. Perfect for one bot. Install Raspberry Pi OS Lite (64-bit) or Ubuntu Server.

▍

NAS with Docker (Synology, QNAP, Unraid)

If you already have one — you already have a 24/7 Linux machine with Docker support. Add the container and you're done. UPS-backed against power flickers.

▍

Old laptop or mini-PC

An unused laptop with Ubuntu, lid open (or disable sleep-on-close), plugged in. Works. Just don't close the lid or reboot it.

!
Home internet trade-off: if your internet is unstable, the bot will miss signals during outages. For serious money, a VPS is safer than a home connection.
─────────────────────────────────────────────────────────────
// 04 — step by step: Hetzner Cloud

From zero to trading
in 5 minutes

Walkthrough for Hetzner Cloud (recommended). The steps for other providers are similar — create a Linux VM, connect via SSH, run one command.

  1. 1

    Create Hetzner account

    Sign up at hetzner.com/cloud. Verify your email and add a payment method (card or PayPal).

  2. 2

    Create a server

    In the Cloud console: + Add Server →

    • Location: any nearby datacenter
    • Image: Ubuntu 24.04
    • Type: CX22 (€4.15/mo)
    • SSH key: add yours or use password
    • Name: trading-bot

    Click Create & Buy Now. ~30 seconds later you'll get an IP address.

  3. 3

    Connect via SSH

    From your terminal (macOS/Linux) or PowerShell (Windows 10+):

    $ ssh root@<your-server-ip>

    First time you'll see "Are you sure you want to continue?" — type yes. Then enter the root password (Hetzner emailed it to you) or SSH key passphrase.

  4. 4

    Run the installer

    One command sets up everything — Docker, systemd, the bot:

    $ curl -fsSL https://your-saas-domain/install.sh | bash

    It'll ask for four things — have them ready:

  5. 5

    Open your Telegram bot

    You'll see a start message. Send /connect and follow the prompts to add Binance API keys (Spot Trading only, withdrawals must be disabled — the bot will refuse anything else).

    Then /strategies to see what's available, /configure <code> <json> to set params, /start_trading <code> to go live.

✓ done

Your bot is running on your server, auto-restarts if it crashes, comes back up after a reboot. You can close the SSH session — it keeps working.

To see logs later: journalctl -u trading-bot -f
To restart: systemctl restart trading-bot

// 05 — questions

Common questions

Which region should I choose? +
Doesn't matter much. Our strategies react to closed candles, not milliseconds. Pick a region close to where you are for lower SSH latency during setup — Frankfurt or Helsinki for European users, Ashburn or Hillsboro for US users.
Can I run multiple bots on one server? +
Technically yes — clone the repo into a second directory, use a different Telegram bot token, different systemd service name. Each needs its own license key. But for most people, one server per bot is simpler and only €4 more per month.
How do I keep my server secure? +

Basic hygiene, which our installer already handles or you should do:

  • Use SSH keys, not passwords (set up during VPS creation)
  • Enable a firewall — ufw allow ssh and nothing else needs to be open
  • Enable automatic security updates — apt install unattended-upgrades
  • The bot itself opens no ports; only outbound connections to Binance and our SaaS
What if the VPS provider goes down? +
Rare but possible. If your bot is silent for 3+ hours, we'll email you. Providers like Hetzner and DigitalOcean have >99.9% uptime, so realistically this is a few minutes per year. You can also set up snapshots ($1/mo on Hetzner) to restore quickly if needed.
How do I back up my bot? +
Everything important lives in ~/trading-bot/data/: the SQLite database with trade history, and .master_key which encrypts your Binance keys. Back up this folder to somewhere safe (encrypted USB, private cloud storage). Without .master_key, encrypted Binance keys can't be decrypted — so especially back it up.
Can I move the bot to a different server? +
Yes. Install the bot on the new server, stop the old one, copy the data/ folder over via scp, start the new one. Everything continues from where it left off — same license, same encrypted API keys, same trade history.
// ready?

Get your license key and go

→ open dashboard see pricing