trading-bot
system online · keys remain local

Trade on Binance
without ever giving
your keys away

A self-hosted trading bot you run on your own machine. Strategies update automatically from a subscription. Your API keys stay on your hardware — encrypted, never transmitted.

~/trading-bot $
$ docker compose up -d
[OK] postgres started
[OK] bot started · listening on telegram
[OK] license validated · plan: basic
[OK] 3 strategies synced from cloud
api keys: stored locally · encryption: aes-128 + hmac · network: localhost only
─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
// 01 — why this is different

Most trading bots ask for your API keys.
We can't.

Custodial bots run on the operator's servers. If they get hacked, your funds are gone. Our bot runs on your own machine — Docker container, encrypted local database.

01_KEYS

Never transmitted

Your Binance API keys are encrypted with a master key generated locally on first run. The master key never leaves your machine.

02_STRATEGIES

Auto-updated

We push strategy updates to your bot via signed bundles. HMAC verification means even DNS spoofing can't run rogue code.

03_CONTROL

Your hardware

Run it on a $5 VPS, a Raspberry Pi, or your laptop. Pause it. Modify it. Inspect every trade.

// 02 — install in 3 steps
full guide →
step 1

Subscribe

Choose a plan. Get a license key.

step 2

One-line install

$ curl -fsSL get.example.com/install.sh | bash
step 3

Connect Binance

Open your bot in Telegram. Paste API keys (read + trade only).

$ ./bot --start

Take control of
your trading infrastructure.

start now
// disclaimer: This is software for personal automated trading. We do not provide investment advice, manage client funds, or guarantee any returns. Cryptocurrency trading carries substantial risk of loss. You are solely responsible for your trading decisions. Past performance does not guarantee future results.