Zerodha Algo Trading VPS

Yes: since 1 April 2026, Zerodha requires a whitelisted static IP for all API-based order placement, under NSE and SEBI algorithmic trading rules. Market data over WebSocket and read-only APIs such as the order book and positions can still be called from any IP.

• How many: one primary IP is mandatory and an optional secondary can be added, two in total.
• Changes: exchange rules allow only one modification per calendar week, so check the address before saving.
• Family use: the same IP can serve your spouse, dependent children and dependent parents through one developer account with separate apps.

A home broadband connection usually changes IP, which is why a VPS with a fixed address is the common choice. The wider rule set is explained in SEBI's static IP rule for algo trading.

Install the same runtime the bot uses on your PC, copy the code without exposing secrets, run it once by hand, then make it a service that starts on boot and restarts on failure. Kite Connect access tokens expire daily, so the bot also needs a fresh login each trading morning before 9:15 AM.

1. Connect over SSH (see what SSH is) and create a non-root user for the bot.
2. Install Python and a virtual environment, then pip install kiteconnect and your other packages.
3. Store the API key and secret in a file readable only by that user (chmod 600), never in a public Git repository.
4. Run the bot in the foreground once outside market hours and read its log.

A minimal systemd unit keeps it running across reboots (save as /etc/systemd/system/kitebot.service):

[Unit]
Description=Kite Connect trading bot
After=network-online.target

[Service]
User=trader
WorkingDirectory=/home/trader/bot
ExecStart=/home/trader/bot/venv/bin/python bot.py
Restart=on-failure

[Install]
WantedBy=multi-user.target

sudo systemctl daemon-reload
sudo systemctl enable --now kitebot
journalctl -u kitebot -f

Windows-only tools such as charting bridges need a Windows server instead; what a Windows VPS is for covers that case.

A VPS removes home broadband outages and power cuts, but it cannot beat the broker's order queue, and no host can promise a fixed millisecond figure for your strategy. Reliability, not speed, is the main reason to move a bot off a home PC.

Many API servers block ping, so measure the HTTPS connection time from the server during market hours instead:

for i in $(seq 1 20); do curl -o /dev/null -s -w '%{time_connect}\n' https://api.kite.trade; done

Take the median of the twenty results, then run the same loop from your home line to compare.