Official Demo And Activation Onboarding
The official demo lets you inspect a completed public backtest before signup, then clone the same starter into your workspace after email verification.
What this is
This article explains the handoff from the public demo report to the in-product onboarding flow. The flow starts with a demo backtest, stores the selected demo template during signup, and creates a stopped starter bot plus a first backtest after the account is verified.
When to use it
Use this article when you want to evaluate SteadyEdge before connecting an exchange key, or when the dashboard shows the activation card after registration. It is also useful when support needs to explain why the first milestone is a completed backtest, not live trading.
Before you start
- You can open the public demo without signing in.
- Cloning the demo requires an account and verified email.
- The onboarding starter removes any exchange account from the cloned config.
- The first backtest can run before a demo or live exchange key is connected.
Step by step
Step 1: Open the official demo
Go to /en/demo and review the equity curve, test settings, and journal preview. The report is a starting point for inspection, not a promise of future returns.
Step 2: Clone the starter
Use Clone and Run to start signup with the demo template attached. After registration, verify your email before starting onboarding.
Step 3: Start onboarding from the dashboard
Open Dashboard . The onboarding card shows the email, template, and backtest stages. Start the flow to create the starter bot and queue the first backtest.
Step 4: Continue after the backtest
When the backtest completes, open the report, then connect a demo or testnet exchange account before attempting the first running bot.
What you should see
A completed onboarding start creates a starter bot, a queued or completed backtest, and a dashboard action that points to the next activation step. It should not require a live exchange key.
Common mistakes
- expecting the public demo to start live trading automatically
- skipping email verification and then seeing onboarding blocked
- treating the demo result as a guarantee instead of a reusable example
- connecting a mainnet key before reviewing the first backtest and risk settings
Related articles
- First Backtest In 15 Minutes
- What You Need Before First Bot
- Why Live And Backtest Results Differ