Service
Practice Partners' risk control layer enforces your loss limits and exposure rules at the server level — independent of your broker and independent of you.
Brokers execute stop-loss orders as market orders in fast conditions — they can gap, requote, or in some cases simply not trigger during extreme volatility. Practice Partners adds a second enforcement layer that monitors your account exposure directly via API and sends a close-all instruction the moment a configured threshold is breached, before the price can move further against you. This is not a replacement for your broker's own risk features; it is a redundant layer that operates on our infrastructure, separate from the broker environment entirely.
Set rules once; the system enforces them every second the market is open.
Define a maximum drawdown figure for the calendar day in your account currency — RON, EUR, or USD. When that figure is hit, the bot halts all new orders for the session and sends you an immediate Telegram or email alert. You resume manually the next trading day.
Cap the total notional value of open positions across all strategies running on the account. Useful when you run multiple bots on correlated instruments and want to prevent unintentional stacking of directional risk during high-volatility sessions.
Automatically flat the account before scheduled high-impact news events by configuring a no-trade window. You specify the event time and a buffer in minutes; the system closes any open positions and blocks new entries until the window clears.
No software-based risk layer eliminates market risk. In the event of a broker system outage, an internet connectivity failure on our hosting infrastructure, or a sudden liquidity gap that skips the configured threshold price, losses beyond the set limit remain possible. Practice Partners' risk controls reduce the frequency and severity of large loss events; they do not make trading capital safe in all scenarios. We document every scenario where the system may not perform as configured, and we expect you to read that documentation before going live.
Currently, each risk control configuration is scoped to a single broker account. If you run bots across two brokers, you configure separate limits per account. Cross-broker aggregate exposure monitoring is on our 2025 roadmap.
Our monitoring loop runs at 500-millisecond intervals. From the moment a threshold breach is detected to the moment the close-all instruction is sent to the broker API, the typical latency is under 1.2 seconds. Execution at the broker side adds additional time depending on market conditions.
Yes. Limit changes made in the azure-trust dashboard take effect within one monitoring cycle — approximately 500 milliseconds. You do not need to pause or restart the bot to update risk parameters.
Every threshold breach, halt, and kill-switch activation is written to an immutable event log in your dashboard. You can export the log as a CSV for your own records at any time.
Risk controls are included in every plan — configure yours before your first live session.
Get started