How to Deploy a Trading Bot on a Cloud Server

Ensuring Uninterrupted Bot Operation

After launching your bot on a cloud server, three hours later it crashed — Killed in the logs. Cause: out of memory. The trading bot loaded market data into RAM, and the OOM killer terminated the process. Without auto-restart, it stayed dead until morning. This happens often: users focus on the trading logic but neglect the infrastructure.

We’ve been setting up bots for 5 years. Along the way we’ve hit WebSocket disconnects, key leaks, and wrong server choices. We’ve developed a simple pattern: a VPS with headroom, systemd for process management, Telegram alerts, and no Docker unless necessary.

Choosing a VPS for Your Trading Bot

The key is a server with 2 vCPU and 4 GB RAM. For scalping, the server must be near the exchange. For Binance, AWS Tokyo (latency ~10 ms) or Vultr Singapore (15 ms) work well. Latency between Europe and Asia exceeds 200 ms — deadly for HFT. We recommend Hetzner for algorithmic trading: it’s 2–3× cheaper than AWS, with 20–30 ms higher latency, which is acceptable for minute‑candle strategies. Hetzner VPS starts at €3.99/month for a 2 vCPU, 4 GB RAM instance. For Binance, DigitalOcean (NYC region) gives ~40 ms to exchange servers. Costs: Hetzner €3.99/mo, DigitalOcean $6/mo, AWS ~$10/mo. Savings can be up to 60% by choosing Hetzner over AWS.

Systemd vs Docker for Bot Management

For a single bot, Docker adds 5–10% CPU/RAM overhead and complicates debugging. systemd is a built‑in Linux init system — reliable and minimal. Here’s the unit file we use:

[Unit]
Description=Trading Bot
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=bot
WorkingDirectory=/home/bot/trading-bot
EnvironmentFile=/home/bot/trading-bot/.env
ExecStart=/home/bot/.venv/bin/python main.py
Restart=on-failure
RestartSec=10
StandardOutput=journal
StandardError=journal
MemoryMax=512M
CPUQuota=80%

[Install]
WantedBy=multi-user.target

systemd documentation states that MemoryMax limits memory via cgroup v2, preventing OOM kill. Restart=on-failure ensures restart only after an abnormal exit, leaving intentional stops untouched.

After creating the file:

systemctl daemon-reload
systemctl enable trading-bot
systemctl start trading-bot
journalctl -u trading-bot -f

Secure API Key Storage

Never put keys in code — that’s the most common cause of leaks. Use environment variables. Example .env file with permissions 600:

# /home/bot/trading-bot/.env
BINANCE_API_KEY=xxx
BINANCE_SECRET=yyy
TELEGRAM_BOT_TOKEN=zzz
TELEGRAM_CHAT_ID=123456
chmod 600 /home/bot/trading-bot/.env
chown bot:bot /home/bot/trading-bot/.env

For extra security, you can store keys in AWS Secrets Manager or 1Password CLI, but for a single bot .env with firewall and minimal permissions is enough.

How to Monitor Your Bot with Telegram Alerts

The minimum set is Telegram alerts and heartbeat. Asynchronous code sends a message on start, on errors, and once per hour (heartbeat). If the message stops coming — the bot is down. Python example with httpx:

import httpx, asyncio
TELEGRAM_URL = f"https://api.telegram.org/bot{TELEGRAM_TOKEN}/sendMessage"
async def send_alert(message: str, level: str = "INFO"):
    prefix = {"INFO": "ℹ️", "WARN": "⚠️", "ERROR": "🚨"}.get(level, "")
    await httpx.AsyncClient().post(TELEGRAM_URL, json={
        "chat_id": TELEGRAM_CHAT_ID,
        "text": f"{prefix} *{level}*\n{message}",
        "parse_mode": "Markdown"
    })
# On start
await send_alert("Bot started", "INFO")
# Heartbeat every hour
async def heartbeat():
    while True:
        await asyncio.sleep(3600)
        await send_alert(f"Heartbeat: balance={await get_balance()}", "INFO")

Additionally, we use UptimeRobot for external checks: it pings the IP and sends SMS if no response. Using asynchronous I/O with uvloop reduces overhead and improves WebSocket reconnection handling.

Updating the Bot Without Downtime

Deploy a new version:

cd /home/bot/trading-bot
git pull origin main
/home/bot/.venv/bin/pip install -r requirements.txt
systemctl restart trading-bot

Systemd waits for the current iteration to finish before starting the new process. For critical updates, use systemctl restart --check — but with Restart=on-failure the new process starts without data loss.

