TradeArmor, Self-Hosted Automated Crypto Trading

A Docker host with two containers, a VPN container holding the network namespace and a bot container sharing it via network_mode service vpn, with a socat gateway bridging a host port into the VPN network and the bot reaching the host over the LAN IP

How to Run a Crypto Trading Bot Behind a VPN (Docker)

How to run a crypto trading bot behind a VPN with Docker: when it makes sense, the container networking that actually works, and the gotchas to expect.

A home server running a self-hosted crypto trading bot with three paths reaching it from outside the house: a Cloudflare Tunnel with an identity check, a WireGuard VPN back to the home network, and a phone on the local network only, illustrating three ways to remotely access a trading bot dashboard without a cloud account

Crypto Trading Bot Remote Access: Cloudflare Tunnel or VPN

Crypto trading bot remote access without a cloud account: Cloudflare Tunnel, a home VPN, or the local network, and what each one actually protects.

A single signal splitting from a proxy server into three paths reaching three trading bot instances, one on the same network over HTTP and two remote over WebSocket on different exchanges, with green, red, and purple delivery status dots showing which instances received the signal

Multi-Instance Crypto Trading Bot: How One Signal Reaches Every Bot You Run

How a multi-instance crypto trading bot fans one signal out to every bot you run, across exchanges and machines, with per-instance delivery tracking.

A proxy admin dashboard showing three registered crypto trading bot instances on separate physical machines, a home Linux box, a small cloud VPS, and a Docker host behind a VPN tunnel, each with its own connection status and exchange

Scaling a Crypto Trading Bot Beyond One Machine

When scaling a crypto trading bot beyond one machine actually makes sense, what Multi-Machine Management does, and the real one-box-vs-many trade-off.

A signal-to-order pipeline diagram showing a cava-signal firing, routing through a local WebSocket connection with no external hop, and landing as a filled order with the elapsed path logged

Crypto Trading Bot Signal Latency: Why the Gap Between Signal and Order Matters

Crypto trading bot signal latency is the gap between a signal firing and an order landing. Here's where that gap comes from and how to close it.

A three-stage diagram showing a trading bot process crashing, an operating system restart policy bringing it back online within seconds, and an alert firing to the operator, illustrating what actually keeps a self-hosted crypto trading bot running

Crypto Trading Bot Uptime and Reliability: What Actually Keeps It Running

Crypto trading bot uptime isn't about never crashing. It's about what happens in the seconds after it does. Here's what actually keeps one running.

Crypto Trading Bot Mobile App: Running TradeArmor as a PWA on Your Phone

TradeArmor's crypto trading bot mobile app is a PWA, not an app-store download. Install it, get real push notifications, and your keys never touch a server.