Install Brimoza on your own server
Brimoza is a self-hosted Binance SPOT trading bot — it runs entirely on a server you control. Your API keys never leave it. This takes about 5 minutes.
1. What you need
- A Linux server (Ubuntu 22.04+ or Debian recommended). Any small VPS works — 1 vCPU and 2 GB RAM is enough for several bots.
- Root or sudo access. The installer sets up Docker automatically if it isn't already installed.
- The default mode is dry_run (paper trading) — no Binance API key is required to try it.
2. One-line install
SSH into your server and run:
curl -fsSL https://brimoza.com/install.sh | bash
This downloads the latest cryptographically signed release, verifies its signature, generates a .env (with a random admin password and an at-rest encryption key), and starts the panel in dry_run on 127.0.0.1:8787.
.env file inside the install folder.3. Open the panel (it's private by default)
For safety, the panel binds only to 127.0.0.1 (it can start LIVE trading and is not meant to be public). Reach it from your own machine with an SSH tunnel:
ssh -L 8787:localhost:8787 user@your-server-ip
Then open http://localhost:8787 in your browser.
0.0.0.0.4. Log in
- User: admin
- Password: the one printed during install (or from the
.envfile).
5. Try it safely first (dry_run)
Dry_run simulates your strategy on live market prices without placing real orders. Create a bot, pick a strategy and budget, and watch it for a day or two. This is the right way to understand the behaviour before risking money.
6. Go live — only when you're ready
- In Settings, add your Binance API key. Give it Spot Trading permission only — never enable Withdrawals. An IP whitelist is strongly recommended.
- Open the LIVE confirmation gate (a deliberate second step so real orders can't fire by accident).
- Set a bot's mode to
liveand start it with the explicit LIVE confirmation.
7. Keep it updated
cd ~/brimoza/brimoza-<version>
bash scripts/update.sh
Updates are signed: the updater verifies the release signature and checksum before applying anything, so a tampered package is rejected. Your .env, data and settings are preserved.
Troubleshooting
- Can't reach the panel? It's loopback-only — use the SSH tunnel in step 3.
- "docker compose not found" — install Docker and the compose plugin, then re-run the installer.
- Forgot the password? Open the
.envfile in the install folder. - Still stuck? Email support@brimoza.com.