Office Network vs Static IP for Algo Trading
Why an office network IP fails Indian broker API whitelists — CGNAT, daily rotation, shared NAT — and how a dedicated static IP lets the same bot run from office, home or VPS.
What Google means by “office network” in this context
Traders search office network when their algo runs on a laptop or mini-PC inside a company LAN. The public IP the broker sees is the office router’s address — not a dedicated host. That address is a poor whitelist target.
Why an office network IP breaks broker APIs
- CGNAT / shared public IP — many staff share one egress; a colleague’s traffic can look like yours
- Daily or weekly DHCP / ISP lease changes — same problem as a home daily IP
- IT may add a new fibre, SD-WAN or backup link overnight and change egress
- Brokers often allow only one IP change per calendar week
- You cannot take the same whitelist home or onto a VPS if it is bound to the office WAN
Static IP vs office network — the working pattern
Keep the bot on the office network if you want. Route only broker API traffic through a dedicated Mumbai static IP (HTTP proxy on port 443). The office LAN is for keyboards and screens; the whitelist is a single-tenant datacenter address that does not change when IT swaps the router.
How to set it up from an office PC
Create an Algo-IP account, finish KYC, allocate IPv4 (₹200/month) unless your broker accepts IPv6. Paste that address into Zerodha, Dhan, Angel One or Fyers. On the office machine set the HTTP proxy to the dashboard host and port 443. Confirm api.ipify.org shows the Algo-IP address, not the office WAN.
When an office static line is still not enough
Some offices buy an ISP static IP. That can work until power, fibre or a site move. A datacenter static IP stays up if the office is closed, and the same credentials work from a home backup PC. For SEBI-style traceability, one dedicated address per trading identity is cleaner than a shared office WAN.