Why usFeaturesTemplatesBlogGlossary

What SEBI's Feb 2025 Retail Algo Framework Actually Changes for You

For most of the last two decades, algorithmic trading in India was a privilege of institutions. In February 2025, that changed — carefully, and with guardrails. If you are a self-directed investor who wants to run a rules-based strategy, this is the regulation that makes it legitimate. It is worth understanding what it does and does not do.

The history: why retail was locked out

The exclusion was not an accident; it was the explicit design of two earlier rules.

  • The 2008 Direct Market Access circular restricted DMA (sending orders straight to the exchange) to institutional clients: foreign investors, mutual funds, insurers.
  • The 2012 algorithmic trading framework (CIR/MRD/DP/09/2012) required each broker’s algos to be pre-approved by the exchange, with system audits every six months. There was no defined route for an individual to deploy their own algorithm.

For roughly thirteen years, the combined effect was simple: institutions automated, retail clicked buttons by hand.

What the February 2025 circular does

SEBI’s circular of 4 February 2025, Safer participation of retail investors in algorithmic trading, is the first framework to give retail a sanctioned, API-based path. It arrives a few months after SEBI’s November 2024 clampdown on retail F&O trading, which tripled minimum index-derivative contract sizes and cut weekly index-options expiries to one per exchange. Its core provisions, as summarised by Zerodha:

1. White-box vs black-box. The framework distinguishes algorithms whose logic is disclosed to and controlled by the user (“white-box” / execution algos) from opaque ones (“black-box”). Black-box providers face a heavier burden — registration as a Research Analyst and filing strategy logic with the exchange, with re-approval when the logic changes. White-box, user-built strategies are the lighter-compliance path.

2. An order-rate threshold. Below a threshold of 10 orders per second per client, an algo does not need per-algo exchange registration. Above it, registration through the broker is required. This is the line that separates an ordinary retail strategy from something that looks like high-frequency activity.

3. Mandatory safety controls. Brokers must support exchange-triggered kill-switches per algo, static-IP access for API order flow, two-factor authentication, and audit trails. These are infrastructure obligations — non-trivial to build correctly, and squarely on the broker-and-platform side, not the individual’s.

What it means in practice

The framework is, in effect, a description of the right kind of retail algo: one whose logic is transparent, whose order rate is modest, and whose execution sits behind kill-switches and authenticated APIs. That is a meaningful endorsement of patient, rules-based investing — and an implicit discouragement of opaque, high-frequency retail punting.

It also shifts a real cost. Static IPs, kill-switch handling, throttling, broker-API integration and audit logging are exactly the things an individual cannot reasonably build alone. A managed platform absorbs that complexity.

Where saral.money fits

A visual strategy graph, where every rule node is visible and editable, is white-box by construction — there is no hidden model, only rules you can open and read. That maps directly onto the lightest-compliance category the circular defines. saral.money is built to route through broker APIs, stay within sensible order-rate limits for portfolio strategies that rebalance over weeks and months, and remain inspectable end to end.

Now the honest limits, because regulation is a moving target:

  • The rollout was staged, and it is now live. SEBI’s September 2025 circular pushed broker registration and mock sessions into late 2025 and early 2026, with full implementation required for all stock brokers from 1 April 2026 — a deadline that has already passed.
  • Live execution today runs through Dhan, with additional brokers planned. saral is not yet connected to every broker, and we would rather state that plainly than imply universal coverage.
  • Compliance is shared. The platform builds for the framework, but live trading always runs through your SEBI-registered broker under its risk controls. Nothing here removes the broker from the loop.

Algo trading is not now a free-for-all: SEBI has defined a safer, transparent, rate-limited path, and a no-code, white-box, backtest-first platform is built for exactly that path.

What to try next

If you want to understand the strategy side before the regulatory side, start with how to backtest properly on Indian markets, then open a strategy in saral.money and see what a transparent, rule-by-rule pipeline actually looks like. The whole point of “white-box” is that you can read every decision the strategy makes — so read them.