Risk per trade
Size comes from the stop distance and the risk cap, not a fixed lot.
Risk Management
Risk per trade, max drawdown, daily loss, exposure and filters.
Scope
The scope is settled before work starts; the items below are part of this service.
Size comes from the stop distance and the risk cap, not a fixed lot.
When a ceiling is reached the system stops opening trades until the next window.
Open trade count and total risk across several symbols are controlled.
Every rule breach is written to the log and raised as a notification.
Risk rules are enforced in code so execution never depends on an in-the-moment decision — built for prop accounts.
Three design questions are settled here: the drawdown reference (balance or equity), the trading-day window in server time, and what the system does once a cap is hit.
The output is usually an independent layer that can also be added on top of an existing EA.
Delivery
Four stages with defined output; nothing moves on without your approval.
Ceilings, percentages and system behaviour for each condition are fixed.
The rules are enforced inside the system as controllable limits.
Edge conditions and losing streaks are simulated and reviewed.
Setup guide, logs and the reset procedure are handed over.
Handover
What you receive at the end of the project.
3 items
This list is part of the project scope; each item is handed over at the end of its stage, before final delivery.
Who it is for
If one of these describes your situation, this is the right service.
The strategy was not the problem; having no defined ceiling was.
Account limits must be respected technically and automatically, not by hand.
Questions
Short answers to what clients ask about this specific service.
Yes. In many projects the risk layer is added to the existing system as an independent module.
Yes. You set the ceilings; we implement and test how the system behaves under each condition.
The reset window is defined in the rules document: a time window, manual approval, or both.