APEX v1.24.0  ·  Omega v1.102.3  ·  released 16 Sep 2026

Eight brokers. One desk. Nothing leaves your machine.

APEX and Omega are Windows trading terminals for the Indian markets. You connect your own broker API key and every order executes in your own demat account — the broker is a plug-in, not the product. Zero runtime dependencies, credentials AES-256-GCM encrypted on disk, and a server that binds to 127.0.0.1 and nowhere else.

Windows 10 / 11 · 64-bit Portable — no installer No account, no telemetry Which one do I need?

Brokers
8
Runtime deps
0
Binds to
127.0.0.1
Test checks
3,658
Instruments
1.79 lakh
Order gate
10/sec

Two terminals

One of them is the desk you already know. The other automates it.

Omega is the manual terminal. APEX is a copy of Omega taken at v1.95.0 with a full strategy builder and execution engine added on top. They share a core, a look and a keyboard — and they install side by side without touching each other.

Omega Terminal

The manual desk

A Symphony XTS-style manual trading terminal. Watchlists, tickets, option chain, books, baskets, alerts and PANIC — fast, smooth and entirely keyboard-driven. If you trade by hand and want the terminal to get out of the way, this is the one.

  • Market Depth window — a five-level ladder with order counts, plus a full snap-quote grid. Only in Omega.
  • Every login live at once with its own books, risk limits and halt switch
  • Option chain with an anchored ATM ladder and one-click marketable limits
  • Baskets, alerts, charges and net P&L, xlsx/CSV export from every book
  • 17 floating windows, each detachable to a second monitor
Version 1.102.3 Port 7810 Tests 89 suites / 3,409

Adds automation

APEX Terminal

The automated desk

Everything Omega does, plus a visual multi-leg strategy builder, an Advanced Scalper, a deployed-run monitor and an append-only journal. Strategies are evaluated on the tick, not on a poll — inside the same function that ingests the quote.

  • Strategy builder — up to 40 legs, per-leg target/SL/trailing, action chains, re-entry
  • Advanced Scalper — Classic, Grid and Ladder modes with per-lot risk management
  • Ranked order lanes and pushed fills — exits jump the queue, fills arrive by websocket
  • Per-day NDJSON journal with a CSV export of every entry, exit, target and stop
  • Auto Login — scheduled broker sign-in, and a Windows task that opens the desk itself
Version 1.24.0 Port 7811 Tests 92 suites / 3,658

You can install both. They use different ports (7810 and 7811) and different data folders (%APPDATA%\Omega Terminal and %APPDATA%\APEX Terminal), so neither can see the other's vault, layout or positions. Running one has no effect on the other.

Side by side

What is actually different

Everything not listed here is the same in both: the engine, the brokers, the option chain, the books, the risk manager, the keyboard map and the look.

Feature comparison — Omega Terminal v1.102.3 against APEX Terminal v1.24.0
Capability Omega APEX
Manual trading — ticket, chain, basket, books, PANIC Yes Yes
Multi-leg strategy builder & execution engine None Up to 40 legs, 7 strike-selection methods
Advanced Scalper None Classic / Grid / Ladder
Deployed-run monitor & per-day journal None NDJSON + CSV export
Order fill confirmation Polled — the order book is re-read at 150 / 300 / 500 / 800 ms Pushed over websocket on Kotak Neo and XTS
Ranked execution lanes Priority insert ahead of polling Six ranked lanes — exits jump every other order
Protective stops SL-M, which some brokers refuse outright Always a stop-LIMIT, accepted everywhere
Auto Login & Windows auto-launch None Scheduled per account
Market Depth window Five-level ladder + snap quote Removed — it duplicated Quick Trade
Floating windows / modals 17 windows 19 windows, 22 modals
Internal port · data folder 7810 · %APPDATA%\Omega Terminal 7811 · %APPDATA%\APEX Terminal
Test gate 89 suites · 3,409 checks 92 suites · 3,658 checks

Scroll the table sideways to see both columns.

Under the hood

Built by someone who got burned, and wrote the rule down

