Skip to content

Features

Every feature QuantGrid ships, on one plan

QuantGrid mirrors orders from a master account into every child account you link, on rules you set yourself. This page is the full inventory: what the engine replicates, what you can control while the market is open, what gets recorded, and what runs underneath it.

Replication

What gets copied, and at what size

One master order, fanned out to every linked child account. The size on each child is computed from your configuration, order by order, and it is arithmetic you can check.

Master order

NIFTY SEP FUT · BUY · 375 qty (5 lots × 75)

Worked example: how each child order quantity is calculated from the master quantity, the copy factor and the lot size
ChildCopy factorLot sizeRawPlacedResult
C-011.0075375.003755 lots, sent as is
C-020.6075225.002253 lots, exact
C-030.4575168.75150floored to 2 lots
C-040.107537.500under one lot, skipped

child_qty = floor_to_lot(master_qty × copy_factor), then capped by max_quantity

Copy factor, set per child account
Each relationship carries its own multiplier against the master order quantity. One child at 0.5 and another at 3.0 is a normal setup, not an edge case, and retuning one leaves every other child untouched.
Lot-size rounding, always down
Set the lot size on the relationship and every computed quantity is floored to a whole multiple of it. Exchanges reject part lots, and rounding up would trade size your multiplier never asked for. Anything that floors below one lot is recorded as a skipped order rather than sent to the broker.
Maximum quantity cap
A hard ceiling per relationship, itself floored to a lot boundary. However large the master order is, the child cannot go past the size you allowed for it.
Partial fills replicate as deltas
When a master order fills in chunks, each increase in filled quantity is mirrored once, as the difference. A staggered fill never re-copies quantity that has already gone through.
Cross-broker symbol and product translation
A Zerodha master can drive a FYERS child. Symbols and product types are converted on the way through: NSE:RELIANCE becomes NSE:RELIANCE-EQ, MIS becomes INTRADAY, NRML becomes MARGIN. The broker pages list what each integration does.
Equity and F&O
QuantGrid replicates equity and F&O orders on NSE, BSE, NFO and BFO. Commodities (MCX) and currency (CDS and BCD) are outside that scope and are never replicated. Inside that scope both segments replicate on the product types each broker exposes: CNC, MIS and NRML on Zerodha, CNC, INTRADAY and MARGIN on FYERS. An order on any other exchange is written to the audit log as skipped, with the exchange as the reason, and no child order is placed for it.

The order of operations, from master fill to child order, is set out in how it works.

Accounts

One master, many children, and the reverse

A family running three accounts and a desk running forty use the same structure. What changes is how many relationships you create and what you set on each one.

Many children, one master

Link every account you want fed by a single master. Each child holds its own multiplier, cap and lot size, so a small account and a large one can follow the same master at completely different size. There is no limit on how many you run, and no software fee that grows with them.

More than one master

Run several masters side by side: two separate books in one household, or different accounts originating different strategies on a desk. Each master keeps its own set of child relationships.

Configuration lives on the link

Multiplier, lot size and maximum quantity are properties of the master-to-child relationship, not global settings. Change one pairing without disturbing any of the others.

Pause a child without unlinking it

Switch a relationship off and that child stops receiving orders immediately, keeping its broker connection, its configuration and its history. Switch it back on when you want it following again.

Every account authorises itself

Master or child, each account connects through its own broker login and its own API authorisation. QuantGrid never holds funds or securities, and you can revoke access from your broker console at any time. More in security.

Daily session handling

Broker access tokens expire every day by design. QuantGrid tracks each account session, shows you which ones need re-authorising before the open, and holds the connection for the rest of the trading day.

Control

Controls you can reach mid-session

Replication is automatic. Stopping it, flattening it or holding it for approval is manual, and every one of those actions is one click away while the market is open.

  • Square off every linked account

    One action closes open positions across all linked accounts, or across a single account when that is all you need. Built for the end of an intraday session, or for the moment you want to be flat without opening five broker terminals.

  • Cancel open orders

    Cancel resting child orders from the same screen. A cancel or a modify on the master order also propagates to the child orders it created, so the two sides do not drift apart.

  • Live positions and holdings

    Positions and holdings for every connected account, read straight from the broker, next to what QuantGrid replicated. You see each account as the broker sees it, not a stale local copy.

  • Manual approval before replication

    Turn approval on and a master order waits for your explicit confirmation, delivered to Telegram, before any child order is placed. Leave it off and replication runs unattended. The setting is yours, and you can change it between sessions.

