← wickwatch home

cTrader · Docker

Run cTrader cBots in Docker, with a dashboard

The cTrader CLI runs a cBot without the desktop app, so a bot fits into a container on a Linux server. wickwatch adds what the command line leaves open: one place to see every bot with its account and its log, and to start, stop and reconfigure it.

What wickwatch does with your bots

• Runs every instance as its own container, started through the cTrader CLI, and shows its status, uptime, broker connection and last log line.
• Creates a bot from an uploaded algo with a form built from the algo's parameters, or from an existing .cbotset file.
• Keeps every saved configuration as a version you can restore, and parameter templates that apply a named set of values to any instance of the algo.
• Follows positions, pending orders and deals per bot and per account, with realised P&L, win rate, profit factor and risk per trade.
• Starts bots again after a host or Docker restart if they were meant to run.
• Stops everything on an account with one emergency stop: bots stopped, orders cancelled, positions closed. Always with confirmation, always in the audit log.

Two ways to define a bot

Both can be mixed on one server.

• Set it up in wickwatch: upload the algo and create an instance. wickwatch creates, replaces and removes its container from the saved configuration.
• Define it yourself: wickwatch shows and controls every container from your own compose file that carries the label wickwatch.instance. It never replaces or removes such containers.

What you need

• A Linux server with Docker and Compose. 2 vCPU and 4 GB RAM are enough for the dashboard and a few bots.
• The cTrader CLI image, which you pull from Spotware yourself, and a cTrader ID with your accounts.
• Your compiled cBots as algo files.
• A reverse proxy with HTTPS in front of the dashboard, and a VPN or an IP allowlist: wickwatch can close positions and should stay out of public reach.

Try it first, without a broker

The image starts with a demo adapter: fake accounts, instances, positions and logs.

docker run --rm -p 3000:3000 \
  -e MASTER_KEY="$(openssl rand -base64 32)" \
  -v wickwatch-data:/app/data \
  ghcr.io/wickwatch/wickwatch:0.7.1

For real bots, follow the step-by-step install guide; the compose files for nginx-proxy, Traefik or a port of its own are in the deployment examples. Docker is reached only through a docker-socket-proxy that allows the few API calls wickwatch needs.

cTrader is a trademark of its respective owner; wickwatch is not affiliated with or endorsed by Spotware and includes no cTrader software. The cTrader CLI is subject to Spotware's licence terms.