Broker Connectivity

Use your broker data access to test strategies before you export code.

Connect your own broker credentials temporarily to discover available historical data, run backtests, review AI-powered risk analysis, and generate broker-ready Python packages for self-hosted deployment.

Check broker readiness View supported brokers

Broker selector

Zerodha

Dhan

Angel One

Groww

Upstox

Fyers

Shoonya

Kotak Neo

ICICI Breeze

5paisa

Capability matrix

ACTIVE_TESTING_NODE

Broker	Historical Data	Equity	Futures	Options	MCX	Instruments	Data Window	Status
Zerodha	Available	NSE/BSE	F&O	Options	No MCX	Instruments sync	Broker-limited	Ready
Dhan	Available	NSE/BSE	F&O	Options	MCX check	Instruments sync	Broker-limited	Checklist needed
Angel One	Available	NSE/BSE	F&O	Options	MCX check	Instruments sync	Broker-limited	Review required
Groww	Available	Equity	F&O check	Options check	Unknown	Instruments sync	Broker-limited	Data limits review

Temporary connection status

Credentials

session-only

Secret storage

disabled by default

Historical fetch

allowed

Order endpoints

blocked in Stockey

Data retained

temporary

Package config

generated

Historical data onlyBroker keys discardedNo live order placementUser-owned packageSelf-hosted execution

Broker access is used for testing and package preparation — not Stockey-side execution.

Stockey uses the user's authorized broker access to fetch available historical data, run strategy backtests, and generate configuration files. Live trading remains self-hosted by the user after export.

User broker credentials

entered by the user for the current testing session

Temporary session

used only for requested historical data operations

Historical data fetch

limited by broker-provided availability

Backtest engine

applies the user's own strategy rules

AI result analysis

explains risk, drawdowns, rule weaknesses, and improvement ideas

Package configuration

prepares broker-specific config placeholders

Credentials discarded

no permanent secret storage by default

Broker capability matrix

Every broker has different APIs, instruments, historical data windows, rate limits, and setup rules. Stockey makes those limitations visible before package generation.

Broker	Historical Data	Equity	F&O	Options Chain	MCX	Instrument Master	Setup Status	Notes
Z Zerodha	Available	Yes	Yes	Limited / broker dependent	Not primary	Yes	Ready checklist	API key, redirect/session flow, broker data limits
D Dhan	Available	Yes	Yes	Review	Review	Yes	Checklist needed	Sandbox/live configuration awareness
A Angel One	Available	Yes	Yes	Review	Review	Yes	Review required	SmartAPI setup and session handling
G Groww	Available	Yes	Review	Review	Unknown	Review	Data limits review	Confirm current API capability
U Upstox	Planned	Review	Review	Review	Review	Review	Planned	Capability mapping pending
F Fyers	Planned	Review	Review	Review	Review	Review	Planned	Capability mapping pending
S Shoonya	Planned	Review	Review	Review	Review	Review	Planned	Capability mapping pending
K Kotak Neo	Planned	Review	Review	Review	Review	Review	Planned	Capability mapping pending

Backtests run only as far back as your broker data allows.

Stockey shows the available historical window before running a backtest. If a broker provides limited data for a timeframe or segment, the backtest range is limited accordingly.

Historical Data Availability

Broker

Zerodha

Segment

F&O

Instrument

NIFTY Options

Timeframe

5 minute

Earliest available candle

Broker-provided

Latest candle

Previous trading session

Backtest range

User-selected within available data

Data gaps

Detected and reported

Available data window

Selected backtest range

Data gaps

Report generated

Broker historical availability varies by broker, instrument, segment, and timeframe. Stockey does not invent missing market data.

Broker credentials are session-only by default.

Credentials used only for the current historical data request

No permanent broker-secret storage by default

No order placement endpoints called by Stockey

Secrets excluded from generated ZIP files

Generated package uses .env.example placeholders

User configures broker keys on their own machine or VPS after export

session_policy.env

BROKER_SECRET_STORE=false
ORDER_PLACEMENT_ENABLED=false
HISTORICAL_DATA_ONLY=true
DISCARD_AFTER_SESSION=true

Each broker gets a setup checklist before export.

Checklist steps keep broker setup, data limits, package files, and self-hosted deployment responsibilities visible.

API Access

Create API app
Configure redirect/session flow
Confirm historical data access
Verify instrument master

Data Limits

Check available symbols
Check timeframe support
Check historical depth
Check rate limits

Package Config

Generate broker_config.example.yaml
Generate instrument mapping
Generate data-fetch script
Generate risk_config.yaml

Self-hosted Deployment

Add credentials to local .env
Configure VPS/static IP if required
Run dry-run verification
Review live-readiness checklist

AI explains the backtest. It does not tell you what to trade.

AI review is constrained to historical result explanation, risk observations, and user-approved experiment ideas.

Data limitations

AI explains whether the backtest was limited by timeframe, data gaps, segment, or broker availability.

Risk analysis

AI reviews drawdowns, stop-loss behavior, exposure, position sizing, and concentration.

Strategy improvement ideas

AI suggests tests the user may run, such as alternate exit rules, stricter risk limits, or different time windows.

AI analysis is for strategy review and education. It does not provide investment advice, security recommendations, or live trade instructions.

Generated packages include broker-aware configuration, not your secrets.

strategy_package/
folderstrategy_package/
key.env.example
folderconfig/
settingsbroker_config.example.yaml
settingsstrategy_config.yaml
shieldrisk_config.yaml
table_chartinstruments.csv
foldersrc/
folderdata/
descriptionbroker_historical_fetch.py
descriptioninstrument_master.py
folderbacktest/
scienceengine.py
monitoringmetrics.py
articlereports.py
folderbrokers/
descriptionbase.py
descriptionzerodha.py
descriptiondhan.py
descriptionangelone.py
descriptiongroww.py
codestrategy.py
terminalmain_backtest.py
lockmain_live.py
folderdeployment/
articleBROKER_SETUP.md
checklistSTATIC_IP_CHECKLIST.md
task_altLIVE_READINESS.md
warningRISK_DISCLOSURE.md

Safeguards

Secrets excluded from ZIP

Backtest uses historical data only

Live script remains self-hosted

Live mode disabled by default

User owns package

Broker capability warnings included

Connect broker data. Test your rules. Export your package.

Stockey helps you understand what your broker can provide before you bake the strategy into a self-hosted Python package.

Check broker readiness Start strategy builder