Appearance

Personalize your experience

Mode
Accent Color
Direction
Step 1 — Particulars

Step 1 — Particulars

Wizard

Identity of the strategy: where it trades, what it trades, which way it leans, and which engine runs it. These fields are fixed once deployed.

Why these fields are immutable

Everything on this step becomes part of the 's identity. The broker , the and the direction are baked into every the engine generates, into the persisted grid graph and into the reconciliation logic. Changing them on a running strategy would orphan its , so the engine does not allow it — to switch symbol or direction you deploy a new strategy.

ℹ
Note:Behaviour — , spacing, targets, capital, trailing, — lives on and is editable . Only identity is frozen.

Name and description

The name is how the appears in the strategy selector, the dashboard and every log line. Pick something that encodes the and the intent — LTC range 0.8% is far easier to reason about six weeks later than grid 4. The is free and is a good place to record why you chose the parameters.

Broker and exchange

The broker determines which credential set the engine uses, which order-rate limit applies, and which symbol format is sent on the wire. Indian venues are quoted and funded in INR and are subject to a per-second order throttle; crypto venues are quoted in USDT and are effectively unthrottled.

Credential lookup
server-side from your saved at start time. No key material is ever sent from the browser.
Rate limiting
Applied per broker inside the engine's order placer, so a deep ladder never trips the venue's limits.
Symbol format
Indian exchanges are addressed as EXCHANGE:SYMBOL (e.g. NSE:ITBEES); crypto venues use the bare contract symbol (e.g. LTCUSD).
Currency
Selecting an Indian broker switches the currency to INR automatically. You can override it, but and capital must share one currency.

Sub-asset

Distinguishes from spot (and , where supported). It matters because contract semantics differ: futures carry a contract and a , so an order of "1 lot" is not one unit of the , and leverage only applies to derivative products.

  • — leveraged, lot-based, marked to a . The default for crypto grids.
  • Spot — unleveraged; you own the asset. Leverage above 1× is meaningless here.
  • Equity — cash-market instruments on Indian exchanges, -bound.

Direction

LONG gridbaseexit (sell)entries buy BELOW · profit as price risesSHORT gridbaseexit (buy)entries sell ABOVE · profit as price falls
Direction decides which side is the entry and which way the ladder deepens.

A long grid buys into weakness and sells strength: entries step down from the base, take-profits sit above. A short grid does the mirror. The choice also flips the meaning of every option and of the , so the filters those lists to the direction you pick.

★
Pro tip:Choose direction from the 's structural bias, not from a short-term view. A long grid on an asset in a multi-month downtrend will keep averaging into the decline.

Session mode

Continuous
24×7 operation. Correct for crypto: the engine never expects a boundary and keeps alive indefinitely.
Intraday
within the venue only. Positions are expected to be closed by the session end.
Positional
-bound trading, but inventory is carried across sessions. On a session open the engine rebuilds the ladder because the exchange cancels overnight.
!
Caution:For -based venues the exchange cancels every resting order between sessions. The engine detects the open transition and re-places exits for inventory plus the entry ladder — do not be surprised to see a of order placements at the bell.

Engine

Wizardapps/webNestJS APIgrid-botDragonflyconfig + commandsPython engineapps/gridC++ engineapps/hft/gridone snake_case config schema · both engines drain the same Redis command channel
Both engines consume the identical config and drain the same command channel.

Both are server-side; the choice selects the , not the semantics. See the dedicated engines article for the trade-offs.

Python (apps/grid)
Mature, broadest broker coverage, easiest to introspect. Ideal for most grids.
C++ (apps/hft/grid)
- decimal, single-threaded per- slots, far lower and memory per strategy. Preferred for tight spacing, deep ladders or many .

API credential name

Optional. When your broker account has multiple key sets, naming one here pins the to it. Left blank, the engine resolves the default credential for the chosen broker.

Related

  • 1.Predefined Strategies — Overview — How the three steps fit together
  • 2.Engines — Python vs C++ — Choosing a runtime
  • 3.Step 2 — Settings — Everything that is editable live

Related articles

Related to Step 1 — Particulars

  • DCA Direction — Long, Short, Neutral

    Automation / Predefined Strategies / DCA Bot

    Direction Base order Safety orders Take-profit Long Buy at market Buy limits below the base One sell above the average entry Short Sell at market Sell…

  • DCA Particulars

    Automation / Predefined Strategies / DCA Bot

    The venue and instrument. Sizes are in that instrument’s lots / contracts / shares.

  • Grid Mode (in the wizard)

    Automation / Predefined Strategies / Wizard Steps

    The single most consequential setting: how much size each level commits as the ladder goes deeper.

  • Grid Structure

    Automation / Predefined Strategies / Wizard Steps

    Ladder depth, the opening batch, and the base size every level scales from. This section reshapes itself around the selected grid mode.

  • Reading the Ladder Plan

    Automation / Predefined Strategies / Wizard Steps

    The ladder preview is not an illustration — it is the plan, computed with the engine's own sizing and pricing math from the settings you have entered.

  • Spacing & Targets

    Automation / Predefined Strategies / Wizard Steps

    Spread sets how far apart the rungs are, target sets how far each fill has to travel to book profit, and buffer keeps refills from becoming market orders.

  • Step 3 — Preview & Deploy

    Automation / Predefined Strategies / Wizard Steps

    The last read-only checkpoint before real orders exist. Everything shown here is what will be written to the engine config.

  • Engines — Python vs C++

    Automation / Predefined Strategies

    Two independent implementations of the same grid semantics, consuming the same config and the same command channel. The choice is a runtime choice, not a…

  • SFO Contract & Expiry

    Automation / Predefined Strategies / SFO Wheel

    Underlying per lot (NSE lot size) or per contract (Delta: BTC 0.001, ETH 0.01). Quantity, cash secured and P&L all use lots × this.

Browse all knowledge base articles →