Algo trading in India: the rules, the cost, and what to do first

I have been building and running my own automated options trading system on Indian markets since early 2026. This is everything I wish someone had told me before I started: what the law actually requires of a retail trader, what it costs to run, and the order in which to build it.

Is algo trading legal in India?

Yes. Retail investors are permitted to develop and use their own algorithms to trade their own accounts. This has been true for years, and SEBI's framework for retail algorithmic trading confirmed it explicitly while adding structure around everything else. That framework was announced in February 2025 and phased in; it has applied to all brokers since 1 April 2026.

What the framework does is put the broker at the centre as the responsible party. Your broker is accountable for monitoring algo orders, enforcing limits, tagging orders so the exchange can trace them, and doing due diligence on any third-party algo provider it allows onto its systems. The practical rules you experience day to day therefore come from your broker's API terms, not from a form you file with SEBI.

Two boundaries matter, and both are about scale and distribution rather than about the act of automating:

• Order frequency. The threshold is enforced by your broker, not by you. Zerodha's own explainer puts it at 10 orders per second per client trading account, and says an algo you wrote for your own account needs no exchange registration while it stays inside that. Cross it and registration, exchange approval and an Algo ID come into play. Note that this is the broker's limit: Zerodha has said the exchange-prescribed rate had not been published and that it expects exchange limits to be higher.
• Distribution. The moment you give, sell or subscribe other people to your algo, you become an algo provider, and a completely different set of obligations applies.

Check the current position with your broker's API documentation and the latest SEBI circular before you go live. The framework is fully in force as of 1 April 2026, but the operational detail still moves. I update this guide monthly, and a circular can land the week after I do.

For what a single round trip actually costs, with every charge itemised, see what one trade costs.

What SEBI's retail algo framework actually changed

The security requirements change how you deploy. Expect to need a static IP address whitelisted with your broker, a key tied to your own account, and two-factor authentication on the login flow. A laptop on home broadband with a changing IP is not a stable deployment target. A small cloud instance with a fixed IP also solves the "my laptop slept during market hours" problem.

Your own algo versus providing one to others

This is the line that catches people, because the two sides look similar from outside and are completely different in law.

Running your own algo means your code, your account, your money. No registration below the thresholds.

Providing an algo means someone else's account trades on your logic. Selling a bot, licensing it, running it for a friend, publishing a strategy that executes through a subscription platform — all of it puts you in provider territory, where empanelment applies and, for undisclosed logic, Research Analyst registration on top.

I have looked at selling mine, and decided against it. The compliance path for a one-person operation is heavier than the income would justify, and anything I would have to say to market it — returns, win rates, "it works" — is exactly the kind of performance claim an unregistered person should not be making.

What you need before writing a line of code

1. A demat and trading account with a broker that has a real API. Not every broker does, and documentation quality varies enormously. You will live inside those docs for months.
2. API access enabled, with a static IP. Sorting out whitelisting and key management before you write code saves a frustrating week later.
3. Historical data you trust. Your backtests are only as good as this. Broker historical APIs are usually adequate for daily and minute bars; tick data is a separate and bigger problem.
4. Python, and enough engineering discipline to test things. Not the language — the discipline. The difference between a bot that survives and one that does not is almost entirely testing, logging and error handling.
5. Capital you can genuinely afford to lose. Your first live deployment will do something you did not predict. Size it so that when it does, it is a lesson rather than a disaster.
6. A machine that stays awake. A small cloud instance in Mumbai, close to the exchange, with a fixed IP.
7. Patience for a slow start. Mine took four months before it placed a live order. That was the correct pace.

Broker APIs compared

The landscape changed in 2025 when Zerodha made execution APIs free for personal use while keeping a charge for market data. Several brokers now offer APIs at no cost, which removes what used to be the first real expense for a beginner.

Pricing and terms move, so confirm on the broker's own developer page. What I weigh more heavily than the monthly fee:

