TalgorSB
Request a demo

TalgorSB · Desktop options trading

Options strategies, executed like infrastructure.

Build multi-leg options strategies visually. Run them live under a risk engine that watches every leg and the whole book. Operate a fleet from one console. Every release is certified against scripted markets first.

Interactive Brokers · Zerodha Paper + simulated brokerage SPX · NDX · SPY · QQQ · ES · CL · NIFTY
Request a demo Explore the suite
The Live Execution strip A running session panel. Five cells show cycle profit and loss, the overall stop loss with its re-entry counter, the overall target profit with its counter, lock-and-trail armed with its counter, and the exit time. Below, the mark price of the package the session sold at 9.28, drifting below that opening line as the position gains. Then a combo band showing net bid, mid and ask with the price currently being worked down toward the bid, the spread and its gate. A footer row carries pause, resume and liquidate controls and the graded error counts. LIVE EXECUTION SPX · SHORT IRON CONDOR · 4 LEGS · IBKR CLOCK 12:40:58 12:41:00 12:41:02 12:41:04 CYCLE P&L $ -84.20 $ -31.60 $ +47.90 $ +112.35 CYCLE 3 · OPEN OSL · OVERALL STOP $ -1,200 RE 1/3 OTP · OVERALL TARGET $ +2,400 RE 0/2 LOCK-TRAIL ARMED RE 0/1 ETR · EXIT TIME 15:55 SQUARE-OFF PACKAGE MARK · 09:35 → 12:41 SOLD OPEN 9.28 COMBO NET BID 9.20 MID 9.35 ASK 9.50 WORKING 9.35 9.31 9.27 9.23 SPREAD 0.30 · GATE ≤ 0.40 · PASS PAUSE RESUME LIQUIDATE CRITICAL 0 · ERROR 0 · WARNING 1 · INFO 12
Product visualization — the Live Execution strip, as it reads while a session runs.

01 / The suite

Six parts, built as one system.

Build a strategy, test it over history, certify the software before it ships, run the fleet, read every session back.

TalgorSB Platform

Multi-leg options, without code.

Design the strategy; a risk engine runs it live in your own account.

  • Legs, strikes, expiries and lots, set visually.
  • Per-leg and overall stops, targets and trailing.
  • Overnight strategies; sessions resume after a restart.

Backtest suites

One strategy, every version of it.

Give the parameters you want to test more than one value and run every combination.

  • Cases run in parallel; long tests split by month.
  • One comparison workbook per run, sortable.
  • Around 120 metrics per case.

SPT Certification

Rehearsal, not backtest.

Every release certified by the same code that trades.

  • Real engine against scripted price scenarios.
  • Machine-checked PASS or FAIL.
  • CI tiers from smoke to weekly.

Remote Launcher

A fleet from one console.

Built for tens of machines and hundreds of sessions a day.

  • Planner schedules rollouts with readiness checks.
  • Live fleet view with per-session drill-down.
  • Performance workbooks and an issues report.

Session Analyser

Every session, readable end to end.

Leg by leg, event by event — live or after the close.

  • Leg-wise P&L with entry and exit markers.
  • Momentum hunt targets where the strategy waited.
  • Option chain at any event on the chart.

Operations backbone

Install, roll back, explain.

Every machine on a known version, every error explained.

  • Install or roll back from inside the app.
  • The installer removes old versions itself.
  • Graded errors; every defect reference opens a card.

02 / Build

Draw the strategy. Skip the code.

A strategy is a set of legs: pick the underlying and the expiry, then set each leg's strike or offset, its lots and its protection. Save it, export it, move it between machines.

  • Legs, strikes, offsets, expiries, lots per leg — all configured visually.
  • Entry styles — scheduled times, momentum hunts that wait for direction, staggered re-entries.
  • Per-leg protection — Stop Loss, Take Profit and Trailing SL, enforced all session.
  • Overnight (BTST) strategies alongside intraday, with a timed square-off rule.
