Is an account-level guard worth it? An honest decision guide
Short answer: it depends on one question - can a single bad day, or a single misbehaving EA, take the account somewhere you would not accept? If yes, an account-level cap is a different control from anything inside the EA, and it is usually the cheapest insurance in the stack. If no, you probably do not need it.
What a stop loss does not do
A stop loss is a per-trade control. An account-level daily cap is a per-account, per-day control. They fail in different ways:
| Situation | Per-trade stop loss | Account-level daily cap |
|---|---|---|
| One EA on one chart, one bad trade | Handles it | Not needed |
| Same EA on three charts | Each trade is "correctly" sized; the account carries 3 correlated positions | Sees the account total and stops |
| An EA that misbehaves (loop, wrong size, no stop) | Depends entirely on that EA being correct | Stops the day regardless of what the EA thinks |
| A prop-firm daily loss rule | Not what the firm measures | Measures the same thing the firm measures |
| You close the terminal mid-session and reopen it | Unaffected | Only works if its state survives the restart |
When it earns its place
- You run more than one chart or more than one EA on the same account or the same symbol.
- You are on a prop-firm or risk-managed account with a hard daily rule.
- You are not watching (VPS, overnight, unattended) and want a bound that does not depend on your attention.
- You have ever had a day you would describe as "that should not have been possible".
When it does not
- You have one strategy, one chart, and a hard stop on every trade, and you accept full per-trade risk. A daily cap adds a layer that will occasionally stop a day that would have recovered - that is a real cost, not a hypothetical one.
- You want it to make money. It will not. A guard reduces the tail; it does not add edge. If the strategy has no edge, risk control just makes the account last longer on the way down.
- You want to be told what to trade. This is not a signal tool.
The ten-minute test
Before buying anything (including free things - your time is the cost), do this on your current setup:
- Write down your worst plausible day: the largest loss your current configuration could produce if several things went wrong together. If you cannot answer, that is the finding.
- Let a limit trip deliberately on a demo account, then kill the terminal with a position open and restart it. Does the protection come back? If it does not, whatever you are relying on has the lifetime of an in-memory variable.
- Ask: if I ignored this tool completely, would anything be different? If the answer is no, it is decoration.
What this project actually is
VigilDesk Guard is an account-level daily loss cap for MetaTrader 5 - one number for the account, derived from the broker's trading day, persisted so a restart cannot reset it, sitting above whatever EAs you already run. It is free, source-included, with no DLLs and no external calls. It is not a strategy, not a signal service, and it does not promise anything about performance. If the test above tells you that you do not need it, that is a perfectly good outcome - you have just saved yourself a dependency.
The free build and the source: xuks124.github.io/vigildesk/free.html
Related notes
- Is your guard real or decorative? A checklist
- Your daily loss limit resets when MetaTrader restarts. Here is the fix.
- Memory plus an expiry policy: what a restarted guard is allowed to assume
- Detection is not resolution: the gap that makes guards decorative
- Decisionless monitoring: the reports nobody acts on
- What a kill switch should actually do (and the four ways they fail)
- Silent failures in trading automation: the three that cost the most
- Which day is it? Broker time, host time, and the trading-day boundary
Risk disclosure
Algorithmic trading carries both technical and market risk. No tool eliminates the possibility of loss. Nothing on this page is investment advice, and no performance is implied or promised.