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 Indian retail traders running MT5-based mechanical strategies via Expert Advisors, the deadline forces a structural decision that depends on which market the EA targets. MT5 itself is platform-agnostic — it runs against whatever broker terminal connects to the underlying market. The SEBI compliance question depends on the broker, the market, and the residency of the trader, not on MT5 as a platform.
This piece walks through the post-April 2026 reality for MT5 EA traders specifically. The framework distinction. The strategy-by-strategy path. The realistic decision tree for Indian retail running EAs across Indian-derivative and offshore-forex environments simultaneously.
What SEBI's Framework Actually Covers
SEBI's retail algo framework applies to retail algorithmic activity in Indian equity derivatives — futures and options on Indian indices and stocks listed on NSE and BSE. The framework requires retail algo flow routes through a SEBI-registered algo platform. The registered platforms supply audit trail, risk-control standards, exchange-side execution path, and regulator-supervised compliance evidence.
The framework does not extend to offshore-broker activity. A trader running an MT5 EA on Exness's MT5 platform in April 2026 is not affected by SEBI's framework. The trade is happening on a non-Indian exchange under a non-Indian regulator. SEBI has no jurisdiction over the platform, the broker, or the strategy logic.
The trader is, however, affected by FEMA's framework for permitted versus non-permitted currency transactions. Offshore forex trading on non-permitted pairs remains structurally non-permitted under FEMA regardless of whether the trader is using manual entry, an EA, or any other execution mechanism.
The Strategy-by-Strategy Decision
Strategy type 1: MT5 EA on USD/INR futures (NSE). USD/INR futures listed on NSE are an Indian equity derivative product. The SEBI framework applies. Post-April 2026, retail EA work on USD/INR via MT5 connecting to a SEBI-registered Indian broker requires that broker to be operating a registered algo path. Many SEBI-registered brokers do not currently offer MT5 connectivity to Indian-derivative products; the standard Indian retail derivatives platform is the broker's own front-end (Zerodha Kite, Angel One Trade, Upstox Pro). MT5 EA work on Indian derivatives is a niche path with limited broker support pre-2026; post-April 2026, the few brokers that supported it must demonstrate registered algo supervision over the EA flow.
Strategy type 2: MT5 EA on Nifty 50 weekly or Bank Nifty monthly options. These are Indian equity derivative products. Same framework applies. Standard retail Indian options trading does not run through MT5 — the Indian retail options stack is built around domestic broker platforms. MT5 EA work on Indian options is rare and structurally constrained.
Strategy type 3: MT5 EA on EUR/USD or GBP/USD via offshore broker (Exness, XM, IC Markets). The product is non-permitted under FEMA for an Indian resident. SEBI's framework does not apply. MT5 EA work continues structurally available — the trader can deploy EAs as before — but the underlying FEMA exposure on non-permitted pairs persists. The deadline does not change anything for this category. The pre-existing risk continues.
Strategy type 4: MT5 EA on US equity index CFDs via offshore broker. SEBI's framework does not apply (not Indian equity derivative). FEMA's framework on offshore investment activity may apply depending on the specific transaction structure and the trader's overall LRS-routed positioning. MT5 EA work continues operationally available.
Strategy type 5: MT5 EA on gold (XAU/USD) via offshore broker. Gold-USD via offshore broker is structurally similar to non-permitted forex. SEBI's framework does not apply. FEMA exposure persists on the underlying currency conversion if the trader's funding routes through Indian banking. EA work continues operationally.
The Decision Tree for an Indian MT5 EA Trader
The realistic decision tree for an Indian retail trader currently running MT5 EAs across multiple strategies post-April 2026 narrows to specific operational choices.
Question 1: Are any current EAs targeting Indian equity derivatives? If yes, those need to migrate to a SEBI-registered algo platform path. MT5 is structurally not the Indian-derivative retail platform; the migration is generally to the broker's native algo path or to a registered third-party (Streak, etc.).
Question 2: Are current EAs running on offshore forex pairs? If yes, the SEBI framework does not change anything. The pre-existing FEMA exposure continues. The trader's compliance question is not the new SEBI deadline but the underlying FEMA frame, which is a question the trader was already answering one way or another before April 2026.
Question 3: Does the trader's account structure pass FEMA scrutiny under the trader's own assessment? If the answer was "yes, with risk acceptance" before April 2026, it remains that. If the answer was "uncertain," the SEBI deadline does not resolve the uncertainty — only direct legal review with a chartered accountant or SEBI-registered investment advisor does.
Question 4: Is migrating to non-Indian markets entirely (US equities options, EU forex via FCA-supervised broker) operationally viable? For some retail traders, the answer is yes — the trader has the capital, the international account access, and the strategy logic that translates. For most, the answer is no — the home-market familiarity and the operational simplicity of Indian-broker retail outweighs the migration cost.
Three Case-Study Walkthroughs
Case A: Retail trader running MT5 EA on offshore EUR/USD with $20,000 account. SEBI framework: not applicable. FEMA exposure: continues at pre-April level. Practical action: no change required from SEBI deadline alone. FEMA-side review remains a separate decision the trader must make with appropriate professional guidance.
Case B: Retail trader running custom Python on Zerodha Kite Connect for Nifty weekly options gamma scalping. SEBI framework: directly applicable. Custom Python via broker API without registered algo platform is non-compliant from April 1. Migration path: Zerodha Streak or an equivalent registered platform. The Python logic re-expresses in Streak's framework or migrates to a registered platform that supports custom logic with audit trail.
Case C: Hybrid trader running MT5 EAs on offshore forex AND custom Python on Indian derivatives. The Indian-derivative leg requires migration to a registered platform. The offshore-forex leg continues operationally as before. The hybrid structure splits cleanly along the SEBI/FEMA framework boundary post-April 2026.
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 MT5 connectivity to Indian-derivative products varies by broker and by regulatory category; the specific MT5 + SEBI-registered broker combinations that exist are a narrow set that retail traders should verify directly with their specific broker. The FEMA framework references reflect publicly available RBI guidance through April 2026; FEMA's application to specific offshore-broker transaction patterns has nuance that depends on the trader's specific facts. None of this analysis substitutes for direct consultation with a SEBI-registered investment advisor on the suitability of any specific strategy or platform choice, or with a chartered accountant on FEMA exposure for offshore-routed forex trading via MT5 EAs. The post-April 2026 reality has just begun crystallizing; broker-side, platform-side, and trader-side responses will continue to evolve through Q2 and Q3 2026 as the framework's enforcement priorities and operational interpretation crystallize through actual cases.