Predefined Strategies — Overview

A grid is not a directional bet. It is an inventory machine. You choose a price window, slice it into evenly spaced levels, and place a resting entry order at each level. Every time price crosses a level the order fills, and the engine immediately places a take-profit a fixed percentage away. When that take-profit fills, the level is refilled and the cycle repeats.

The strategy therefore makes money from movement, not from direction. A market that oscillates inside your window pays you on every swing. A market that trends straight through your window leaves you holding inventory — which is why capital planning and the stop-loss matter more than entry timing.

• Rest — a limit order sits at the level. It consumes margin only once filled, so an unfilled ladder is cheap to carry.
• Fill — price reaches the level. The engine records the fill, links it to the level, and derives the exit from that fill's own price (not from the base).
• Exit — a take-profit order goes out one target step in the favourable direction. For multi-order modes each of the level's orders gets its own target, so a level can book partial profits.
• Refill — once the exit fills, the level is restocked with a fresh entry. This is what makes a grid compounding rather than one-shot.

1. 1
   Particulars — what and where

   Name, broker, exchange, sub-asset, symbol, direction, session mode and which engine runs it. These are identity fields: they are fixed for the life of the strategy and cannot be edited live.
2. 2
   Settings — how it behaves

   Grid mode, ladder structure, spacing and targets, leverage and base price, capital, trailing and the stop loss. Almost everything here can be changed later from the terminal's Settings tab while the strategy runs.
3. 3
   Preview — confirm and deploy

   A full read-back of the configuration plus the derived capital requirement. Deploying writes the config, creates the bot record and starts the chosen engine.

• Realised range — the market must actually travel back and forth across your levels. Spacing that is too wide never fills; spacing that is too tight is eaten by fees.
• Survivable depth — the ladder must be deep enough (and funded enough) that a normal excursion does not exhaust it.
• Size curve — the grid mode decides how much size each level commits. This single choice dominates both recovery speed and blow-up risk.
• Exit discipline — a target that is too small drowns in fees; too large and levels rarely complete a cycle.

• 1.Grid Modes — Overview — How the 27 size curves differ, and which to pick
• 2.Grid Structure — Levels, initial batch and the ladder plan
• 3.Capital Allocation — Why the mode changes the capital you need
• 4.Stop Loss — Bounding the trend risk
• 5.Engines — Python vs C++ — What actually runs your config