01 / Broker terminals
Every trader becomes the risk system.
Entries, exits and limits depend on fast clicks and individual discipline. Slippage, missed exits and inconsistent decisions become desk-level problems.
FOR NSE F&O PROP DESKS
Run every options trade inside the desk’s limits.
Take strategies from minute-level backtests to paper trading and live execution, with risk limits checked before every order. Privately deployed in about a week; traded daily with the builder’s own real capital.
Request a 30-minute demo
rehan@gammarails.com
If it fits: paper-trading pilot before any license discussion.
01Trades the builder’s own real capital daily
0250+ strategies in the backtest library
03Risk checks before every order
04Private deployment in about a week
The desk today
Manual clicks, brittle scripts, or another seat license.
The order window is rarely the missing piece. The gap is one route from research to execution, with the desk’s discipline and records built in.
02 / Broker scripts
The script is only the first bill.
Static IPs, dead sessions, re-logins, strategy registration and years of records turn a small script into permanent operating work.
03 / Dealer terminals
Execution stays separate from research.
Per-seat terminals put orders into the market, but the backtest, paper run, live trade and journal remain separate workflows.
01 Risk rails
A junior trader cannot trade past the desk’s limits.
Set the day’s boundaries before the session. GammaRails checks them where execution happens, so discipline does not depend on a rulebook or a calm reaction mid-trade.
- Daily loss caps
- Max-trade caps
- Master kill switch
- Intraday auto-close
- Trailing SL with break-even locks
02 Positions & orders
Every exit already has its explanation.
Manage risk per leg or across the index while a trade is open. Every order is tagged, every fill is journaled, and the exit reason stays with the trade. The resulting history is built for five-year recordkeeping.
- Live SL/TP on every leg
- Index-level SL/TP
- Tagged orders and fills
- Entry, exit and exit reason
03 Research & accounting
The route from backtest to books stays intact.
Test on minute-level history, watch the strategy in paper, then run it live. Broker-reported P&L, charges and the trade journal close the loop after execution.
- 50+ backtest strategies
- Paper trading with live MTM
- Broker P&L net of charges
- Complete trade journal
Full desk inventory
One operating surface. Four desk jobs.
Research, execution, automation and records stay in the same private deployment.
01 / Trade
Trade
- Live execution engine
- One-click ATM options desk (Quick Trade)
- Live positions
- Per-leg stop-loss and take-profit
- Index-level stop-loss and take-profit
- Trailing stop-loss with break-even locks
- Order management with exit reasons
- Daily loss caps and trade caps
- Kill switch and intraday auto-close
02 / Analyze
Analyze
- Backtest engine with 50+ strategies
- Minute-level historical data
- Paper trading with live MTM
- Live and historical option chains
- Trending open interest
- Open-interest movers
- Implied-volatility charts
- Candlestick and minute-level charts
- Watchlists
03 / Automate
Automate
- Per-symbol strategy configuration
- Price and open-interest alerts
- Notification routing
- Signal ingestion
- Telegram signal parsing into structured trades
- Webhooks
- Historical data backfill tools
04 / Account for
Account for
- Trade journal
- Broker-reported P&L net of charges
- Tagged order and fill history
- Entry, exit and exit-reason records
Build or deploy
An internal build starts a year before the first live trade.
A backtest-to-live desk takes 12–18 months, 2–3 engineers and ₹50 lakh+ in salaries before it trades live. That is before the ongoing work around broker sessions, data and records.
- 12–18
- months
- 2–3
- engineers
- ₹50L+
- salaries before live
GammaRails goes onto your infrastructure in about a week. The system already trades its builder’s real capital daily, and you have one person to call.
Operating model
How your desk runs it
-
01
Backtest the strategy
Run it across minute-level history and configure it per symbol.
-
02
Prove it in paper
Watch live MTM, positions, exits and desk limits before live capital is involved.
-
03
Deploy it privately
Run on your infrastructure, in your broker account, with your data.
-
04
Trade inside the rails
Move live with loss caps, trade caps, the kill switch and intraday auto-close already in place.
Before the walkthrough
Six direct answers.
Where does it run?
On your servers or cloud as a private deployment. Your trading setup and data stay with your desk.
Which broker and data feed?
GammaRails connects to your broker account. The Upstox connection is included today; other broker connections are scoped separately. The data-feed layer has already been moved between vendors.
What exactly do we get?
The full platform: backtests, paper and live execution, Quick Trade, risk rails, option-chain and open-interest analytics, alerts, signal ingestion, reports, journal and installation support.
How long does deployment take?
About a week for the private deployment. Broker or data-feed connection work outside the included setup is scoped separately.
Who built this?
A solo engineer who trades it live with his own capital every trading day. You speak directly with the person who wrote and runs it.
What happens after the demo?
If the fit is clear, the next step is a paper-trading pilot on your account. You see live MTM, positions and risk rails before any live capital or license discussion.
30 minutes on the live platform
See the full route from backtest to live.
See the desk, the risk checks and the audit trail. If it fits, the next step is a paper-trading pilot before any license discussion.