Jio, Airtel, ACT — every Indian ISP hands you a moving target. Every broker on your whitelist blocks the moment it moves. One dedicated IPv6 makes the address stop moving. Route only your order calls through it. Skip the VPS entirely.
The Problem
You didn't do anything wrong. This is how residential and mobile networks work in India — and how brokers verify who's allowed to call their API. The mismatch is the trap.
Jio, Airtel, ACT — most Indian ISPs hand out dynamic addresses. A router reboot, a link flap, an ISP-side lease renewal, and your public IP silently changes. Every broker whitelisted to the old one blocks you instantly.
Under CGNAT (all Indian ISPs), hundreds of subscribers share one public IPv4. If any of those strangers whitelisted the same address with the same broker first, your calls now hit their whitelist — or get flagged as a duplicate identity.
Broker webhooks and postback URLs need to reach you. Under CGNAT, inbound TCP to your public IP hits the ISP's shared NAT — and never gets to your machine. Order fills, exit signals, callback confirmations: silently dropped.
Started a session in the morning at IP 203.0.113.42. Router disconnected at 11am. Reconnected at 45.117.8.99. The broker still holds an open session tied to the old IP — and refuses your new calls until the token expires. Locked out of your own account.
4G/5G on Jio, Airtel, Vi — carriers rotate your public IP every few minutes as you move between towers. Your algo running off a mobile hotspot survives about one order cycle before the address changes. No whitelist can keep up.
Managing algos for yourself + family + partners across Dhan + Kite + Groww? To keep whitelist collisions from taking everyone down at once, you spin up a VPS per account. Costs stack: ₹500-800/mo per account, plus the ops time to babysit them.
Dead Ends
Still one IP per machine. VPS IPs rotate on restart, billing failure, or provider migration. Scaling to multiple accounts means multiple VPS — cost and ops multiply linearly.
Dhan Cloud, Kite Cloud give you their one shared IP. You can't run cross-broker bots from it. Your strategy lives on their servers — your competitive edge becomes readable.
Streak, AlgoBulls, and friends host your strategy logic. Platform risk is real — they can read it, change the rules, or shut down. Your custom indicators become theirs the moment you upload them.
Shared exit IPs get flagged when another user misbehaves. No dedicated address means broker callbacks are unreliable — the IP receiving the webhook today isn't guaranteed tomorrow.
The math
One broken fill during an expiry-day breakout pays for a year of this service. These are the failure modes we've watched real traders eat while they waited to "get around to fixing it."
Broker locks the whitelisted call path for 5–15 minutes after an IP change. Your algo retries. The retries all fail. The move you were trying to trade is gone.
Broker support responds during business hours. Your bot sits idle. Every strategy that depended on today's setup rebases against tomorrow's flat market open.
A VPS gives you two vCPUs and a rotating IP. You solve nothing — you've just moved the problem to a different machine and added a monthly bill on top.
The stranger sharing your ISP's shared IPv4 gets rate-limited by a broker for hammering the API. Now you're rate-limited too. There's no notification. There's no fix at your layer.
The Solution
One dedicated IPv6 address, yours alone. Route all your broker API calls through it via SOCKS5. Three lines of Python. That's the entire change.
What you actually get
Solving the IP problem alone doesn't finish the job — you still need one SDK across brokers and one place to route trades. ServLoci ships all three together.
One address, yours alone, that never rotates. Whitelist once with every broker. All your API calls exit through it — regardless of which machine, which city, which network you're on.
One Python (and JS) SDK that speaks Dhan, Kite, Groww and Fyers. Same method names. Same order shape. Same tick-stream interface. Add a new broker by changing one string — not rewriting a service.
tradeclient.place_order(broker="kite", ...)One dashboard for all your accounts. Route a signal to family, partners, or a pooled account with a rule — not a copy-paste. See fills, exposure, and P&L across every broker and every login in one panel.
Beta access opens for paying subscribers first. Sign up now — you're grandfathered into every future release without a price bump.
Under the hood
A static exit IP is a solved, boring networking problem. We've built the plumbing so you don't have to think about it.
A /128 is the smallest IPv6 allocation — a single address. Assigned to you alone. Not a range shared with other users, not a pool that rotates. One address. Yours.
Every connection requires your username and password. Those credentials map to exactly one IPv6 exit. No auth = no connection. There's no anonymous routing, no shared session.
SOCKS5 is a transport-layer protocol. Your broker calls are HTTPS — TLS-encrypted between your machine and the broker's servers. The proxy routes encrypted bytes. We cannot read your order payloads.
The IPv6 is configured on the server's network interface — not a floating IP, not a NAT rule. It doesn't change when software restarts, when we deploy updates, or when you reconnect.
Python's requests library supports SOCKS5 via PySocks. Monkey-patching the session before your broker import means the SDK never knows it's proxied. No broker SDK modification.
We give you a stable exit IP. Your trading strategy, your broker accounts, your execution logic — those stay yours. We don't see your trades. We just make sure every API call leaves from the same address your broker has on file.
Setup
Google sign-in. Share your broker name and client ID. We assign a dedicated IPv6 and SOCKS5 credentials.
~2 minutesThree lines before your broker SDK import. No VPS config, no nginx, no iptables. The SDK never knows it's proxied.
3 lines of PythonAdd your IPv6 to each broker's whitelist settings. Done. Forever. Move machines as often as you like — the exit IP never changes.
permanent · dedicatedAdvisory
Buy one address, run it lean. Six habits the sharpest ServLoci users hold — each one keeps your monthly bill flat while the strategy behind it gets fatter.
The same IPv6 whitelists cleanly on Dhan, Kite, Groww, Fyers — and any REST-based broker after that. Don't buy a second address until you actually have a second identity. Verifying a new broker under the same account reuses the same IPv6 automatically.
10 GB / month is included. If a busy month sneaks past that, overage bills at ₹5 per extra GB — no upsell, no plan switch. Most order-only workloads run under 2 GB. If you're at 30, you're probably routing traffic that doesn't need to be routed.
Only create, modify, cancel need to leave from your whitelisted IP. Ticks, LTP snapshots, holdings, positions, historical bars — those can go straight from your box. Same account, same broker; nothing breaks. Data usage on our side drops by an order of magnitude.
A ₹800/mo VPS gives you 2 vCPUs and a rotating IP. Your desk already has a faster machine that isn't rotating anywhere. Run the strategy there — the proxy is what makes the exit address stable, not the VPS. Ops shrinks to "did I close the laptop lid?"
Backtests, feature engineering, model inference, indicator computation — none of it hits the network. Only the final order dispatch touches ServLoci. Your compute stays with you, your data stays with you, your competitive edge stays with you.
An agent watching signals, computing sizing, punching the trade — it all lives on your box. The single line of egress config is what makes it deployable. Order came from anywhere in the world? Broker sees the same IPv6. The agent doesn't care where it runs; you don't care what changed.
When to add a second IP
One address per trading identity, not per broker. A family account, a partner book, a bot that needs its own whitelist — that's when you provision a second IP. Everything else stays on the one you already pay for.
Integration
Monkey-patch requests.Session before importing your broker library. Works with every Indian broker SDK we support: Dhan, Kite, Groww, Fyers.
Pricing
Cloud-hosted for one bot — or self-hosted on your metal with a fully managed opaque install. No setup fee. Cancel anytime.
₹100 refundable within 24h if you don't use your API key. Cancel anytime.
Approximate list price. Opaque appliance-style install — not open-source DIY. Contact us to size the host.
Need fully own control of code, routing, and address space? You're free to develop one yourself — no ServLoci required. Our self-hosted option is different: the binary runs on your host, but the install stays opaque and fully managed by us.
FAQ
Start today
Sign in with Google → paste your broker + client id → we assign a dedicated IPv6 with 1 GB / 10 RPS / 7 days on the house. No card. Upgrade later — the same IP survives.
Claim my free IPv6 · 1 GB · 7 days · no card Read the docs firstor submit your broker details directly