10-Step Bot Deployment

1. Choose a VPS: 2 vCPU, 4 GB RAM, region close to exchange.
2. Install Ubuntu 22.04 LTS, update packages.
3. Create user bot without sudo.
4. Clone the bot repository.
5. Install Python 3.11 and dependencies in a virtual environment.
6. Create .env with API keys and Telegram token.
7. Place the systemd unit file and enable the service.
8. Set up Telegram alerts: start, errors, heartbeat every hour.
9. Check the log: journalctl -u trading-bot -f.
10. Configure external monitoring (UptimeRobot).

After these steps, the bot runs 24/7 with automatic restart. If something goes wrong, Telegram will notify you.

What's Included in the Setup

• Documentation of server configuration and environment variables
• SSH access with secured key pairs
• Telegram alerts configured with heartbeat and error notifications
• 7-day post-deployment support for any issues
• Detailed runbook for maintenance and updates

Common Self-Setup Pitfalls

If you’re unsure about your infrastructure, order a turnkey setup from us. We’ll prepare the server, deploy the bot, and configure monitoring in 2–4 days. Our turnkey deployment includes server setup, bot configuration, monitoring, and documentation—delivered in 2–4 days. Contact us for a free consultation to assess your project.

Blockchain Infrastructure Deployment: Nodes, RPC, Indexing

Subgraph fell at 3:47 AM. By morning users saw outdated balances, transactions "hung" in the UI, support received 47 tickets in an hour. Cause: the handler in the subgraph failed on a transaction with a non-standard event log — and the entire index stopped. We have encountered such situations dozens of times. Our experience shows: blockchain infrastructure does not forgive gaps in observability. Guaranteeing uptime without multi-layered monitoring and fault-tolerant architecture is impossible. Over 8 years working with Ethereum, Polygon, and Solana, we have developed an approach that allows predictable deployment of infrastructure of any scale — from a single node to a multichain grid with dozens of subgraphs.

RPC Layer Architecture

Every dApp interaction with the blockchain goes through RPC — the JSON-RPC API provided by a node. Three options:

Managed providers — Alchemy, QuickNode, Infura, Ankr. Minimal operational costs, SLA, built-in monitoring. Limits: rate limits (Alchemy Free: 300 RU/sec), vendor lock, potential downtime during provider incidents. For most projects — the right choice at the start.

Self-owned nodes — full control, no rate limits, no third-party dependence. Cost: archive Ethereum node requires 2.5–3TB SSD, a strong server, and DevOps support. Sync from scratch on Ethereum via Geth/Nethermind — 3–7 days. Justified under high load or latency requirements.

Hybrid — self-owned node as primary, managed provider as fallback. Standard for protocols with high TVL. Proper load balancing can reduce costs by 20–30% compared to pure managed setup. Under high monthly request volume, hybrid saves significantly.

How to Set Up an RPC Layer Without a Single Point of Failure?

At least two providers, DNS round-robin with health check every 5 seconds, automatic fallback when latency >500 ms. In practice, this gives 99.99% availability during any provider failure. For protocols with high TVL, we recommend a custom HA-proxy (nginx or Envoy) in front of two managed providers.

Why Is a Hybrid RPC Scheme More Cost-Effective Than Pure Managed?

At high request volumes, managed providers can be very expensive; a hybrid using a self-owned node as primary and a managed fallback cuts costs significantly without losing SLA.

Ethereum Node Clients