Four legs around the spot price A strike ladder for an SPX short iron condor. A vertical axis carries four legs at their strikes, highest at the top: a bought call wing at 6065 and a bought put wing at 5570 on the outside, drawn as faint dashed rungs; a sold call at 5915 and a sold put at 5720 on the inside, drawn solid. Between the two sold legs an amber dashed line marks the underlying at 5820. The sold legs sit inside the spot, the bought wings outside them. SPX · SHORT IRON CONDOR BUY CALL 6065 SELL CALL 5915 SPOT 5820 SELL PUT 5720 BUY PUT 5570 SOLD INSIDE · BOUGHT WINGS OUTSIDE
The strategy builder A four-leg short SPX iron condor laid out as rows: sell call and sell put at forty delta offsets, each carrying two lots with a stop loss percent, a take profit percent and a trailing stop; then buy call and buy put wings a hundred and fifty points out, two lots each and no per-leg protection of their own. Chips at the top set a weekly expiry, an entry time of 09:35 Eastern and momentum hunt on. A footer states the entry style, the re-entry budget, the square-off time and overnight availability. STRATEGY BUILDER SPX · SHORT IRON CONDOR WEEKLY (FRI) ENTRY 09:35 ET MOMENTUM HUNT LEG SIDE TYPE STRIKE / OFFSET LOTS SL % TP % TRAILING SL L1 SELL CALL +40Δ → 5915 2 35% 60% ON · 15% L2 SELL PUT -40Δ → 5720 2 35% 60% ON · 15% L3 BUY CALL +150 PTS → 6065 WING 2 — — — L4 BUY PUT -150 PTS → 5570 WING 2 — — — ENTRY STYLE SCHEDULED + MOMENTUM RE-ENTRY BUDGET OSL 3 · OTP 2 EXIT SQUARE-OFF 15:55 ET OVERNIGHT BTST AVAILABLE
Product visualization — a four-leg strategy as it is configured, not coded.

03 / Backtest

Test the strategy. Then test every version of it.

Run a strategy over history from the Backtest tab, or headless from a command line. Give the parameters you want to test more than one value and TalgorSB generates and runs every combination — a search of a strategy's parameter space.

  • Sweep what you choose to vary — strikes, stops, targets, re-entries, entry and exit times.
  • Runs in parallel — across workers, with long tests split by month and merged back.
  • One comparison workbook per run — a row per case, sortable in the app.
  • Around 120 metrics per case — including the exit reason behind every trade.

The backtest runs the same strategy code that trades. Same risk manager, same leg selection, same parameter file — so a strategy moves from the Backtest tab to the Live tab unchanged.

A backtest is not a certification. It asks how a set of parameters would have behaved over history; SPT asks whether the software itself is correct.

You supply the market data. TalgorSB reads a 1-minute bar folder you provide, and backtest P&L is gross — fees and slippage are applied afterwards, in the Analysis tab.

One base strategy expanded into its parameter space On the left, a single box labelled BASE: one strategy. Four lines fan out from it into a lattice of twelve by twelve cells on the right — a hundred and forty-four generated cases, one per combination of the parameter values chosen to vary. Four cells are lit in amber, cases finishing across the sweep. PARAMETER SPACE BASE 1 STRATEGY 144 CASES EVERY COMBINATION, RUN
A bulk backtest comparison The result table for one generated suite: a hundred and forty-four cases produced from a single SPX short iron condor and run over the twelve months of 2025. The six strongest cases of the run are shown, sorted by net profit and loss; the table sorts on any column and a row click opens that case's full analysis. Every row is named from the parameters that vary in it — entry time, exit time, overall stop, overall target, lock-and-trail and re-entry count — and carries net profit and loss, Sharpe, Sortino, maximum drawdown, win rate, profit factor and trade count. The strongest case is highlighted; the last case lost money. The footer notes that each case was split into twelve monthly tasks, run in parallel over a shared data cache and merged into one result folder, and that the comparison exports to Excel. BACKTEST COMPARISON SUITE  SPX_SHORT_IC 144 CASES · 2025-01 → 2025-12 SORTS ON ANY COLUMN · A ROW CLICK OPENS THAT CASE'S FULL ANALYSIS TOP 6 OF 144 · SORTED BY NET P&L TEST CASE NET P&L SHARPE SORTINO MAX DD WIN % PF TRADES ET0935_OSL40_OTP60_RE2 $ +18,420 1.42 2.06 -6,180 64.8 1.71 248 ET0935_OSL30_OTP60_RE2 $ +12,905 1.18 1.63 -5,240 61.2 1.48 251 ET0935_OSL40_OTP60_RE1 $ +9,640 0.97 1.32 -5,910 59.4 1.36 186 ET0945_OSL40_OLAT25_RE2 $ +6,215 0.71 0.94 -7,430 57.0 1.21 244 ET0935_OSL50_OTP80_RE1 $ +1,480 0.22 0.29 -9,860 52.6 1.05 190 ET0945_Ext1530_OSL30_RE0 $ -3,270 -0.31 -0.40 -11,240 48.1 0.88 122 EACH CASE SPLIT INTO 12 MONTHLY TASKS · RUN IN PARALLEL · MERGED INTO ONE RESULT FOLDER SHARED DATA CACHE NAMES CARRY THE PARAMETERS THAT VARY · ET · EXT · OSL · OTP · OLAT · RE COMPARISON → EXCEL
Product visualization — one generated suite, compared case by case; every name carries its own parameters.

