Per-trade stop-loss
Fixed or ATR-based stop-loss on every order. The bot will never open a position without a defined exit point on the downside. Maximum per-trade risk is expressed as a percentage of account equity, recalculated before each entry.
Risk Controls
Hard-coded risk controls built directly into your bot enforce discipline that no manual checklist can match.
Every automated system we build treats risk controls as structural, not supplemental. This means stop-loss logic, daily drawdown ceilings, maximum concurrent position limits, and kill-switch triggers are coded into the core bot — not added as an afterthought in a settings file someone might accidentally edit. During onboarding, we work through your risk parameters methodically: what is the maximum percentage of capital you are willing to lose in a single day? In a single trade? What should happen if the bot loses three consecutive trades? These answers become hard constraints in the code. The bot will not override them under any market condition. The downside of this approach is that during strong trending periods, your conservative limits may cause the system to sit out profitable moves. That is the correct trade-off — limiting downside consistently is worth more than capturing every upside spike.
Fixed or ATR-based stop-loss on every order. The bot will never open a position without a defined exit point on the downside. Maximum per-trade risk is expressed as a percentage of account equity, recalculated before each entry.
If cumulative daily loss reaches your configured threshold, the bot suspends all new entries until the next configured session start. This prevents one bad morning from compounding into a catastrophic day.
Automatic position closure and bot suspension triggered by broker disconnection, abnormal spread widening beyond a defined multiple, or a consecutive-loss count you specify. Each trigger is logged with a timestamp and alert sent immediately.
Dynamic position sizing based on current account equity means the bot automatically scales down after a drawdown period. You never over-leverage a depleted account — the math is done before every single entry.
“During a flash crash in March last year, the kill-switch fired within two seconds of spread widening past the configured threshold. I lost nothing on that event. Every other time I'd been through a similar spike manually, I'd hesitated and paid for it. The difference was stark.”
Andrei Munteanu, FX trader, Oradea
Tell us your current limits and we'll show you exactly how they'd look as hard constraints inside your bot.
Book a call