Static IP · your VPS · managed compute

One stable route
for your broker API.

Use a ServLoci static IP, connect your own VPS, or let us run the machine. Your strategy and broker credentials remain yours.

Get your static IPv6Choose the broker account that will use this IP.
About 1 minute · no card

Use the numeric client ID shown in DhanHQ · No card. Broker secrets stay in your runtime.

7 days free · no cardPlans from ₹199 + GSTNo signals or strategies
Free 1 GB for 7 days · no card, no VPS
SOCKS5 carries broker HTTPS without terminating broker TLS
Non-custodial · broker secrets are not persisted
10 RPS free-tier ceiling · add your own pre-trade risk gates
Setup guides forDhanKiteGrowwFYERSUpstoxICICI DirectKotak Neo

Choose by what you already have

Four clear ways to start.

KYCChecking status…KYC for managed services →
I already have compute

Static IP

Keep running on your laptop, notebook or cloud. Route supported broker calls through one dedicated IPv6.

₹299/month + GST
Start 7-day free trial →No managed-service KYC to claim the trial.
I have a VPS or cloud VM

ServLoci Router

We install routing, IP discovery, broker environments and health monitoring on your machine.

₹199/month + GST
Connect my VPS →KYC required before activation.
I need a small managed VPS

Route VPS

A small always-on machine for a stable IP, broker routing and one lightweight process.

₹599/month + GST
Request Route VPS →KYC required before provisioning.
I need more compute

Compute / Monster

Run a lightweight bot continuously or schedule heavier compute only for your trading window.

₹899or ₹1,999/month + GST
Compare compute →KYC required before provisioning.
Optional add-onTrading Suite on your VPS

Broker OAuth, callbacks and encrypted token storage stay on your machine. Use your own strategy; we do not provide indicators, options logic or signals.

See Trading Suite →

Quick setup · stays on this page

Sign in, get your IPv6 and token,
then copy the code.
1 GB · 10 RPS · 7 days · no card.

Choose your broker and client ID below. We remember them through Google login, assign the dedicated IPv6 here, and reveal one long token once. Broker passwords and trading access tokens stay with you.

We store: Google email, broker name, client ID, assigned IP and a hash of the ServLoci token.
We do not ask for: broker password, PIN, TOTP, broker API secret or broker access token.
All seven broker examples and Colab guide →
Finish setup

Choose where orders should exit

  1. 1Details
  2. 2Assign IP
  3. 3Copy setup
Checking your sign-in…

Recommended algo workflow

Use good compute for Python.
Use ServLoci for the exit IP.

Heavy pandas, Jupyter, backtests and multiple data feeds can exhaust a 1 GB VM or saturate shared CPU until the machine becomes slow or unreachable. Free and low-cost VPS plans may also throttle sustained burst usage or send a fair-use notice under their own policies.

01 · ComputeResearch in Colab or locally

Run analytics, indicators and backtests where useful CPU and memory already exist.

02 · RouteConfigure trading-static-ip

Approved broker calls leave through your assigned ServLoci IPv6; unrelated notebook traffic stays direct.

03 · OperateKeep the network layer lean

StaticIP supplies the stable broker-facing path. Use managed compute for unattended or continuously running strategies.

Colab is interactive research compute, not a 24×7 trading host. Runtimes can disconnect and resource limits vary. For unattended execution, keep the same ServLoci exit IP but move the strategy to managed, persistent compute. Google Colab runtime FAQ ↗

The Problem

Six ways your automation quietly dies.

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.

01

Your home broadband IP rotates

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.

router reboot → 3 brokers blocked
02

Someone else already claimed your IP

Many residential and mobile connections use CGNAT, where multiple subscribers share one public IPv4. That address is a poor fit for an account-specific broker allowlist.

shared with 500+ strangers
03

Notebook runtime IPs are temporary

A hosted notebook can move to a different runtime when it reconnects. Your research still works, but the outbound address may no longer match the one approved for broker order routing.

new runtime → new egress
04

Even you can't reuse your own IP

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.

old allowlist entry → rejected calls
05

Mobile networks are worse

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.

new IP every ~5 min
06

Every extra account = another VPS bill

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.

5 accounts × ₹700 = ₹3,500/mo just for IPs

Dead Ends