04 / Certify

The code that trades is the code under test.

SPT — Simulated Paper Test — boots the real engine and the real algorithm in live mode against a simulated brokerage fed scripted prices, and returns a machine-checked PASS / FAIL report. Every release passes it before shipping.

  • Scenario suites cover entries, stops, targets, re-entries, square-offs and overnight cycles.
  • CI tiers run continuously — smoke, hourly, daily, weekly.
  • SPT Studio — a desktop GUI to build suites, watch runs, explore results.
  • Weekend-proof — the simulated brokerage trades outside market hours.
Scenarios converging on one release gate Six scenario tracks on the left converge into a single amber-outlined gate carrying a check mark. One output leaves the gate to the right, into a box reading SHIP. A second, dashed, drops from the bottom of the gate into a box reading HELD. Any failing scenario holds the release, and the verdict is machine-checked. SCENARIO SUITE SHIP HELD ANY FAIL HOLDS THE RELEASE VERDICT IS MACHINE-CHECKED
The SPT certification pipeline Five stages left to right, connected by a flow line along which markers travel. One, the suite: scenarios for entries, stops, targets, re-entries, square-offs and overnight cycles. Two, scripted prices: a compiled price series per scenario. Three, the live-mode run, highlighted as the core stage: the real engine and the real algorithm running headless, several sessions in parallel, with the external services replaced by local stubs. Four, the simulated broker, which fills the orders and gives each test its own exchange. Five, the verifier, which machine-checks the event sequence and writes a verdict. Beneath the five stages a release gate states that no release ships until every scenario passes, and that a finished run can be re-verified without being run again. SPT CERTIFICATION PIPELINE EVERY RELEASE PASSES THROUGH IT SMOKE · HOURLY · DAILY · WEEKLY 01 SUITE SCENARIOS YOU DEFINE ONCE 02 PRICES A SCRIPTED SERIES PER SCENARIO 03 LIVE-MODE RUN REAL ENGINE, REAL ALGORITHM, HEADLESS 04 SIMULATED BROKER FILLS THE ORDERS, ONE PER TEST 05 VERIFIER CHECKS THE EVENT SEQUENCE, NOT THE P&L IN PARALLEL EXTERNAL SERVICES REPLACED BY LOCAL STUBS RELEASE GATE No release ships until every scenario passes — and the verdict is machine-checked, not read. A FINISHED RUN CAN BE RE-VERIFIED WITHOUT BEING RUN AGAIN SPT STUDIO · BUILD, WATCH, EXPLORE
Process visualization — the same code that trades, run against scripted markets, judged by machine before a release ships.
An SPT certification report A certification table with columns scenario, sessions, duration and verdict. Six scenario rows — scheduled entry, momentum hunt entry, per-leg stop and target, overall stop, target and lock-and-trail, timed square-off, and an overnight cycle — each carrying a green PASS badge. The square-off row is expanded to show the scripted price series that drove it. The footer reads six of six PASS, machine-checked. SPT CERTIFICATION REPORT SUITE  SPT_REGRESSION_DAILY MACHINE-CHECKED SCENARIO SESSIONS DURATION VERDICT ENTRY · SCHEDULED 09:35 3 04:12 PASS ENTRY · MOMENTUM HUNT 4 05:38 PASS RISK · PER-LEG SL / TP / TRAIL 4 06:01 PASS RISK · OSL / OTP / LOCK-TRAIL 3 05:20 PASS EXIT · TIMED SQUARE-OFF 2 03:44 PASS SCRIPTED PRICE SERIES · SPX WEEKLY · 1M BARS 15:55 ETR ENTRY 09:35:00 · 4 LEGS FILLED PEAK CYCLE P&L  $ +1,860 FLAT AT 15:55:04 · 0 LEGS OPEN OVERNIGHT · BTST CYCLE 2 08:26 PASS SUITE  6/6 PASS  · MACHINE-CHECKED WEEKEND-PROOF · SIMULATED BROKERAGE TRADES OUTSIDE MARKET HOURS
Product visualization — a certification report; the release is gated on it.

