Platform
An engine designed around one fact: the broker is the truth.
Our in-house platform runs a multi-instrument Iron Fly strategy through Zerodha Kite Connect. This page shows how it is engineered, and the kind of system we build from client rules.
The strategy behind it
What an Iron Fly is.
An Iron Fly sells an at-the-money call and put, and buys further out-of-the-money options as covers. Those covers define the maximum loss on the structure.
Shown for education. It is not a recommendation to trade this or any other strategy, and a defined structure can still lose money. The platform's own stop-out, re-entry and expiry rules go beyond this basic shape.
Cycle life
Every cycle moves through states you can see.
At any moment the dashboard shows which state an instrument is in, what it is waiting for and what the broker currently holds.
- IDLEWaiting for approval, Start, an open market and today's option chain.
- ENTERINGCovers fill and are confirmed first, then the ATM legs.
- OPEN / STOPPEDEach side follows its breakeven, stopping out or re-entering on its own.
- EXITINGOn expiry or Stop: cancel working orders, close ATM legs, then covers.
- HALTEDRetries exhausted on a close. Disarmed and flagged for a person to act.
Order handling
The trigger decides. Orders only make the broker match.
Targets and order work
Each leg has a target quantity and its own order work, with every order, tag and timer recorded. A leg with unfinished work takes no new trigger until it converges.
Retries by situation
Entries, running adjustments and closes have separate retry limits. Only a failed new entry ends a cycle, while a failed adjustment is flagged and the cycle runs on.
Positions Book
Every symbol shows each cycle's share, the total the broker should hold, what it actually holds, and whether they match.
Rate and size limits
Orders pass through an account-wide rate limiter and are sliced at each instrument's freeze limit. No order is ever sent above a leg's total size.
Shared contracts
At month end, weekly and monthly cycles can hold the same symbol. Work on that symbol is serialised and each cycle closes only its own quantity.
Safe restarts
State is written atomically and an unreadable file is set aside rather than trusted. Nothing is sent at start-up until the broker has been read again.
Expiry day and manual control
Automation where it helps, your hand where it matters.
Expiry handling
- Automatic close of the expiring cycle at the configured time
- Next cycle entered once the short legs are bought back
- Covers sold alongside the new cycle, without blocking it
- A cover that will not sell is left to cash-settle, and is clearly shown
Manual controls
- Start and Stop per instrument, or for everything at once
- Approve and Revoke per instrument
- Defer: pause trading on a running cycle until you lift it
- Tag to expire: keep a chosen cover through the expiry close
- Retry adjustment on any flagged leg
Many accounts, one dashboard
Superuser and standard users.
For families and groups with several broker accounts, one superuser dashboard can see and operate every standard user, while each account keeps its own server and credentials.
- Shared settings copied from the superuser, with lots and approvals set per account
- New accounts arrive disabled, with nothing approved
- Broker credentials never travel between servers
- Signed commands, an IP allowlist, certificate pinning and an audit log
- A daily fleet login check before the market opens
- An account can be retired only when stopped and flat
Beyond options
Stock SIP and portfolio.
A separate module automates recurring delivery purchases in NSE stocks you approve, on its own thread so it cannot delay the options engine.
- Fixed-rupee weekly plans, placed in orderly Monday time slots
- Whole shares only, with any leftover amount carried forward
- Ledger with invested amount, holdings and XIRR
- Regular comparison with broker holdings, with differences shown
- Stock portfolio card, with a family view for the superuser
Running it as a business
Billing for fleets.
For a superuser who charges for managed accounts, billing is built into the same dashboard.
- Monthly invoices per account, with HTML and PDF copies
- Company and customer details managed on screen
- Payment receipts and manual reconciliation against the bank
- Overdue alerts and a yearly records reminder
- Annual reports for the superuser and for each account
- Full backup, then guarded removal of old years from the server
Instruments
Nine instrument cycles across NSE and BSE derivatives.
Each one stays off until you approve it. Liquidity varies a lot across monthly contracts, so check it for yourself before you approve any of them.
| Instrument | Exchange | Group | Expiry traded |
|---|---|---|---|
| NIFTY | NFO | Weekly | Nearest expiry |
| SENSEX | BFO | Weekly | Nearest expiry |
| NIFTY (M) | NFO | Monthly | Last expiry of the month |
| SENSEX (M) | BFO | Monthly | Last expiry of the month |
| BANKNIFTY | NFO | Monthly | Nearest listed expiry |
| BANKEX | BFO | Monthly | Nearest listed expiry |
| FINNIFTY | NFO | Monthly | Nearest listed expiry |
| MIDCPNIFTY | NFO | Monthly | Nearest listed expiry |
| NIFTYNXT50 | NFO | Monthly | Nearest listed expiry |
Release discipline
Every version is tested before it reaches a server.
Each release is versioned and carries an upgrade runbook, checksums and a dry run against copies of live files.
Results from one platform release, tested against a simulated broker. Simulated tests reduce software risk. They do not predict live market behaviour or trading results.
Technology
Request a callback
Your rules can be built on the same foundations.
Options, futures or stocks, on common or custom indicators: tell us how you trade, and we will show you which parts of this platform apply and what would be built new.
Or reach us directly: +91 74174 54940 info@dhruti.co.in