Kotak Neo Static IP: Fix Your Trading API After the SEBI Deadline

Important Update: Other QG Customers w/ Shared IPs Could Reject Yours (April 3, 2026)

Since the SEBI deadline hit on April 1, we've seen a surge of Indian algo traders signing up for QuotaGuard. That's great, but it's created an unexpected side effect. Because brokers require each IP to be uniquely tied to one trader, a shared static IP can be rejected if another QuotaGuard customer has already registered it with the same broker. The more customers we onboard, the more likely this becomes.

Our recommendation: For the most reliable setup, use our Shield Enterprise plan, which gives you a dedicated proxy with IPs that are exclusively yours. Lower-tier plans (Starter, Production, Business) can still work, and many customers are connecting successfully, but if your assigned IP has already been claimed by another QuotaGuard customer at your broker, you'll need a fresh one.

How the Enterprise setup works:

1. Sign up for the Shield Enterprise plan.
2. Reach out to our team.
3. We'll build your dedicated proxy infrastructure.
4. We'll work with you to rotate through IPs until we find ones that haven't been previously registered with your broker. QuotaGuard has been operating for 13 years with over 100,000 customers, so some IPs in our pool may have been registered by past users. We keep rotating until we find clean ones.
5. Once we find two working IPs, they're yours exclusively. No one else will ever be assigned them.

Have questions or want help choosing the right plan? Contact us and we'll get you sorted.

Route your cloud app's traffic through QuotaGuard Shield to get a static IP, register it with Kotak Neo, and your trading API connects again. SSL passthrough keeps your credentials and order data encrypted end-to-end.

SEBI's static IP mandate took effect April 1, 2026. Kotak Neo's trading API now rejects connections from any IP that isn't pre-registered. If you're running on Heroku, Render, Railway, or any platform with dynamic outbound IPs, your bot stopped working. Here's how to fix it.

Verified: QuotaGuard Shield Connects to Kotak Neo's Infrastructure

We tested connectivity on April 2, 2026 through QuotaGuard Shield's proxy. The developer portal at napi.kotaksecurities.com returned HTTP 200. The trading API at mnapi.kotaksecurities.com timed out.

That timeout is expected. It's not a compatibility problem. Kotak Neo's trading API is firewalled by design. It only accepts connections from pre-registered IPs. Once you register your QuotaGuard Shield static IP, connections go through.

QuotaGuard tip: Don't panic if you see a timeout when testing before registration. The firewall is server-side. The fix is completing the registration step on Kotak Neo's end. Once they've added your IP, it works immediately.

Why Kotak Neo Now Requires a Static IP

SEBI issued circular SEBI/HO/MIRSD/MIRSD-PoD/P/CIR/2025/0000013 on February 4, 2025. The original deadline was extended by circular SEBI/HO/MIRSD/MIRSD-PoD/P/CIR/2025/132. Final enforcement: April 1, 2026. That date has passed.

SEBI's exact language:

"not permit open APIs and allow access only through a unique vendor client specific API key and static IP whitelisted by the broker to ensure identification and traceability of the algo provider and the end user"

SEBI Circular SEBI/HO/MIRSD/MIRSD-PoD/P/CIR/2025/0000013, February 4, 2025

NSE operationalized this via circular NSE/INVG/67858. Kotak Neo built enforcement directly into their API infrastructure. The trading API firewall isn't a bug. It's the compliance mechanism.

Kotak Neo published their own static IP documentation at kotakneo.com/platform/kotak-neo-trade-api/static-ip-details/. That page covers the registration process on their end. This post solves the other half: how to get a static IP when you're running on a cloud platform that assigns dynamic outbound IPs.

Get a Static IP With QuotaGuard Shield (Step by Step)

QuotaGuard Shield is an egress proxy that runs on AWS. Your API calls route through it and exit from a static IP address that never changes. You register that IP with Kotak Neo. Your bot connects again.

QuotaGuard Shield uses SSL passthrough. It routes your encrypted traffic without decrypting it. Your Kotak Neo credentials and order data are never exposed to the proxy. This is the right product when financial data flows through the connection.

