Risk per trade
Define the maximum amount or percentage you are willing to risk on each trade. Position size follows this limit.
Risk Controls
Nister AI does not remove risk, but it lets you define the maximum exposure you are willing to accept before automation can place any trade.
Risk controls reduce specific failure modes; they do not make trading risk-free. Losses are possible.
Define the maximum amount or percentage you are willing to risk on each trade. Position size follows this limit.
Set a maximum daily drawdown. If reached, trading should stop until the next session.
Cap how many positions can be open at once so exposure stays within your tolerance.
Strategy logic controls entries and exits, but your risk boundaries should keep outcomes inside your acceptable loss range.
If your account balance is $10,000 and you set risk at 1% per trade, each trade risks about $100. If your daily loss cap is 5%, trading should stop after around $500 of cumulative daily losses. Use numbers that match your own risk tolerance.
Local users should keep device, power, and internet stable. Managed VPS reduces this dependency.
Spreads, slippage, and execution speed vary by broker. Use a broker with reliable fills.
Protect account credentials and enable security controls available on your accounts and devices.
See how autonomous Forex Trading works with broker-account ownership and risk boundaries.
Open Forex PillarFollow the setup flow to connect broker details, configure risk, and activate in the correct order.
Read Setup GuideReview the full risk disclosure before using autonomous execution on a live account.
Read Risk DisclosureNo. Risk controls define boundaries, but they cannot prevent all market moves, slippage, outages, broker issues, or strategy losses. There is no profit guarantee.
Set them before live automation starts, then review whenever account size, volatility, broker conditions, or your risk tolerance changes.
Configure limits first, then activate. Conservative settings are usually safer while you learn how the workflow behaves.