The tradeoffs in common alternatives

✗

Another VPS

A VPS can provide a fixed address, but it also makes you operate a server just to satisfy a networking requirement. Multiple identities can multiply infrastructure and maintenance work.

✗

Broker cloud

Broker-hosted tools can reduce setup for that broker, but they may not fit a cross-broker workflow or the compute environment where your strategy already runs.

✗

Algo platforms

Managed algo platforms can accelerate standard strategies, but custom workflows must fit their supported features, integrations, limits and pricing.

✗

Shared proxy pools

Shared exit IPs can inherit the traffic reputation and rate behaviour of unrelated customers. They also cannot provide the account-specific network identity a dedicated allocation offers.

Broker and regulatory requirements vary by API and can change. A static IP is a network-control component, not a compliance guarantee; confirm current requirements before live trading.

The math

The quiet cost of "let's see what happens."

When the source address no longer matches an approved route, execution can stop until the network or broker configuration is corrected. The impact depends on the strategy and broker.

Rejected
order API request

A strategy can produce a valid signal while the broker rejects the request because the observed source no longer matches the approved route.

Manual
allowlist rework

A changed source address can mean updating settings or contacting broker support, depending on that broker's current process.

Extra
server operations

A VPS can provide a fixed IP, but it also adds patching, monitoring, deployment and credential-management work when the compute itself was not needed.

Shared
network identity

A residential or pooled address may represent unrelated users, which makes it a weaker identity for an account-specific broker allowlist.

The measurable outcomefewer network variables between a risk-approved order and the broker API

The Solution

Just the exit path.
Everything else
is yours.

One dedicated IPv6 address, yours alone. Route the broker-facing calls that require an approved source through it via SOCKS5 or the restricted HTTP forwarder.

  • Run from anywhere — laptop, VPS, Lambda, GitHub Actions. Same exit IP.
  • Keep the same approved source while the ServLoci allocation is active and the broker's policy remains compatible.
  • Route only the write side — keep market data, indicators and backtests direct where broker policy permits; send approved order and trade paths through the dedicated exit.
  • Skip an extra VPS when it adds no compute value — keep the strategy on your existing environment and use ServLoci for the broker-facing exit.
  • Choose SOCKS5 for broker end-to-end TLS. Use the optional application forwarder only when its documented data path fits your security requirements.
  • Portable across custom solutions, off-the-shelf apps, and any HTTP/REST SDK.
Start free · 1 GB for 7 days · no card See setup docs
Your code
any machine · any location
laptopVPSLambda
SOCKS5 · 3 lines of Python
comm.servloci.in
your dedicated IPv6 exit
2401:c080:2400:2fed::xxxx
always same IP · whitelisted once
Dhan
Kite
Groww
+ any

What you actually get

Static routing now.
Execution tools next.

The dedicated IPv6 service is live today. A unified trading library and trade-management layer are separate private-beta products in development.

Live now

Dedicated Static IPv6

One dedicated address for the life of the active allocation. Register it with compatible broker APIs, then use the same broker-facing exit from your notebook, workstation or automation runner.

  • Runs from laptop, VPS, mobile, GitHub Actions — same exit IP
  • Not shared with any other subscriber, ever
  • Works with any broker that supports IP whitelisting
Private beta

Unified Trading Library

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", ...)
  • Normalises fills, positions, holdings across brokers
  • No more per-broker adapter code cluttering your algo
Private beta

Trade Manager & Dispatcher

A planned dashboard for supported accounts, routing rules, fills, exposure and P&L. Private-beta scope may change as broker integrations are validated.

  • Multi-account routing rules (allocations, exclusions)
  • Live position + P&L across every whitelisted broker
  • Kill-switch: halt every account with one click

Paying subscribers can request early beta access. Beta scope, availability and future pricing may change.

Under the hood

Infrastructure, not magic.

A static exit IP is a solved, boring networking problem. We've built the plumbing so you don't have to think about it.

01

Your own /128 IPv6

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.

02

Auth-gated SOCKS5

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.

03

Your data stays encrypted

With SOCKS5, broker HTTPS remains TLS-encrypted between your client and the broker. The optional /api/v1 application forwarder is a separate path that processes customer-authorized order requests.

04

Address bound at interface level

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.

05

Three lines is genuinely all it takes

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.