Execution clients: Geth (most used), Nethermind (C#, fast sync), Besu (Java, enterprise), Erigon (fastest sync, efficient archive mode ~2TB instead of 3TB).

Consensus clients (post-Merge): Lighthouse (Rust), Prysm (Go), Teku (Java), Nimbus (Nim). Each node after The Merge requires a pair of execution + consensus clients.

For DevOps: eth-docker — Docker Compose configurations for all client combinations. Setting up monitoring via Grafana + Prometheus is mandatory; a standard dashboard is available in each client's repository.

The Graph: Event Indexing

The Graph Protocol — decentralized indexing. A subgraph describes which events from which contracts to index and how to transform them into a GraphQL schema.

Subgraph structure:

• subgraph.yaml — manifest: contract addresses, startBlock, events to handle
• schema.graphql — GraphQL schema of entities
• src/mapping.ts — AssemblyScript event handlers

dataSources:
  - kind: ethereum
    name: UniswapV3Pool
    network: mainnet
    source:
      address: "0x88e6A0c2dDD26FEEb64F039a2c41296FcB3f5640"
      abi: UniswapV3Pool
      startBlock: 12370624
    mapping:
      eventHandlers:
        - event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
          handler: handleSwap

AssemblyScript handlers — not TypeScript. No nullable types, no closures, no many standard APIs. An error in the handler stops the subgraph indexing on that transaction. Important: add try-catch for operations that can fail (e.g., store.get() for an entity that may not exist).

How to Avoid Subgraph Indexing Stops?

Graph Node logs are monitored in real-time; on hasIndexingErrors = true an alert fires and an automatic node restart (via systemd or Kubernetes). Typical downtime on error — 150–300 seconds to recover. Additionally, for production we set up a watchdog that restarts Graph Node if subgraph lag exceeds 50 blocks.

Choosing Between Hosted Service and Decentralized Network

Graph Hosted Service (free, centralized) is deprecated in favor of Subgraph Studio + Graph Network. For production: deploy on Graph Network with GRT curation signal — the subgraph gets indexers proportional to curation.

Alternatives to The Graph: Ponder (TypeScript, self-hosted, easier to debug), Envio (ultra-fast indexer, supports EVM + non-EVM), Subsquid (TypeScript, own network), Moralis Streams (managed, webhook-based). Our experience shows: for high-load projects with unique logic, Ponder or Envio are more effective — they give full control over the process and do not require GRT tokenomics.

Webhooks and Real-Time Notifications

Alchemy Webhooks and QuickNode Streams allow receiving events in real-time via HTTP webhook or WebSocket. For monitoring addresses, new transactions, mints — this is faster than polling RPC.

Tenderly — platform for monitoring and alerts. You can set up an alert for a specific contract event, balance change, function call with certain parameters. Transaction simulation via Tenderly API is invaluable for debugging.

Monitoring and Observability

Minimum monitoring stack for a protocol:

On-chain: OpenZeppelin Defender Sentinel — watches contract events, triggers webhook or Autotask when conditions are met. Forta Network — community-maintained bots detect anomalies (large withdrawals, flash loans, governance attacks).

Infrastructure: Grafana + Prometheus for nodes, Datadog or Grafana Cloud for managed metrics. Alerts on: node is 10+ blocks behind, RPC latency >500ms, subgraph lag >100 blocks.

Uptime: Better Uptime or PagerDuty on RPC endpoint and subgraph health endpoint (The Graph provides _meta { hasIndexingErrors, block { number } }).

Why Is Monitoring Without Tenderly Insufficient?

Tenderly provides transaction simulation and detailed traces — critical for debugging subgraph and smart contract errors. Forta focuses on network anomalies, not your infrastructure. The combination of Tenderly plus a custom Grafana dashboard covers 90% of incident scenarios.

Multichain Infrastructure

A protocol on 5 chains = 5 separate RPC endpoints, 5 subgraphs, 5 monitoring configs. Manageable but requires deployment automation.

For subgraph multi-network deployment: graph deploy --network mainnet, graph deploy --network arbitrum-one etc. with a unified codebase and network-specific addresses in separate config files.

Chainlink CCIP and LayerZero for cross-chain messaging require monitoring of both chains and transactions on intermediate relayers. A reorg on the source chain after a confirmed mint on the target chain is a classic bridge problem. Solution: wait for finality (on Ethereum ~15 minutes after Merge for economic finality) before confirming on the target chain.

Infrastructure Setup Process

1. Audit current stack — determine chains, request volume, latency and availability requirements.
2. Architecture design — select providers, load balancing, redundancy.
3. Subgraph development — manifest → schema → handlers → testing on local Graph Node → deploy to testnet → mainnet.
4. Monitoring configuration — Tenderly alerts, Grafana dashboard, PagerDuty integration.
5. Documentation and runbook — what to do when: subgraph falls behind, RPC downtime, node desync.
6. Handover to operations — team training, access transfer, first month support.

What's Included

• Deployment of managed or self-hosted Ethereum, Polygon, BNB Chain nodes
• RPC layer setup with primary/fallback and load balancing
• Subgraph development and deployment for your protocol
• Monitoring connection (Tenderly, Grafana, alerts)
• Runbook and operations documentation
• Team training (up to 4 hours online)
• 30-day support after delivery

Timeline

All projects are managed in a GitHub/GitLab repository with CI/CD; configuration code stays with you. Order infrastructure deployment — we'll show how to cut costs by 20–30% without losing reliability. Get a consultation — we'll demonstrate how we deployed infrastructure for a protocol with large TVL on Ethereum and Arbitrum. Contact us.