• Documentation and an active developer forum. You will be stuck at 11pm on an undocumented error code.
• Websocket stability under load. Test this in week one, not month six.
• Rate limits, and how the API behaves at them. A clear error is fine; silent dropping is not.
• Order rejection messages that tell you why. This determines how well you can classify failures, which is what keeps a bad afternoon from becoming an expensive one.

What it costs to run, including the 2026 STT change

This is the section most beginners skip, and the one that decides whether a strategy that looks profitable actually is. An automated system trades more often than you would by hand, so costs compound faster than the edge does.

Securities Transaction Tax from 1 April 2026

Budget 2026 raised STT on derivatives significantly. If you are working from an older article, your cost model is wrong.

Futures STT rose by 150%. If your system trades futures frequently with a small per-trade edge, rerun your numbers before anything else.

Everything else you pay

• Brokerage — typically a flat fee per executed order at discount brokers.
• Exchange transaction charges — a percentage of turnover, different per segment.
• GST at 18% — on brokerage plus transaction charges.
• SEBI turnover fees and stamp duty — small, but real at volume.
• Slippage and impact — usually the largest cost of all, and the one no statement shows you. Measure it from your own fills rather than assuming it.

Infrastructure

A small cloud instance runs roughly ₹800–2,000 a month, and market data adds about ₹500 on Zerodha or Dhan (most other brokers in the table above don't charge for it). Total fixed cost for a one-person setup is usually under ₹2,500 a month, which is nothing compared with what a poorly tested deployment can cost in one afternoon.

Every strategy is profitable until you subtract costs. Build the cost model before the strategy, not after.

The build path, in order

1. Get data in and store it properly. Before any strategy work. Clean, gap-checked, timestamped data is the foundation.
2. Build the replay harness. The ability to rerun any past session and see exactly what your system saw. I built mine four months in and regretted not starting with it.
3. Backtest, then distrust the result. Look-ahead bias, survivorship, mid-price fills and forgotten fees each flatter your results independently.
4. Paper trade against real order books. Not against mid prices. The gap between the two is where most people's live results disappear.
5. Write the risk layer before the strategy layer. Daily loss cap, per-trade cap, maximum orders per signal, kill switch. Store the counters outside the code they limit.
6. Go live with the smallest size the exchange allows. The purpose of the first month is to find out what you got wrong.
7. Log everything, and review daily. Every decision with the state it was based on.

Mistakes that cost me money

1. A paper switch that didn't stop real trades. A strategy I had switched to paper kept trading live because a rule outranked my switch. It placed real orders for part of a session before I caught it.
2. Bugs that never threw an error. A strategy that could never take a trade, an order that silently wasn't placed, a data feed that recorded zero rows for a whole session.
3. Trusting the backtest. Fill assumptions, bar timeframes and candle-close logic each made live trading behave differently from the test.
4. Believing my own analysis. Test enough versions of one idea and a few will look brilliant by luck alone. What 25 versions of one breakout strategy taught me.

How your profits are taxed

In broad terms, and this is not tax advice: F&O trading is generally treated as non-speculative business income, while intraday equity trading is treated as speculative business income. Both usually mean filing ITR-3, maintaining books, and computing turnover correctly — which for F&O is not the same as the value of your trades, and is where most people get it wrong.

Business treatment does let you deduct genuine expenses: broker charges, data subscriptions, your cloud instance, and a share of your internet bill. Losses can generally be carried forward if the return is filed on time.

Turnover computation, audit applicability and loss carry-forward have real consequences and real penalties. Spend money on a CA who has handled F&O returns before. I am a developer who trades, not a tax professional.

Sources

• QuantInsti — Algorithmic trading in India: SEBI framework
• Upstox — Retail algo trading under SEBI's new norms
• Zerodha — Free personal APIs from Kite Connect
• Zerodha Support — How STT is calculated
• ICICI Direct — STT changes in Budget 2026
• AlgoTest — Best brokers for algo trading in India

This guide explains rules and costs for information only. It is not investment advice, not tax advice, and not a recommendation to trade. Rates and regulations change, so check the current position before you rely on them. I am not registered with SEBI as an investment adviser or research analyst.