Every guard in these terminals exists because something went wrong on a live desk once. The changelog transcribes measured failures into tests rather than inventing them.

Both terminals

Every login signed in at once

Connecting a second broker does not touch the first. Switching between accounts is a click on the account strip — not a fresh login, and never another TOTP.

  • Each account owns its books, quote cache, candles, scrip index, feed health, risk limits and timers. The account on screen polls at full cadence; the others poll at half rate.
  • An order can name the account it belongs to, so you can trade one login while looking at another.
  • The Desk — All Accounts window nets identical instruments across logins. A long on one account and a short on another is flat in risk and flat at neither broker — the row still names its constituents.
  • Every money route is pinned to the account you are looking at; a pin to a dropped account is refused by name, never re-routed.

"A refusal the trader can read beats an order on an account they did not choose."

Desk — All Accounts

KOTAK NEO · PROP1+12,480
XTS · JAINAM−3,120
ZERODHA · HEDGE+1,845
PAPER simulator+640
↓  netted across accounts
NIFTY 24800 CE ×2 accountsNET 0
TOTAL excl. simulators+11,205

APEX

One gate, ten orders a second, ranked lanes

Every order, modify and cancel from every window goes through one per-broker queue. When a burst goes out, the order of the queue is the order that keeps you safe.

  • Exits are lane 0 — a square-off jumps every entry, stop and target already waiting.
  • Fills are pushed over the broker's order websocket and polled only as a fallback. Confirming by re-reading the book used to cost one to three seconds per fill.
  • Orders over the exchange freeze quantity are sliced into whole lots automatically, and an exit is sliced whether or not auto-slice is switched on.
  • A per-order value cap that no instrument master publishes is learned from the exchange's own rejection text and the order re-sent, sliced 2% under it.

Order lanes — lower number goes first

0EXIT
1ENTRY
2STOP
3TARGET
5READ
9POLL

 

Confirmation burst0 · 120 · 370 · 870 · 1870 ms
Bulk sweep10 orders / second

APEX

Strategies decided on the tick, not on a poll

Target, stop, trailing stop, wait-and-trade and portfolio rupee rules are all evaluated inside the same function that ingests the quote. There is no separate loop and no lag between the price moving and the decision being made.

  • Strike selection by ATM, ITM, OTM, Manual, Delta, IV or closest premium, resolved against the instrument master already in memory — no network call at all.
  • Twelve leg actions — square off, move stop to cost, re-entry, re-execute, pyramiding, reverse position, square off a linked leg. One strategy can start or stop another.
  • Broker protect rests the stop and target as real broker orders, so they fire even with APEX closed, with the terminal emulating OCO by cancelling the sibling.
  • On restart, every entered leg is reconciled against the broker's own position book — nothing is ever re-entered on a guess.
  • Deploy one strategy across several accounts with per-account quantity multipliers; one account refusing leaves the others exactly as they would have been.
Deployed Strategies Pause AllSquare Off All
Illustration of the Deployed Strategies window
StrategyStateLegsMTM
Short Straddle 9:20RUNNING2 in · 0 wait+4,280
Iron Condor CWRUNNING4 in · 0 wait−1,140
BNF Ratio 1:214:20:000 in · 3 wait
Scalper — GridRUNNING1 in · 0 wait+2,865
Expiry FlySQUARED OFF0 in · 0 wait+3,355

Both terminals

Thirteen checks before anything reaches a broker

Every order — manual, basket, chain or strategy — passes the same risk manager. A strategy is never a way around a guard.

  • The price band is measured against the live book, not LTP alone. A marketable price scores zero, because crossing the spread is how you get filled — while 1420 typed as 14200 is still 900% away.
  • Exits are exempt from every entry-side guard. A halt must never trap you inside the position it is protecting you from.
  • NO NEW ENTRIES stops opening and keeps managing, per account, and survives a reconnect and a restart. It is not PANIC — nothing is squared off.
  • PANIC cancels everything and squares off — on the account it names. With an unreadable position book it refuses loudly and tells you to flatten from the broker's app, because an empty list is "unknown", never "flat".
  • A daily loss limit halts the account automatically, and still lets every exit through.

