Skip to content Reverse proxy with authentication
Allows users to backtest strategies without risking real capital. zenbot private link
By establishing a continuous WireGuard tunnel between your local machine and your cloud infrastructure, your bot can securely stream MongoDB data or receive remote commands without public exposure. Method 3: Tailscale or ZeroTier Overlay Networks Reverse proxy with authentication Allows users to backtest
+-----------------------------------------------------------------------+ | Your Secured Local Device | | | | +--------------------+ Local Stream +----------------------+ | | | Zenbot Core Engine| ------------------> | MongoDB Database | | | +--------------------+ +----------------------+ | | | | | | Encrypted API Handshake | | v | | +--------------------+ | | | Exchange API Keys | (Never leaves local machine storage) | | +--------------------+ | +-----------------------------------------------------------------------+ | | Outbound Private Link Protocol v +-----------------------------------------------------------------------+ | Private Webhook Hub | --> Dispatches alerts to Discord/Slack | +-----------------------------------------------------------------------+ 2. Setting Up an Isolated, Secure Zenbot Environment Setting Up an Isolated, Secure Zenbot Environment Keeping
Keeping exchange requests within an isolated, trusted network environment. Whitelisted Static IPs & VPNs Step-by-Step: Setting Up a Secure, Private Link Environment
If your MongoDB database is compromised, your bot can be fed fake market data to trigger bad trades. Ensure MongoDB is configured to require strong user authentication and is set to bind only to internal, private network interfaces ( 127.0.0.1 or your VPC internal IP). Keep Dependencies Updated