—

What this is and isn't

We give you a stable broker-facing exit IP. Your strategy and execution logic stay on your compute. Choose SOCKS5 for broker end-to-end TLS, or the restricted /api/v1 forwarder for authorized order and trade paths.

Setup

Three steps, under 10 minutes

01

Sign up

Google sign-in. Share your broker name and client ID. We assign a dedicated IPv6 and SOCKS5 credentials.

~2 minutes
02

Patch

Three lines before your broker SDK import. No VPS config, no nginx, no iptables. The SDK never knows it's proxied.

3 lines of Python
03

Whitelist once

Add your IPv6 to each broker's whitelist settings. Done. Forever. Move machines as often as you like — the exit IP never changes.

dedicated while active

Advisory

One IP. Many brokers.
Minimum data. Zero VPS.

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.

01
One address

One IPv6 across compatible broker routes.

The same IPv6 can be used with an approved account on Dhan, Kite, Groww, FYERS, Upstox, ICICI Direct or Kotak Neo. Broker approval and IP-family rules still apply. Don't buy a second address until you actually need a second identity.

02
Data top-up

₹5 / GB. Top up, don't over-provision.

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.

03
Only orders

Route only the write side. Read side stays direct.

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.

04
Your machine

Skip the VPS. Use your own hardware.

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?"

05
Local analysis

All the heavy lifting stays local.

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.

06
AI agent

Point your agent at the proxy. Done.

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

Python SDK patch

Configure socks5h before importing your broker library. The proxy accepts only your selected broker's approved HTTPS API destinations.

pysocks_setup.py
# pip install PySocks import socks, socket socks.set_default_proxy( socks.SOCKS5, "comm.servloci.in", 1080, username="BROKER:CLIENT_ID", # e.g. "dhan:1000000001" password="YOUR_API_KEY" ) socket.socket = socks.socksocket # global patch — before any SDK import from dhanhq import dhanhq
$ pip install PySocks

Pricing

Start with routing. Add compute only when needed.

Five clear monthly options, from a router on your own VM to scheduled managed compute. Prices show the taxable value and the final amount including 18% GST.

ServLoci Router · your VM
₹199/month + GST
₹234.82/month including 18% GST
  • Use a free-tier or paid cloud VM you already control
  • Easy IP discovery, broker order routing, and heartbeat health
  • Your provider bill, VM access, and OS remain yours
Connect my VMSee the VM installation flow

No VM included. Best when free cloud credits or an existing server already cover your compute.

Most common
Static IP · routing only
₹299/month + GST
₹352.82/month including 18% GST
  • One dedicated IPv6 exit — yours alone
  • Hosted SOCKS5 + /api/v1 · runs on ServLoci infra
  • Seven broker-specific SOCKS5 routes · whitelist once
  • Free 7-day trial · 1 GB · no card
Start free · 1 GB for 7 days · no card Read docs before you buy

Explorer is free with no card. Upgrade to ₹299/month + GST to retain the same allocation after day seven. Annual: ₹2,999 + GST (₹3,538.82 billed).

Route VPS
From ₹599/month + GST
₹706.82/month including 18% GST
  • Small managed IPv6-first VPS with ServLoci routing
  • Sized for order routing and one lightweight always-on process
  • Managed provisioning, health, updates, and broker-facing IP
  • Provider, region, and exact resource limit confirmed before activation
Request Route VPSCompare compute options

The ₹599 floor assumes an eligible low-cost IPv6-only provider. IPv4 or a larger machine is quoted separately.

Compute VPS
From ₹899/month + GST
₹1,060.82/month including 18% GST
  • Managed VPS for the IP lane and a lightweight trading workload
  • More memory than Route VPS for an always-on Python process
  • Deployment, process health, logs, and network routing managed
  • Not intended for large backtests, model training, or many data feeds
Request Compute VPSSee workload boundaries

The starting price assumes an eligible IPv6-only 1 GB class plan. Final resources are written into the activation quote.

Small Monster
From ₹1,999/month + GST
₹2,358.82/month including 18% GST
  • Choose a controlled persistent machine or scheduled compute
  • Start before trading and stop after the configured time window
  • Spot available for restart-safe jobs; controlled On-Demand for continuity
  • Resource and monthly usage allowance agreed before activation