05 / Execute

A risk engine that acts. Orders that arrive as one package.

Risk is enforced at two levels: each leg carries its own Stop Loss, Take Profit and Trailing SL, while Overall Stop Loss, Overall Target Profit and Lock-and-Trail hold the whole book, with a timed square-off underneath.

  • Re-entry budgets per criterion, counted live on the strip as RE used / max.
  • Atomic multi-leg orders on Interactive Brokers — one package, not four races.
  • Execution quality — live package Net Bid / Mid / Ask, and a spread gate.
  • Ladder modes — auto, patient or cross, working the entry toward marketable.

Exits never ladder. Every exit takes the direct marketable path — never gated, never worked.

Four legs sent as one package Four leg boxes on the left — sell call, sell put, buy call, buy put — feed along dashed lines into a single amber-edged block on the right labelled atomic package, carrying the package net price of 9.35. One arrow leaves the block for Interactive Brokers: one order, not four. Exits take the direct path. FOUR LEGS · ONE ORDER SELL CALL SELL PUT BUY CALL BUY PUT ATOMIC PACKAGE NET 9.35 IBKR · ONE ORDER EXITS TAKE THE DIRECT PATH
The combo execution band A package price scale from net bid 9.20 through net mid 9.35 to net ask 9.50, with the spread of 0.30 bracketed above it and a spread gate of 0.40 marked as passed. Below, the price ladder in auto mode sells the package: it starts at mid 9.35 and walks down through 9.31 and 9.27 to 9.23, close to the bid, where it becomes marketable and fills. A footer notes that exits always take the direct marketable path. COMBO EXECUTION IBKR · 4-LEG PACKAGE · ONE ATOMIC ORDER AUTO PATIENT CROSS PACKAGE NET SPREAD 0.30 NET BID NET MID NET ASK 9.20 9.35 9.50 SPREAD GATE ≤ 0.40 · PASS PRICE LADDER · SELL · MID → BID 9.20 BID 9.50 ASK 09:35:02 9.35 WORKING · MID 09:35:20 9.31 RE-PRICE 1 09:35:38 9.27 RE-PRICE 2 09:35:56 9.23 MARKETABLE · FILLED EXITS ALWAYS TAKE THE DIRECT MARKETABLE PATH — NEVER LADDERED, NEVER GATED. DECISION LOG PER SESSION
Product visualization — one entry, worked from mid to marketable, logged step by step.

06 / Operate

Built for tens of machines. Hundreds of sessions. One console.

Remote Launcher dispatches, monitors and controls trading sessions across a fleet. Every run produces two documents for two audiences: a performance workbook for the desk, and an issues report for whoever has to act.

  • Live fleet view — status, P&L, graded errors and execution quality, per session.
  • Planner — schedule a rollout days ahead, with readiness checks: machine online, capacity, sanity.
  • Fleet performance workbook — every session's P&L, margin and fees, subtotalled by machine and strategy.
  • Issues report — findings graded high, medium and low, each with evidence and an action.

Reports state their own coverage. A fleet health report says how many sessions it actually read, and flags closed sessions still holding positions.

One console over a fleet of machines A single amber-edged console box at the top drops onto a bus that branches to five machine nodes. Under each node a row of small marks stands for its running sessions — six, five, four, eight and one. The fourth node is drawn in amber: it is the one at capacity. Beneath the fleet, the run splits into the two documents it produces — a performance workbook and an issues report — on demand or on a schedule. REMOTE LAUNCHER CONSOLE N01 N02 N03 N04 N05 5 MACHINES · 24 SESSIONS PERFORMANCE WORKBOOK ISSUES REPORT ON DEMAND OR ON A SCHEDULE
The Remote Launcher fleet console On the left, five machines with status dots and session counts, and a coverage block stating twenty-four of twenty-four sessions read with no closed sessions holding positions. On the right, a grid of twelve live session chips with their profit and loss, one flagged with a warning dot, and a planner card scheduling strategy T63 across three machines with a 09:35 entry and all readiness checks green. REMOTE LAUNCHER · FLEET 5 MACHINES · 24 SESSIONS WINDOWS 09:35–15:55 ET · 09:20–15:20 IST MACHINES TSB-NODE-01 6 SESSIONS · READY TSB-NODE-02 5 SESSIONS · READY TSB-NODE-03 4 SESSIONS · READY TSB-NODE-04 8 SESSIONS · AT CAPACITY TSB-NODE-05 1 SESSION · READY COVERAGE 24 / 24 SESSIONS READ 0 CLOSED SESSIONS HOLDING POSITIONS SESSIONS RUNNING WARNING SPX-IC-01 +112.35 SPX-IC-02 +188.20 NDX-BF-01 -96.40 SPY-CS-01 +240.10 QQQ-CS-01 +64.75 ES-IC-01 +512.00 CL-STR-01 -142.30 NIFTY-IC-1 +318.60 NIFTY-IC-2 +96.15 SPX-OVN-01 +720.40 NDX-BF-02 -58.90 SPY-CS-02 +134.05 PLANNER · SCHEDULED ROLLOUT T63 · 3 MACHINES · 09:35 ENTRY · 15:55 EXIT ✓ MACHINES ONLINE ✓ CAPACITY ✓ SANITY READY
Product visualization — the fleet view, with the planner staging tomorrow's rollout.