"Never lie to the desk. A failed book must not look like a flat account. An 'unknown' is never printed as 0.00."

RiskManager.check() — order of evaluation

0 · account haltedexit passes
1–2 · quantity positive and wholealways
3 · max quantity per orderexit passes
4 · exchange allowedalways
5–6 · price / trigger presentalways
7 · notional value capexit passes
8 · price band vs live bookalways
9 · stop on the wrong sidealways
10 · orders per minuteexit passes
11 · open order countexit passes
12 · day loss kill switchexit passes

Both terminals

An option chain that holds still while you trade it

The at-the-money strike is recomputed on every tick in the browser using the same formulas the server used, so the two can never disagree. The ladder is anchored — it re-centres only when the ATM drifts into the outer margin, so a strike never slides out from under the pointer.

  • The money is read out of the options themselves by put-call parity on commodity and currency chains, and from the real cash spot on index and stock chains — with the source named in words.
  • A bare buy or sell sends a marketable limit: the touch padded 1.5% through and rounded outward onto a tick grid inferred from the book itself.
  • Right-click any strike to add a BUY or SELL leg straight to a basket — the chain is where a multi-leg spread is actually assembled.
  • The footer sums the whole ladder, not just the rows on screen, and shows relative difference to four decimals.
  • Keyboard over the ladder: arrows move, + buys, sells, Enter arms a ticket instead of firing.

Nothing is hardcoded to an exchange, tick or strike step

Strike count2 – 250
Stepsnapped to the ladder's own base step
ATM sourcespot, or implied forward by parity
Tick gridinferred from quoted prices (GCD)
Re-readevery tick, in the browser

Both terminals

Paper trading on real market data

The simulator borrows a live broker session: real instrument master, real prices, real depth, real lot and tick sizes, real freeze quantities. Only the execution is simulated — and it costs no extra broker quota.

  • A MARKET order walks the visible depth ladder. A LIMIT fills where the market traded through it and takes the improvement. Stops latch.
  • Slippage is structural, not a parameter. There is no slippage constant to tune until the backtest looks good.
  • Losing the live source is not a fallback to invented prices — the account goes quiet with everything intact and re-latches onto the next broker.
  • Every simulated order is logged with SIMULATOR (not sent to any exchange) beside it.

"A simulator that fills every size at the touch teaches a trader that size is free, which is an expensive lesson to unlearn on a real desk."

Also in both terminals

Charges & net P&Lbrokerage, STT, stamp, SEBI, GST
Basketsup to 50 legs, split equally by value
Alertsprice, P&L, position, margin, rejection
Auto square-offseveral timed rules per account
Export.xlsx and .csv from every book
Workspaceone code carries a desk between machines
Keyboardevery chord rebindable
Windowsdetachable to a second monitor

Broker-agnostic by construction

Eight adapters. One interface. Your API key.

No vendor field name leaks above the adapter layer — the terminal never knows whether your broker calls it tradingsymbol or trdSym. You need your own account with the broker and their API access enabled.

Paper Trading

simulator

Real market data, real fills, nothing sent to any exchange. Start here.

Needs
Nothing — one field for starting capital
No account neededOffline demo

Zerodha

Kite Connect v3

The terminal shows the login URL; you paste the request token back.

Needs
API key + secret + daily request token
Token
Expires next morning
Polled feedPosition convert

Angel One

SmartAPI

TOTP is asked at connect time and never stored.

Needs
API key + client code + MPIN + TOTP
Token
Daily
Polled feedPosition convert

Dhan

DhanHQ v2

The easiest live option — no daily login at all.

Needs
Client id + access token
Token
30 days
No daily loginPosition convert

Fyers

Fyers v3

App id and a daily access token from the Fyers dashboard.

Needs
App id + access token
Token
Daily
Polled feedPosition convert

Upstox

Upstox v2

A single access token, refreshed each morning.