On the Enterprise plan, each account gets a dedicated IP that is exclusively yours. SEBI's requirement is traceability: the IP must map to you specifically. Lower-tier plans assign static IPs, but those IPs may be shared across customers. As we've discovered, Indian brokers are rejecting IPs that were previously registered by another user. See the important update at the top of this post.

On Any Platform (Direct Signup)

Sign up at quotaguard.com/products/pricing. Copy your proxy URL and static IP from the dashboard. Set it as an environment variable in your platform's settings:

QUOTAGUARDSHIELD_URL=http://username:password@proxy.quotaguard.com:9293

On Heroku

Install the add-on:

heroku addons:create quotaguardshield:starter --app your-app-name

This sets QUOTAGUARDSHIELD_URL automatically. Your static IP is visible in the add-on dashboard. Use that IP when registering with Kotak Neo.

Python Code: neo_api_client

import os
from neo_api_client import NeoAPI

# On Heroku: QUOTAGUARDSHIELD_URL is set automatically by the add-on.
# On other platforms: set it in your environment variables.
proxy_url = os.environ['QUOTAGUARDSHIELD_URL']
os.environ['HTTPS_PROXY'] = proxy_url
os.environ['HTTP_PROXY'] = proxy_url

client = NeoAPI(
    consumer_key="your_consumer_key",
    consumer_secret="your_consumer_secret",
    environment='prod',
)

Setting HTTPS_PROXY and HTTP_PROXY before initializing NeoAPI routes all outbound requests through the proxy. The neo_api_client library uses the standard requests session underneath. It picks up proxy settings from environment variables automatically.

Register Your IP With Kotak Neo

1. Get your static IP from the QuotaGuard dashboard.
2. Go to Kotak Neo's static IP registration page.
3. Follow their process to submit your static IP for whitelisting.
4. Wait for confirmation. Kotak Neo's docs indicate this is a manual review step.
5. Test your connection once confirmed.

The VPS Alternative Costs More Time Than Money

You can spin up a DigitalOcean Droplet or an AWS EC2 instance with a reserved Elastic IP. That also gives you a stable static IP. It runs roughly $6 to $12 per month. It's a legitimate option. Many developers in the algo trading community use it.

Are you a trader or are you trying to run 24/7 devops as your primary goal with a little trading on the side? That's the question.

The real cost is time and maintenance. You own the server. You handle OS updates, security patches, SSH key rotation, and uptime monitoring. You need a deployment workflow to push code changes to it. If you're already on a cloud platform, you're giving up the deployment tooling you've built. If the server goes down during market hours, your bot goes dark.

If you want to minimize monthly spend and you're comfortable with DevOps, the VPS route works. If you want to be back online today without learning server administration, the proxy route is faster. QuotaGuard Shield's Production plan is $49/month. That's the math.

Latency Won't Affect Your Strategy

QuotaGuard Shield adds roughly 10 to 50ms per request for the proxy hop. That sounds like it matters. It doesn't. Not for the strategies hitting this static IP wall.

High-frequency trading firms don't run on Heroku. They use NSE co-location facilities and custom network infrastructure. If you're deploying to a PaaS cloud platform, you're running a daily, hourly, or minute-level strategy. Intraday systematic. Swing trading. Options strategies. For those, 20 to 50ms is noise.

SEBI's static IP requirement is about authentication and identity verification. The broker's system confirms you're a registered, authorized trader before allowing order placement. That check doesn't need to be fast. It needs to succeed.

If you want to minimize latency on execution calls specifically, you can whitelist your static IP and then connect to the trading API directly for order submission. Route authentication calls through the proxy. Both architectures work. With Shield's SSL passthrough, routing everything through adds no security exposure. For most traders, routing everything through the proxy is simpler and the latency difference is irrelevant.

Get Your Bot Back Online

The enforcement deadline passed on April 1, 2026. If your Kotak Neo API bot stopped working, this is why. The trading API firewall is working exactly as Kotak Neo and SEBI intended.

Sign up at quotaguard.com/products/pricing. Set QUOTAGUARDSHIELD_URL in your environment. Register your static IP with Kotak Neo using their static IP registration process.

The same static IP covers all your broker connections. If you're also running through Zerodha, Upstox, or Dhan, one QuotaGuard Shield subscription handles all of them from the same IP.