07 / Analyse

Read the session back, leg by leg.

The Session Analyser charts a session while it runs and after it closes. Nothing is inferred after the fact: every session leaves a complete forensic folder behind it — engine log, trade log, order events, parameters.

  • Leg-wise P&L and price paths with entry and exit markers on one timeline.
  • Momentum hunt targets drawn where the strategy was waiting for direction.
  • Option-chain snapshot at any event on the chart.
  • An analysis window, not a report — Excel export belongs to the live views.
One event, read across every leg Two leg traces run across one timeline from an entry marker at 09:47 to an exit marker at 15:52. A single amber probe stands at 12:32, marking where it crosses each leg. Below a rule, the four files every session leaves behind: engine log, trade log, order events and parameters. SESSION READ-BACK P&L 12:32 LEG 1 LEG 2 ENTRY 09:47 EXIT 15:52 SESSION FOLDER ENGINE LOG TRADE LOG ORDER EVENTS PARAMETERS
A Session Analyser chart A leg-wise profit and loss chart across a trading day. Two lines track the short call and short put legs from the 09:47 entry marker to the exit at 15:52, three minutes before the square-off time, where Overall Lock-and-Trail closed the session. Gridlines sit at plus two thousand, plus one thousand, zero and minus one thousand. A dashed amber line marks the overall target profit at plus two thousand four hundred, which the session never reaches. A footer band shows the option-chain snapshot captured at 12:32. SESSION ANALYSER LEG-WISE P&L SPX · SESSION 4812 · WEEKLY LEG 1 · SHORT CALL 5915 LEG 2 · SHORT PUT 5720 ENTRY EXIT OTP TARGET $ +2,400 +2,000 +1,000 0 -1,000 OTP $ +2,400 09:47 ENTRY 15:52 EXIT · LOCK-TRAIL 09:35 11:00 12:30 14:00 15:30 15:55 OPTION CHAIN @ 12:32:04 5865 C 42.30 5890 C 30.10 5915 C 19.10 5940 C 10.10 SNAPSHOT AT ANY EVENT ON THE CHART · MID-SESSION OR AFTER THE CLOSE
Product visualization — one session, read back leg by leg with the chain at any event.

Rigour / How it is built

Software that trades money must not guess.

The differentiator is not a feature; it is what happens after something goes wrong. Every field incident gets a root-cause analysis, golden-file tests hold the strategy engine's behaviour, and releases are gated on SPT certification.

Live and paper execution runs on LEAN, the open-source institutional trading engine, hardened and extended by Creative Mindze for options execution.

“We publish what broke and why to our operators. Our reports state their own coverage. Software that trades money must not guess.”

Creative Mindze · engineering practice

Defect register

Every field incident gets a root-cause analysis; the fix ships with a regression test pinned to the code that failed.

Golden-file regression

On the strategy engine, the recorded behaviour is the specification: drift is a failing test.

Coverage-honest reporting

Fleet reports state how many sessions they actually read. No green all-clear over a blind spot.

Demo / Contact

See it run on a live market.

The honest way to evaluate trading software is to watch it work. Write to us and we will walk you through a session end to end.

Request a demo Ask a question

Talgor's original line: “Trade complex strategies, for assets you understand, in markets you like, with brokers you prefer.”

Registered office

Creative Mindze Technologies Private Limited
1010, B Wing, Mittal Tower
6 MG Road, Bangalore – 560001
India
contactus@talgor.com