Who decides

QuantGrid does not manage your account or trade on your behalf at its own discretion. The software executes only the replication rules you configure, mirroring orders that you or your chosen master account originate.

Read the full compliance position

Visibility

Every event is written down

A copier you cannot audit is a copier you cannot trust. Every event the engine receives, every quantity it computes and every response the broker sends is recorded, in order, with timestamps.

Trade logIllustrative
Example trade log lines for one master order and the child orders it produced
TimeRoleBrokerSymbolSideQtyStateNote
09:15:04.118MasterZerodhaNSE:RELIANCEBUY750OPENorder seen
09:15:04.149ChildFYERSNSE:RELIANCE-EQBUY300PLACED+31 ms
09:15:04.152ChildAngel OneRELIANCE-EQBUY187PLACED+34 ms
09:15:04.161ChildZerodhaNSE:RELIANCEBUY75REJECTEDmargin shortfall, alert sent

Sample lines in the format the log records. Timings shown are typical, not a guarantee for any one order.

Real-time trade log

Every master event and every child order as it happens, with the gap between them in milliseconds. Nothing is rolled up or averaged away.

Append-only audit trail

Every event received, every decision the engine took and every broker response, written once and never edited. Skipped and rejected orders carry the reason they were skipped or rejected.

Exportable records

Pull the log out for your own reconciliation, for your accountant, or to answer a question about one specific order weeks after it was placed.

Telegram alerts

Fills, rejections and connection loss pushed to your phone, so a problem reaches you during the session instead of at the end of it.

Infrastructure

What runs underneath

The parts you never configure, and the ones that decide whether an order reaches your broker in tens of milliseconds or does not reach it at all.

A dedicated static IP, never shared

Every broker account you connect gets a static IP address reserved to it alone, because SEBI requires broker API access to come from a whitelisted static IP. It is one stable address that belongs to you, and your API activity is never mixed in with another customer. The address is the one thing you pay for, per broker account, with IPv6 priced below IPv4.

WebSocket first, REST polling behind it

Order updates arrive over the broker WebSocket, which is the fastest path available. If that socket drops, order-book polling takes over automatically and replication carries on. Both paths feed the same engine and share the same state, so a handover neither duplicates an order nor loses one.

Three independent duplicate checks

Every replicated order passes three separate checks before it reaches a broker: a marker key, a distributed lock and a database constraint. A network retry, a reconnect or a repeated event cannot place the same child order twice.

  • < 50ms

    Median replication latency

    Master fill to child order placed

  • 99.9%

    Uptime SLA

    During NSE and BSE market hours

  • 3

    Brokers live today

    Zerodha, Angel One and FYERS

  • 1

    Static IP per broker account

    Reserved to you, never shared

Pricing

Every feature comes with the dedicated IP

There is no platform fee, no higher tier and no per-feature upsell: everything on this page is included with the dedicated static IP each broker account you connect needs, at ₹499 plus GST per 30 days for IPv6 or ₹799 plus GST for IPv4.

  • Sub-50ms median replication, master fill to child order
  • As many masters and child accounts as you run, within your own accounts
  • Per-account quantity multipliers with lot-size rounding
  • Cross-broker replication with symbol and product translation
  • Real-time trade log with a full, exportable audit trail
  • 99.9% uptime during NSE and BSE market hours
  • Duplicate-order protection on every replicated order
  • Square-off and cancel controls across all linked accounts
  • Telegram alerts for fills, rejections and connection loss
  • Email support, Monday to Friday, 8:00 AM to 5:00 PM IST
Dedicated static IPv6Every feature included

₹499 per 30 days, per broker account · + 18% GST

Dedicated static IPv4Every feature included

₹799 per 30 days, per broker account · + 18% GST

Compliance

QuantGrid is a technology platform, not an investment adviser.

QuantGrid is a technology platform for order replication. It is not registered with SEBI, does not provide investment advice, and does not guarantee any return. Trading in securities carries substantial risk of loss. You are solely responsible for your trades.

Compliance positionRisk disclosureDisclaimer

Get started

Put it on your own accounts

Everything on this page is on the one plan. Link a master, add one child at a small multiplier, and watch the trade log for a session before you scale it up. If you would rather see the engine running first, a demo takes about twenty minutes.

Prepaid wallet · No lock-in, stop any time