First Backtest In 15 Minutes
The fastest useful milestone in SteadyEdge is not only creating a bot. It is getting a real backtest result you can inspect and reuse.
What this is
This article gives the shortest accurate path from a fresh account to a completed backtest in the current product.
When to use it
Use this article if:
- you are new to SteadyEdge
- you want the first real result quickly
- you prefer starting from a template instead of designing every rule manually
Before you start
Complete these prerequisites first:
- create an account and sign in
- verify your email
- connect at least one validated exchange account
For speed, this article assumes you will start from a template.
Step by step
Step 1: Open the bot builder
Go to Dashboard -> Bots and create a new bot.
If speed matters most, start from a template on the first step instead of creating the configuration from scratch.
Step 2: Fill the basic trading context
In the Basic step, confirm:
- exchange account
- symbol or all-coins mode
- side
- leverage and margin mode when relevant
- position sizing
The exchange account must already be validated or it will not be available here.
Step 3: Make sure the strategy is valid
A meaningful starter bot needs more than a name. In practice, the minimum usable setup should include:
- at least one entry filter
- at least one exit rule, such as take profit or stop loss
- sizing that matches the connected account
Templates help because they prefill more of this structure.
Step 4: Save the bot
Click Save Bot . Saving creates the bot record, but it does not start live trading.
For a new bot, the current flow returns you to the dashboard after save.
Step 5: Launch the backtest
From the dashboard, find your bot row and click Run Backtest .
Important current behavior:
- the standard saved-bot flow runs with initial_balance = 1000
- Free plan users are limited to shorter periods
- Free plan backtests are forced public
- paid plans can use longer periods and choose public or private visibility
Step 6: Open the result
After submission, the run appears in Backtest and moves through the normal lifecycle:
- pending
- running
- completed
- failed
Open the backtest detail page once the run is available.
What you should see
At the end of this flow, you should have:
- one saved bot
- one backtest record in Backtest
- a visible status for that run
- a result page you can return to later
Common mistakes
- skipping email verification and only discovering the restriction when the run is blocked
- building from scratch before understanding filters, exits, and sizing
- assuming Save Bot also means Start Bot
- choosing a period your current plan does not allow
- treating a pending run as failed instead of queued
Related articles
- Registration And Login
- Templates And Basic Settings
- Run Backtest
- Connect Exchange Account