Bots And Strategy

Bots are the core operating unit of SteadyEdge. A bot combines exchange context, market scope, entry logic, grid behavior, exit rules, and risk management into one saved configuration.

What this is

This overview explains how bot configuration is structured in the current product and how the bot editor is intended to be used.

When to use it

Use this page if:

- you are about to create your first bot

- you opened the bot editor and want a mental model before filling fields

- you need to understand what each step in the editor controls

Before you start

Before you create a bot, make sure you already have:

- a verified email address if you plan to backtest or launch it soon

- at least one validated exchange account

- a basic idea of the market and side you want to test

Step by step

Step 1: Choose how to start

The editor supports several starting points:

- use a strategy template

- build manually

- import a config file

- edit an existing bot

Templates are usually the fastest option for a first test because they prefill more of the strategy structure.

Step 2: Complete the basic trading context

The Basic step defines the non-negotiable setup:

- exchange account

- spot or futures market type

- symbol or all-coins mode

- spot mode or futures side

- leverage and margin type

- position sizing

Step 3: Add the strategy logic

The remaining steps define behavior:

- Filters decide when the bot is allowed to enter

- Grid defines how the position scales

- Exit defines take profit, stop loss, trailing, and optional funding-capture behavior

- Risk adds daily limits and cooldown rules

Step 4: Save before you test

Saving stores the bot configuration. Running a backtest uses that saved bot. Starting live is a separate command and is blocked until the bot passes the initial launch gate. Later strategy-affecting edits warn that the last backtest may be stale instead of resetting that gate.

What you should see

You should understand two important ideas after this overview:

- a bot is the full execution policy, not only an entry signal

- save, backtest, and start are separate actions with separate checks

Common mistakes

- treating templates as finished strategies without reviewing account, symbol, leverage, and sizing

- editing only the basic fields and forgetting that filters and exits still decide whether the bot is usable

- confusing a saved bot with a running bot

- expecting a bot to start before a valid backtest has passed

- Templates And Basic Settings

- First Backtest In 15 Minutes

- Run Backtest

- Plans And Limits