The Platform
AI Strategy Infrastructure for Broker-Led Markets
Stretus enables brokers and fintech platforms to provide intelligent strategy experiences without rebuilding the complete strategy lifecycle internally. It is API-led, configurable and white-labellable, and it occupies exactly one layer of the stack, the strategy lifecycle, leaving the client relationship, risk authority and market connectivity with the broker.
Software infrastructure only. No investment advice, no brokerage services, no guaranteed returns.
01 · Client experience
Broker digital channels
02 · The governed layer
Stretus AI Strategy Infrastructure
03 · Execution authority
Broker execution environment
Overview: what Stretus is
Stretus is AI-native strategy infrastructure for broker-led markets. It adds a governed strategy lifecycle to existing broker web and mobile journeys, from AI-native creation and deterministic validation through backtesting, activation, monitoring and controlled execution.
It is not a broker, an investment adviser or a portfolio manager. It holds no exchange membership, no client funds and no securities, and it makes no execution decisions, the broker's OMS and RMS remain authoritative throughout.
Those four exclusions are published deliberately. A vendor that states its own boundaries is easier for a compliance function to approve than one that leaves them to be discovered, and each of them is enforced by the architecture rather than promised as conduct.
Stretus does not hold
- Stretus is not a broker and holds no exchange membership of its own.
- Stretus is not an investment adviser and publishes no recommendations.
- Stretus is not a portfolio manager and holds no client funds or securities.
- Stretus does not make execution decisions, the broker's OMS and RMS remain authoritative.
The business problem
Indian market access has broadened while participation in derivatives has narrowed, and the operating model most retail journeys offer has not kept up. CDSL investor accounts grew from 10 crore in November 2023 to 18.59 crore by June 2026, while unique active individual equity-derivatives traders declined about 18% year on year in FY26.
SEBI's Press Release 50/2026 of 20 August 2026 reported that 87.7% of individual equity-derivatives traders incurred losses in FY26. That is regulatory context rather than a Stretus performance figure, and the useful reading of it is about process: leverage, expiry, liquidity and contract-selection risk require more discipline than a chart and an order button provide.
For a broker, the commercial version of the same problem is engagement that stops at order placement, and a build programme, builder, instrument service, backtester, validator, approval workflow, monitoring plane, audit trail, where none of the components are what differentiate a brokerage.
87.7%
of individual equity-derivatives traders incurred losses in FY26.
SEBI Press Release 50/2026, 20 August 2026
Regulatory context, not Stretus performance.
Four things a disciplined operating model has to supply
Ideas need structure
entry, exit, risk, time horizon and instrument identity must be explicit before testing starts
Contracts need identity
an option is more than its underlying: expiry, strike, call/put right, lot and post-trade context all matter
Evidence needs context
return must be read with drawdown, risk-adjusted metrics, costs, trade quality and data coverage
Automation needs limits
positions, order value, daily loss, allocation, stale prices and connector eligibility should stop unsafe exposure
Gate 01
Build
Describe the market idea
Gate 02
Validate
Resolve asset and contract
Gate 03
Test
Backtest with trading charges applied
Gate 04
Improve
Manual, Loop, Target Moves
Gate 05
Paper
Observe without live capital
Gate 06
Execute
Eligible connector route
Gate 07
Monitor
Risk, state and activity
Gate 08
Govern
Approvals, exposure, audit
The solution
One governed layer embedded within the broker ecosystem, carrying a strategy from a plain-language description through validation, testing, paper observation, policy-gated activation, monitoring and audit, with the broker's authority intact at both ends.
The lifecycle runs in eight stages: Build, Validate, Test, Improve, Paper, Execute, Monitor, Govern. Each is a gate rather than a step, which is the distinction that matters: a strategy that fails validation does not advance, and a candidate that misses its declared objective is refused promotion rather than flagged for optimism.
Architecture
Three layers with clean ownership boundaries. Broker digital channels hold brand, identity, consent, entitlements and client journeys. The Stretus strategy layer holds AI-native creation, deterministic validation, policy-gated activation, evidence and governance. The broker execution environment holds authoritative risk decisions, order routing, account permissions and market access.
Orders flow left to right and never leave the broker's perimeter: execution is through the broker's own connection under the broker's own exchange membership, and every algorithmic order carries the identifier the exchange assigned.
That shape is not a commercial preference. Under SEBI's circular of 4 February 2025, extended by circular SEBI/HO/MIRSD/MIRSD-PoD/P/CIR/2025/132 of 30 September 2025 and applicable to all stockbrokers from 1 April 2026, an algo provider is empanelled by the broker, treated as the broker's agent, and cannot connect to an exchange directly.
Implemented broker adapters
- Upstox
- Zerodha
- Angel One
- Dhan
Production availability depends on the broker API, account and segment permissions, credentials, instrument coverage, and deployment approval. Implemented integration paths do not imply universal live certification. Third-party names are shown only for identification and do not imply endorsement.
Capabilities
| Capability | What it does |
|---|---|
| AI strategy builder | Captures intent in natural language, asks for missing inputs, and assembles a reviewable rule set through deterministic validation |
| Backtesting engine | Applies costs at fill time and reports return, risk-adjusted metrics, drawdown and trade quality, with a gate that refuses weak candidates |
| Broker integration | API-led and white-label integration with scoped credentials, approved endpoints and broker-whitelisted static IPs where required |
| Risk governance | Exposure, loss, readiness and lifecycle controls, with approvals, rejection context and connected audit evidence |
| Options and derivatives | Contract-aware handling of expiry, strike, right, lot and margin, with HALT-NEW emergency controls that fail closed |
| Custom indicators | Organisation-specific indicator groups through a guided validation, versioning and activation workflow |
| Strategy marketplace | Discovery where publication is restricted to eligible verified SEBI-registered Research Analysts under broker policy |
| Remote strategy execution | Signed, time-bounded order intents from private infrastructure, validated and routed without the logic being transmitted |
| Monitoring and observability | Strategy health, order activity, latency, exceptions and audit evidence retained for at least five years |
| Enterprise security | Self-hosted deployment, tenant isolation, role-based access, BYOK and controlled egress |
Capability availability depends on tenant configuration, entitlements, connector readiness and deployment policy.
Certifications we do not hold
- No SOC 2 report
- No ISO 27001 certification
- No published penetration test
Deployment model
Four ownership columns. Client channels are broker-owned. Identity and API controls are a shared boundary. The tenant strategy layer is Stretus. OMS, RMS and exchange routes are broker-owned.
Within that, three deployment shapes are available: inside the broker's own estate, a dedicated single-tenant instance, or shared tenancy. For a broker running colocated infrastructure with a separate disaster recovery site, a multi-tenant cloud service is usually the wrong answer, and we will say so rather than sell it.
Each enterprise deployment defines its own capacity targets, security boundaries, rollout phases, support coverage, integration responsibilities and operating ownership during technical discovery. Broker and exchange procedures remain authoritative for each production rollout.
Security
Two structural facts frame everything else: Stretus holds no client funds or securities, and it has no exchange connectivity of its own. Beyond that: tenant isolation, role-based access, scoped credentials with rotation and one-time secret display, BYOK for AI providers, and controlled egress with dedicated outbound IPs where configured.
What we do not have is stated on the security page as plainly as what we do: no SOC 2 report, no ISO 27001 certification, no publishable third-party penetration test, and no date for any of them. If a certification is a precondition for your organisation, the useful time to say so is before an evaluation rather than after six weeks of one.
Enterprise use cases
Four shapes recur: a broker launching a differentiated platform, an adviser governing publication, a trader structuring an idea, and an institution protecting proprietary strategy logic.
Each is covered in depth on its own solution page, and each carries the same qualification: availability varies by broker, exchange, account, connector and tenant. Implemented integration paths do not imply universal live certification.
Ownership boundaries
Where Stretus sits in the stack
01 · Client experience
Broker digital channels
- Web
- Mobile
- APIs
Broker-owned
02 · Strategy lifecycle
Stretus strategy infrastructure
- Create
- Validate
- Backtest
- Activate
Stretus
03 · Execution authority
Broker execution environment
- OMS
- RMS
- Markets
Broker-owned
Broker-owned channels · policy-gated activation · OMS/RMS-authoritative execution
Stretus holds no exchange connectivity, no client funds and no securities
Benefits
Business benefits
Shorten time to market
Add differentiated strategy journeys without rebuilding the full lifecycle internally.
Govern every activation
Apply broker-defined eligibility, policy and execution controls before strategies go live.
Expand progressively
Start with defined users and capabilities, validate the evidence, then scale with confidence.
Keep the boundaries clear
Broker-owned channels, policy-gated activation, OMS/RMS-authoritative execution, stated the same way on every page.
Use cases
Enterprise operating situations
Illustrative operating situations. Availability varies by broker, exchange, account, connector and tenant.
- Challenge
- Launch a differentiated strategy experience without separately building the builder, backtester, marketplace, monitoring and governance layers.
- Stretus role
- Integrate through broker journeys while client ownership, approvals, risk policy, OMS and RMS remain broker-controlled.
- Outcome
- A configurable premium product on existing brokerage infrastructure.
- Challenge
- Keep private code or connected alert logic outside the platform without losing execution governance.
- Stretus role
- Validate signed, time-bounded intents, apply configured risk, and route only through eligible accounts and connectors.
- Outcome
- Remote and native strategies share one monitored operating workspace.
- Challenge
- Manage several strategies with consistent publication, evidence and monitoring.
- Stretus role
- Broker or admin teams verify documents, activate eligible RA access, and gate publication by policy.
- Outcome
- A reviewable, role-controlled client workflow with accountable creator context and suspendable access.
- Challenge
- Translate an equity, futures or options idea into exact, testable rules without coding.
- Stretus role
- Resolve the instrument, assemble conditions, test with brokerage and statutory charges applied, and support paper observation before eligible deployment.
- Outcome
- A disciplined INR-reported workflow with visible drawdown, risk and contract identity.
Security posture
Security considerations
- No custody, structurally
- Stretus holds no client funds or securities and no exchange connectivity of its own. Orders leave through the broker's connection under the broker's membership.
- Self-hosted deployment available
- Run inside your own estate, where the data does not leave it and you hold the keys.
- Certifications we do not hold
- No SOC 2, no ISO 27001, no publishable penetration test, and no date for any of them. Stated on the security page rather than omitted.
Answers
Frequently asked questions
Is Stretus a broker?
No. Stretus is a technology provider. It holds no exchange membership, no client funds and no securities, and it makes no execution decisions, the broker's OMS and RMS remain authoritative.
Does Stretus provide investment advice or recommendations?
No. It is software infrastructure. Strategy content is authored by the customer or by an eligible verified SEBI-registered Research Analyst under broker-governed policy, and a marketplace listing is a discovery object rather than a recommendation.
Who carries the regulatory responsibility?
The broker. NSE circular NSE/INVG/67858 of 5 May 2025 states that brokers are fully responsible and liable for all orders emanating through their IBT, STWT, Client API and Vendor API systems, and an algo provider is empanelled by the broker and treated as its agent.
Can it be deployed inside our own infrastructure?
Yes. Self-hosted deployment inside the customer estate is supported, in which case the data never leaves that estate and the customer holds the keys.
Which markets and instruments are covered?
NSE and BSE ecosystems, cash, futures and options, and configured currency products, with INR-native portfolio reporting. BSE cash is represented; the BSE derivative catalogue follows a phased enablement path.
Is live F&O execution available?
The NSE futures and options contract model is available in the platform. Live broker execution is connector-enablement dependent, and availability depends on broker, account, segment, catalogue, permissions and tenant configuration.
Do you publish pricing?
No. Commercial terms depend on deployment model and scale and are established during technical discovery rather than published as a table.
How do we evaluate it?
Arrange a working demonstration covering strategy creation, F&O contract handling, backtesting, broker controls and integration boundaries. For a white-label infrastructure layer, a scoped walkthrough is more informative than a self-serve sandbox.
Ecosystem
Explore the capabilities
AI Strategy Builder
Natural-language strategy creation with deterministic validation: intent becomes a structured, reviewable rule set your client can read before testing.
Enterprise Security
Self-hosted deployment, tenant isolation, BYOK, controlled egress and role-based access, with an explicit statement of the certifications we do not hold.
Broker Integration
Integrate a governed strategy layer into existing broker journeys while identity, entitlements, risk policy, OMS/RMS and market access stay broker-owned.
Arrange a working demonstration
Review strategy creation, F&O contract handling, backtesting, broker controls and integration boundaries with the team. If you would rather talk to an engineer than a salesperson, say so and we will arrange that instead.
Risk and disclosure
Trading and derivatives involve risk of loss. AI output requires review. Backtests and simulations do not predict future results; live outcomes can differ because of costs, latency, slippage, liquidity, rejections, broker rules and market conditions. Availability varies by broker, exchange, account, connector and tenant. Product information only; not investment advice.