Capabilities
What the strategy layer actually does
Sixteen capability areas, grouped by the surface they belong to: what a broker's client works in, what the broker's own teams operate, and what the platform guarantees underneath both. Each page covers the problem it solves, how it works, where the limits are, and what it does not do. Capability availability depends on tenant configuration, entitlements, connector readiness and deployment policy.
Software infrastructure only. No investment advice, no brokerage services, no guaranteed returns.
Surface 01
Trader workspace
What a broker's own client sees, inside the broker's journeys and under the broker's brand: research context, strategy creation, contract-aware derivatives, testing, and a live view of their own positions and orders.
Market Intelligence
Heatmaps, past days that look like today, instrument detail and setup discovery. Screens that show what is happening, not what to trade.
AI Strategy Builder
Natural-language strategy creation with deterministic validation: intent becomes a structured, reviewable rule set your client can read before testing.
Backtesting Engine
Backtesting that applies brokerage, STT and slippage, then reports drawdown, risk-adjusted metrics and trade quality alongside return.
Options & Derivatives
Expiry, strike, right, lot and margin preserved from exploration through execution, grouped exits and reconciliation, with scoped HALT-NEW controls.
Custom Indicators
Organisation-specific indicator groups with a guided validation, versioning and activation workflow, reusable in charts, scanners and strategy rules.
Strategy Marketplace
Strategy discovery where publication is restricted to verified SEBI-registered Research Analysts and broker policy governs access, review and suspension.
Remote Strategy Execution
Keep private strategy logic on your own infrastructure and send signed, time-bounded order intents through a gateway that applies risk controls.
Surface 02
Broker console
The broker's own operating surface, approvals, algo authorization, execution control, exposure, order monitoring and the audit record. This is what makes the layer governable rather than merely configurable, and it is where the responsibility the framework assigns the broker becomes actionable. Emergency F&O controls live here too, under Execution Control.
Broker Console
Deployment control, algo authorization, execution control, risk and exposure, order monitoring and audit governance, the broker's own operating surface.
Algo Authorization
Registering algorithms, administering exchange-assigned identifiers, and tagging every algorithmic order so it is traceable during an inspection.
Risk Governance
Approval workflows, exposure controls, order limits and audit evidence, risk enforced by the platform rather than left to intention.
Monitoring & Observability
Strategy health, order monitoring, latency, exceptions and connected audit evidence, retained for at least five years and identifying the actual user.
Surface 03
Platform and integration
How the layer connects to a broker's estate, and what the platform control plane guarantees about isolation. The group a security review reads first.
Broker Integration
Integrate a governed strategy layer into existing broker journeys while identity, entitlements, risk policy, OMS/RMS and market access stay broker-owned.
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.
AI Governance
Tenant-authorised AI provider credentials protected at rest, per-tenant model policy, and a hard boundary between what a model proposes and what runs.
Instrument Catalogue
Canonical instrument records, venue enablement, market-data symbology mapping and validated reference-data imports, the foundation contract resolution depends on.
Platform Administration
Tenant provisioning, module entitlement, venue and instrument catalogues, reference-data imports, credential isolation and production activation review.
Three surfaces, one governed layer
The product ships as three consoles with different audiences. A broker's client works in the trader workspace. The broker's own risk, compliance and operations teams work in the broker console. The platform control plane sits underneath both and is operated by us, not by you , but its isolation and validation guarantees are what a broker's security review depends on, which is why it is documented publicly rather than left implicit.
Reading in that order is the fastest way to evaluate the layer. The workspace tells you what your clients would get; the console tells you what your teams would control; the platform group tells you what separates your tenant from every other one.
How to read these pages
Each capability page follows the same structure: the problem it addresses, why the industry usually gets it wrong, how it works, the architecture, business benefits, use cases, security considerations and an FAQ. Every capability statement traces to a documented product behaviour rather than a roadmap item.
Where a capability carries a boundary, the boundary is on the page rather than in a footnote. Live F&O execution is connector-enablement dependent; BSE derivatives follow a phased enablement path; implemented broker adapters do not imply universal live certification. Those constraints are more useful to an evaluator than an unqualified claim, and considerably cheaper than discovering them during a proof of concept.
The eight-stage lifecycle these capabilities serve
Build, Validate, Test, Improve, Paper, Execute, Monitor, Govern. Each is a gate rather than a step: a strategy that fails validation does not advance, and a candidate that misses its declared objective is refused promotion rather than flagged optimistically.
Reading the capability pages against that sequence is the fastest way to see where each one sits. The builder and custom indicators serve stage one; validation and contract resolution serve stage two; the backtesting engine serves stages three and four; paper observation is stage five; broker integration and remote execution serve stage six; and monitoring and risk governance serve stages seven and eight.
What none of these capabilities do
- Recommend an instrument, a strategy or a transaction to any person
- Exercise discretion over any account
- Hold, receive or transmit client funds or securities
- Connect to an exchange directly, or place an order outside a broker's own connection
- Guarantee an outcome, a return, a fill, or availability beyond an executed agreement
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.
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