Needs
Access token
Token
Expires daily at 3:30 am
Polled feedPosition convert

Kotak Neo

Trade API v2

Two-step sign-in. Binary HSM market feed and a websocket order feed.

Needs
Access token + mobile + UCC + TOTP + MPIN
Token
Daily
Push feedsFreeze qtyNo convert API

Symphony XTS

Interactive + Market Data

Two separate logins. Socket.IO price feed and order feed.

Needs
Base URL + both app keys
Token
Per session
Push feedsFreeze qtyPosition convert

The XTS adapter is wider than it looks. Symphony XTS is the platform behind IIFL, Jainam, Kotak XTS, Motilal XTS, Share India and most institutional white labels — so one adapter reaches far more than one broker. Point it at your provider's base URL and it works.

Broker-side prerequisites are yours to arrange. API trading needs your API subscription activated, TOTP enabled and an app created in the broker's own dashboard. Kotak Neo additionally requires your IP address whitelisted with Kotak before it will accept API orders.

Security & privacy

The only thing that leaves your machine is a call to your own broker

There is no account to create, no cloud to sign into and no server of ours in the path. The terminal is one process on your PC that talks to your broker's API and to nothing else.

Bound to 127.0.0.1 only

The address is hard-coded, never configurable, and never off-machine. A request arriving with an origin that is not loopback is refused with a 403 before it reaches any route.

AES-256-GCM credential vault

Credentials are encrypted at rest, and the key lives in a separate file beside the vault — so the vault alone is useless if it is copied off the machine.

TOTP codes are never stored

A typed six-digit code is dead in thirty seconds and is dropped immediately. Only a static setup key can be saved, and only encrypted, and only if you choose to.

Zero runtime dependencies

Nothing from npm runs in the shipped app. The WebSocket client, the AES vault, the TOTP generator, the Excel writer and the Black-Scholes maths are all written in-tree. There is no supply chain to compromise.

No CDN, no iframes, no external URLs

The interface loads nothing from the internet. The desktop host permits exactly one navigation — detaching a window to a second monitor — and denies everything else.

Secrets never reach a log or a screen

Access tokens, secrets and passwords are stripped from the session profile before it can be broadcast. Anything matching secret, token, password, pin or key is masked before it is written anywhere.

Your data stays where you put it. Watchlists, layouts, alerts, risk limits, strategies and the encrypted vault live in %APPDATA% on your own machine. Nothing is uploaded, and there is no telemetry — the only network traffic the app makes is to your broker's own REST and WebSocket endpoints.

Engineering

Tested like instrumentation, not like a website

Test gate

3,658

checks across 92 suites in APEX, 3,409 across 89 in Omega. Zero failures is the release condition — a version cannot ship red.

Browser suites

43

driving real headless Microsoft Edge over the Chrome DevTools Protocol. Real renderer, real mouse drags, real key events — not a mock DOM.

Book cycle

340ms → 0.2ms

after the instrument index was made lazy. Measured, recorded in the changelog, and locked behind a test.

DOM churn

2,655 → 0

nodes destroyed over fifteen seconds of live ticking. Tables are reconciled by row key, so selection, hover and scroll all survive.

P&L moves at tick rate, not at book rate. Open positions are re-marked from the quote cache on every incoming tick rather than waiting for the next three-second book refresh — so the number on screen is the number right now.

Download

One file. No installer. No account.

Each terminal is a single portable executable. Put it anywhere and run it — your data lives in %APPDATA%, so you can drop a newer build straight over the old one and keep every login, layout, strategy and journal entry.

APEX Terminal

Automated
Version
1.24.0
Size
Released
Platform
Windows x64
SHA-256
Published with each release

Windows 10 or 11 · 64-bit · portable, no installer

Omega Terminal

Manual
Version
1.102.3
Size
Released
Platform
Windows x64
SHA-256
Published with each release

Windows 10 or 11 · 64-bit · portable, no installer

1

Windows will warn you the first time. That is expected.

