How an order actually travels through Algorika.
From a tick on the tape to a fill at the broker, every hop is a product surface you can open. This page walks one order through all of them.
One order · 12:41:02 IST
01 Market data
+0 ms
NIFTY 24800 CE prints 142.40 on the Kotak feed; instrument master resolves it to one canonical id.
02 Intelligence
+4 ms
Analytics engine updates IV 12.8 and delta 0.51; Options Intelligence marks buildup as short-cover.
03 Strategies
+9 ms
GPS v2 reducer sees ATM shift; emits intent: roll CE leg, policy PASSIVE, 2 lots.
04 Risk
+11 ms
Caps: capital 64% used, day loss 17% used. Gates open. Lot and tick valid. Intent admitted.
05 OMS / execution
+14 ms
Execution engine builds child order LIMIT 142.50; OMS records order state OPEN.
06 Broker egress
+18 ms
Router checks Kotak rate limit 8/10 per s; executor on 3.108.174.225 POSTs the order. 87 ms later: FILLED.
07 Firm layer
+110 ms
Fill posts to the positions ledger; org manager's platform activity ticks; request register stores the call.
01Market data
Live quotes, depth and a canonical instrument master across every connected broker.
Quotes and depth come from each connected broker's feed and are normalised onto one instrument master, so NIFTY 24800 CE is the same instrument whether Zerodha or Kotak is quoting it.
A market-state monitor tracks freshness per shard, so the desk knows when a tape is stale rather than guessing.
Historical OHLC jobs and instrument files are queued and stored, and long-horizon ticks, greeks and candles land in a warehouse for research.
Market watchDepth · NIFTY 24800 CE
Est. charges ₹41.20 · MIS
02Intelligence
Option chains, OI analytics, IV surfaces and greeks computed continuously.
The analytics engine computes IV, greeks and the vol surface continuously for any universe you subscribe.
Options Intelligence turns raw OI into PCR, max pain, buildup classification, support and resistance scores and gamma exposure, for the NIFTY family always and for stocks on demand.
The same numbers show up in the option chain, in the cockpit and in reports. One computation, many views.
NIFTY option chain · Options IntelligencePCR
1.18
Max pain
24,750
GEX
+2.1B
Buildup
Short cover
Support
24,700
Resistance
25,000
03Strategies
Subscribe to strategies from a marketplace. Same code path for backtest, paper and live.
A strategy is a package with a reducer and effects. The same code runs in backtest, simulation, paper and live; only the venue changes.
Traders subscribe from a marketplace and pick universe, broker, max capital, max loss and autostart. Firms decide which strategies each org can see.
Shadow mode emits signals without orders. Paper books trade a virtual INR account on live prices. Live books send real orders.
Strategy cockpit · GPS v2Book · LIVE
Running+₹12,460
Unrealised · 4 open legs · notional ₹5.85L
Legs · 0.5Δ + 0.3Δ wings
Tape
09:31:04 signal · ATM shifted 24800 → 24850
09:31:05 intent · roll CE leg passive
09:31:06 child · 24850 CE SELL 2L @ 131.10 filled
09:31:06 risk · caps ok · exposure 61%
04Risk
Capital and loss caps, trading gates, kill-switch, exposure checks on every fill.
Caps are enforced before an order is built. If a subscription is at its max capital, the intent never reaches the OMS.
Trading gates, kill-switch, placement enable and dry-run, are global and visible on every desk. Flipping one stops the whole book.
Every fill re-checks exposure. Baskets carry their own MTM target, stop and trail in software, independent of the broker.
Trading gates · subscription capsTrading gates
Subscription · GPS v2 · LIVE
Basket MTM
05OMS / execution
Intents become validated child orders: policies, slicing, multi-leg plans, smart baskets.
Orders enter as intents. The execution engine validates lot and tick sizes, applies a policy (aggressive, passive, balanced, TWAP, iceberg, hedge-first, emergency) and emits child orders.
Smart baskets compose legs sequentially, in parallel or as a DAG, with price policies per leg and one-click exit for the whole structure.
The OMS keeps one canonical order state and fill history. The positions ledger reconciles against each broker and flags differences.
Smart basket · iron condorTarget
+₹9,000
Stop
−₹6,000
Trail
₹1,500 step
Payoff at expiry
06Broker egress
Rate-limit aware routing to Zerodha, Upstox, Kotak Neo, Angel One, or the paper venue, via static IPs.
A broker registry holds versioned capability configs: order types, product types, instrument mappings, rate limits. Adding a broker is configuration, not a rewrite.
Each trader can be routed through a static-IP remote executor, so the IP a broker sees is the one registered with it. Placements, schedules and an IP ledger keep it auditable.
Every outbound broker request, direct or via the executor, is written to a request register with status and latency.
Broker egress · static IPRoute
Intent
EE-2 · policy PASSIVE
Validators
lot ✓ tick ✓ caps ✓ gates ✓
Router
rate-limit 8/10 per s
Executor
static IP 3.108.174.225
Broker
Kotak Neo · 87 ms
Broker request register
429 retried after 250 ms under registry backoff.
07Firm layer
Orgs, roles, act-as, strategy enablement and usage charges wrap the whole stack.
Sub-brokers create orgs, invite owners and managers, and onboard traders. Roles carry module-level permissions.
Operators can act on behalf of a trader from the accounts desk. Every such session is audited.
Usage and charges attribute infrastructure spend to sub-brokers, traders and shared nodes, straight from the cloud bill. Platform activity shows the book's day: orders, brokers, alerts, onboarding.
Accounts desk · Trader deskActive
6
Auth today
5
Auth missing
1
Remote on
5
Draft
1