SEBI's retail algorithmic trading framework reaches full compliance on April 1, 2026 — meaning any retail algo activity in Indian equity derivatives must, as of that date, route through a SEBI-registered algo platform with audit trail and risk-control standards. For the meaningful population of Indian retail traders running mechanical strategies — gamma scalping bots on Nifty 50 weekly options, calendar spread roll automation on Bank Nifty monthly, IV-based premium-selling rules on the post-Tuesday-expiry chain — the deadline is operative. The bespoke-script regime that retail algorithmic options traders ran for the past several years is structurally constrained inside SEBI's framework from April 1 onward.
For Indian retail traders also running strategies through offshore brokers (Exness, XM, IC Markets) on non-permitted forex pairs, the SEBI framework does not apply directly — but the FEMA framework that governs the legality of offshore trading does. The two frameworks intersect in ways that retail comparison material rarely surfaces. This piece is a procedural walkthrough of the post-April 2026 reality. Zerodha Streak as the dominant compliant alternative in the discount-broker tier. Offshore custom algo as a structurally available but FEMA-exposed alternative. The decision tree that determines which path applies for which strategy.
What Zerodha Streak Actually Does
Zerodha Streak is a SEBI-registered algorithmic trading platform that provides retail traders with structured paths to deploy mechanical strategies on Indian equity derivatives. Streak's specific positioning under the post-April 2026 framework: it supplies the audit trail, risk-control standards, and exchange-side execution path that SEBI's framework requires for retail algo. Strategies that previously ran via custom Python scripts plugging into broker APIs migrate onto Streak's structured environment, where the strategy logic is expressed in Streak's domain-specific framework rather than in arbitrary Python.
The Streak environment supports a defined set of strategy primitives — entry conditions based on technical indicators, position sizing rules, stop-loss and take-profit logic, time-of-day filters, multi-leg structures for options. The framework supports many but not all strategy types that bespoke Python scripts express. Strategies that depend on external data feeds (alternative data, custom news parsing, multi-broker arbitrage) generally do not migrate cleanly into Streak's environment.
The SEBI compliance posture of Streak: it is a registered platform under the framework. Strategies deployed via Streak meet the audit-trail and risk-control standards SEBI's framework requires. The trader using Streak does not need to maintain separate compliance documentation beyond what the platform itself provides.
What Offshore Custom Algo Becomes Post-April 2026
For Indian retail traders running mechanical strategies on offshore brokers — Exness, XM, IC Markets, OctaFX, and others — through bespoke MT4/MT5 EAs, custom Python via broker API, or third-party algo services not registered with SEBI, the post-April 2026 reality is structurally different from Indian-market algo work. SEBI's framework does not regulate offshore broker activity directly. The trader running an EA on Exness's MT5 platform in April 2026 is not affected by the SEBI deadline.
The trader is, however, affected by FEMA's framework for permitted versus non-permitted currency transactions. Offshore forex trading on non-permitted pairs (anything beyond USD/INR, EUR/INR, GBP/INR, JPY/INR, EUR/USD, GBP/USD, USD/JPY) is not legalized by SEBI's algo framework — it remains structurally non-permitted under FEMA, with potential penalties up to 3x the transaction value applied to the Indian resident.
The decision space the post-April 2026 reality creates for an Indian retail trader running mechanical strategies: continue running bespoke EAs on offshore forex (FEMA-exposed but not SEBI-affected), migrate Indian-derivative algo work onto Streak or an equivalent SEBI-registered platform, shift the entire algo stack to non-Indian markets entirely (US equities options via international broker, EU forex via FCA-supervised broker), or hybrid combinations of the three.
The Strategy-by-Strategy Migration Reality
Strategy type 1: Nifty 50 weekly options gamma scalping. Pre-April 2026, this was typically run via custom Python on broker APIs (Zerodha Kite Connect, Angel SmartAPI, Upstox API). Post-April 2026, the SEBI framework requires this work routes through a registered algo platform. Streak supports gamma scalping primitives though with specific constraints on tick-level rebalancing frequency. Direct broker API access without registered platform supervision is non-compliant.
Strategy type 2: Bank Nifty monthly calendar spreads with roll automation. The post-November-2024 weekly discontinuation made monthly the only option for Bank Nifty. Calendar spread roll automation pre-April 2026 ran via custom Python. Post-April, Streak and equivalents support calendar primitives, with specific timing-rule expression that maps reasonably cleanly to Streak's framework.
Strategy type 3: USD/INR futures arbitrage versus offshore EUR/USD. Pre-April 2026, this was typically run as multi-broker custom logic spanning Indian onshore and offshore broker accounts. Post-April 2026, the Indian-side leg requires registered algo supervision; the offshore leg remains operationally available but FEMA-exposed. The structural arbitrage opportunity narrows materially because the registered-algo overhead on the Indian leg degrades the realized economics.
Strategy type 4: Pure offshore forex EA on Exness MT5. The Indian SEBI framework does not apply. The FEMA framework continues to apply to the act of trading non-permitted pairs from Indian residence. The trader's compliance question is not the SEBI deadline but the underlying FEMA exposure that pre-existed and continues post-April.
The Comparison That Retail Material Should Surface
The Zerodha Streak versus offshore custom algo comparison post-April 2026 is not symmetric. They cover different markets and different regulatory frames. The structural decision for an Indian retail trader is not "which is better" but "which strategy belongs in which path."
| Strategy class | Zerodha Streak path | Offshore custom path |
|---|---|---|
| Indian equity / Nifty options | ✅ Compliant under SEBI framework | ❌ Direct API path non-compliant post-April 2026 |
| Bank Nifty monthly options | ✅ Compliant; calendar primitives supported | ❌ Direct API path non-compliant |
| USD/INR futures (NSE) | ✅ Compliant; available product | ❌ Not available offshore |
| Permitted forex pairs (7-pair NSE) | ✅ Compliant | ❌ Not available offshore |
| Non-permitted forex (majors offshore) | ❌ Not available | ⚠ Available but FEMA-exposed |
| US equities or international markets | ❌ Not available | ⚠ Available; depends on jurisdiction |
The post-April 2026 reality is that Streak (and equivalents) become the structural answer for SEBI-supervised Indian-derivative work, while offshore custom algo paths remain available for international-market work but carry their original FEMA exposure on non-permitted pairs.
Honest Limits
This Desk did not review SEBI's primary framework documents in full — only the published summary materials and broker-side implementation guidance through April 2026. The Zerodha Streak feature set summarized here reflects publicly disclosed Streak documentation; the platform's specific capabilities continue to evolve and individual strategy migration depends on the strategy's specific expressibility in the Streak framework. The FEMA framework references reflect publicly available RBI guidance through April 2026; FEMA's application to specific offshore-broker transaction patterns has nuance that reflects RBI's compounding decisions and case-specific facts. None of this analysis substitutes for direct consultation with a SEBI-registered investment advisor on the suitability of any specific strategy migration, or with a chartered accountant on FEMA exposure for offshore-routed forex trading. The post-April 2026 reality has just begun crystallizing as the framework took effect at the start of the month; broker-side and platform-side responses will continue to evolve through Q2 and Q3 2026.