What you are doing
You are binding a fixed HEDGERON engine to one verified exchange subaccount and starting its monitored runtime.
Why it matters
A controlled launch prevents incomplete credentials, insufficient capital or account conflicts from reaching order execution.
Before you start
Confirm active membership, VERIFIED exchange connection, required capital and no other running bot on the same subaccount.
Step by step
- 01Open My Bots and choose the engine.
- 02Select the dedicated exchange subaccount.
- 03Enter the approved capital and supported mode.
- 04Review the summary and submit deployment.
- 05Open Dashboard and check bot, Sentinel and Shield states.
What you should see
The bot can show ACTIVE with no open position while it waits for a valid signal. That is not a fault.
Security check
Never launch in Live until the platform explicitly unlocks the required production release gates.
Common problems
No trade opened
Wait for valid market conditions and check that market data is current.
Subaccount already in use
Use a separate dedicated subaccount for the second bot.
Launch failed
Do not retry blindly; read the preflight error and follow its linked Help article.
Next step
Learn how to read the live Dashboard without confusing balance and equity.
Privacy note
HEDGERON Help analytics must never collect API credentials, passwords, private account values or secret-bearing URLs.