These builds are not code-signed, so Microsoft SmartScreen shows "Windows protected your PC" on first run. To continue, click More info, then Run anyway. You can verify the file you downloaded is the file we published using the checksum above before you do.

2

Verify the download

Open PowerShell in the folder you downloaded to and compare the result with the SHA-256 printed above.

Get-FileHash .\APEX-Terminal-1.24.0.exe -Algorithm SHA256
3

Run it, then connect a broker

Double-click the exe — there is no installer and no console window. Open Connection → Connect Broker and start with Paper Trading: it rides the live feed of whichever broker you connect, so everything you learn there transfers to a real account.

4

Updating

Close the terminal, drop the new exe over the old one, and open it again. Your vault, watchlists, window layout, risk limits, strategies and journal live in %APPDATA% and are untouched by the swap.

Questions

Before you download

Which terminal should I download?

Omega if you trade by hand and want the fastest possible manual desk — and if you want the Market Depth window, which only Omega has.

APEX if you want to build multi-leg option strategies and have them executed for you, or if you want the Advanced Scalper, the journal, Auto Login and websocket order feeds. APEX contains everything Omega does apart from Market Depth.

If you are unsure, take APEX — it is the superset. You can always install both.

Do I need a broker account?

To trade live, yes — your own account with one of the eight supported brokers, with API access enabled. That usually means an API subscription activated, TOTP enabled and an app created in the broker's dashboard. Kotak Neo also requires your IP address whitelisted with Kotak before it will accept API orders.

To explore the terminal, no. The Paper Trading broker needs nothing at all, and its offline demo mode runs with no account whatsoever.

Is any of my data sent anywhere?

No. The terminal runs a server on your own machine bound to 127.0.0.1, which means it is not reachable from your network let alone the internet. The only outbound traffic it makes is to your broker's own REST and WebSocket endpoints, using your own API key.

There is no account, no sign-up, no analytics and no telemetry. Your credentials are AES-256-GCM encrypted in a vault on your disk, with the key in a separate file, and they never travel.

Is there a Mac or Linux build?

Not currently. Both terminals ship as a portable Windows x64 executable and use Windows-specific integrations such as %APPDATA% storage and, in APEX, a Windows scheduled task for auto-launch.

Why does Windows say the file is unsafe?

Because the builds are not code-signed. SmartScreen warns about any executable it has not seen signed by a known publisher, regardless of what it contains. Click More info then Run anyway.

Verify the SHA-256 checksum on this page against your downloaded file first if you want certainty that what you have is what we published.

If I close the terminal, are my positions closed?

No. The terminal says so itself on exit: open positions and working orders stay with the broker. Closing the application does not square them off or cancel them.

If you need to flatten, use PANIC or Square Off All before you close — or square off from your broker's own app.

Can I run both terminals at the same time?

Yes. Omega uses port 7810 and APEX uses 7811, and each keeps its data in its own %APPDATA% folder with its own credential vault. Neither can see the other's logins, layout or positions.

Does a strategy keep running if I close APEX?

Only the parts that were placed at the broker. With broker protect enabled, a leg's stop and target rest as real broker orders, so they fire whether or not APEX is open.

Everything decided in software — trailing stops, wait-and-trade, action chains, portfolio rupee rules — needs the terminal to be running. On restart, APEX reconciles every leg against the broker's own position book rather than assuming anything.

How often is it updated?

Frequently. Every code change ends with a version bump, a changelog entry and a rebuilt executable — Omega is on its hundredth minor release and APEX reached v1.12.0 within four days of being forked. Desk-wide changes are applied to both trees in the same sitting so they cannot drift apart.

Real money. Please read this.

Once a live broker is connected, these terminals place real orders in your real trading account. Trading in securities and derivatives carries substantial risk of loss and is not suitable for everyone. You are solely responsible for every order sent from your machine, whether you pressed the button or a strategy did.

This software is provided as-is, with no warranty and no guarantee of execution, uptime, accuracy or fitness for any purpose. Nothing on this site or in the software constitutes investment advice or a recommendation. Test every workflow on the Paper broker before you risk capital.

Read the full risk disclaimer →