Configure Small MonsterCompare Spot and controlled compute

₹1,999 is the base service price. Usage beyond the agreed infrastructure allowance is approved and billed separately.

Free cloud VM

Already have AWS, Google Cloud, Azure, Oracle Cloud, or Vultr credits? Use our provider-neutral installer to add Python and all seven broker SDKs to an Ubuntu/Debian VM you operate. Add ServLoci Router for ₹199/month + GST for private enrollment, IP provisioning, health, and order routing. Open the VPS installer →

What ServLoci brings beyond a raw VPS or proxy
Raw cloud VPSFrom $3.50–$7/mo
You receive compute and an address. You still provision the network, secure the host, install broker SDKs, monitor it, and recover failed jobs.
Generic dedicated proxyOften sold per IP
Useful for scraping and geo-targeting, but not packaged around Indian broker allowlists, order-only routes, broker SDK setup, or trading-runtime health.
ServLoci Router₹199 + GST
Adds private enrollment, IP discovery, approved broker routing, health, docs, and tested SDK paths to a VM you already own.
Trading Suite add-onYour VPS only
Adds a local encrypted Broker Vault for Kite, Dhan, and FYERS authentication. Broker secrets and sessions stay on your VPS; ServLoci's central system never receives them.
ServLoci cloud₹299 + GST
One dedicated IPv6, destination-controlled SOCKS5 and /api/v1, broker guides, egress verification, and no VPS to administer.
Small MonsterFrom ₹1,999 + GST
Scheduled Spot or controlled compute with routing and lifecycle management.

FAQ

Honest answers

Do Indian brokers actually support IPv6 whitelisting?
ServLoci provides setup guides for Dhan, Kite (Zerodha), Groww, FYERS, Upstox, ICICI Direct Breeze and Kotak Neo. Compatibility depends on the broker, API product, account relationship and current IPv6 policy, so each guide includes an official source and last-verified date.
Is my trading data safe going through your proxy?
With SOCKS5, broker HTTPS remains TLS-encrypted between your client and the broker; ServLoci does not terminate that broker TLS session. The optional /api/v1 forwarder operates at the application layer and processes only customer-authorized order and trade paths. Broker secrets used for central verification are not persisted. If you install Broker Vault, its encrypted secrets remain only on your own VPS.
Does the Trading Suite provide indicators, options strategies, or signals?
No. Those inputs can be risky and remain entirely yours. The optional Trading Suite installs a Broker Vault on a VPS you control, completes broker authentication, and makes the current session available only to code on that VPS. Your code chooses every trade; ServLoci only helps route the broker call.
What if the proxy goes down?
Your algo will fail to connect to the broker — the same as if your internet went down. We don't guarantee 100% uptime (anyone who does is misleading you). What we guarantee is that when the proxy is up, your exit IP is always the same one your broker has whitelisted.
How is this different from a VPN?
A VPN typically gives you a shared IP and adds OS-level routing that affects all your apps. SOCKS5 is application-level — only your Python process uses the proxy. Everything else on your machine continues as normal. And your exit IP is dedicated: no other user shares it.
Can I use one IP across multiple brokers?
The same IPv6 can be registered across compatible broker API routes when their current policies allow it. Check the broker-specific guide before relying on a shared address across accounts or family relationships.
How long does setup take?
Google sign-in and the no-card Explorer allocation usually take about two minutes. Broker allowlisting and approval time varies by broker. Your portal provides an egress check and broker-specific guide so you can verify each step before live routing.
What does Small Monster include?
Small Monster is a managed execution machine with ServLoci routing and lifecycle control. Choose either a persistent controlled machine or a larger Spot/On-Demand worker that wakes before the agreed trading window and stops afterward. The exact CPU, memory, provider, schedule, and included usage allowance are written into the activation quote; usage above that allowance is never implied to be unlimited.

Start today

You're two minutes from a dedicated IPv6.

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.

Read the docs first

or submit your broker details directly

Submitted! We'll email your SOCKS5 credentials within 24 hours.
Something went wrong. Please try again.
Contact
Broker details
Proof of account
Click to upload or drag & drop
PNG · JPG · PDF — max 5 MB

Do not send passwords, PINs, TOTP codes, API secrets or access tokens in this form.