Risk Alert System
Real-time risk monitoring for MT4 and MT5 brokers. The Risk Alert System watches every account on your trade servers and raises an alert the moment something looks wrong — abnormal volume, large losses, equity jumps, scalping or credit not covered by equity.
Alerts for the risk team — and no one else
The Risk Alert System streams the state of every account from your MT4 and MT5 servers and checks it against a pack of configurable rules. When a rule fires, the alert lands in the web UI with a sound — visible to your risk team only. Nothing is ever sent to clients or to the MT terminals, and the shipped rules never change anything on the trade server.
Rules are Lua modules configured from the web UI. Changing a threshold, a group or a server filter takes effect the moment you press Apply — no rebuild, no restart, nothing to deploy.
- Any number of MT4 and MT5 servers watched at once, each with its own server key
- Deals and balance operations processed within about a second
- Every alert stores the server, rule and login it belongs to
- Runs on your infrastructure: Windows services next to the trade servers, a Linux service for the engine

Twelve rules that catch what matters
Shipped and ready to tune. Thresholds, windows, group and server masks are edited in the web UI; custom rules plug into the same Lua scripting API.
PnL, equity and balance
- Closed PnL spike — a large realized profit or loss booked within a short window, in either direction
- Equity jump — a fast rise in equity over a short and a long window, with deposits excluded
- Large loss / drawdown — realized plus floating losses reach a share of the balance
- Large balance change — net real deposits or withdrawals out of pattern
- High leverage with low equity — small accounts trading very high leverage
- Credit not covered by equity — a client trading only on broker credit
Volume and turnover
- Turnover spike — an abnormally large closed volume within a short window
- Large open volume — a total open position above the threshold, in lots
- Open volume by direction — one-sided exposure: BUY, SELL and NET checked separately
Watch a single symbol, a mask like XAUUSD,BTCUSD* or the whole book — each rule chooses its own instruments, groups and servers.
Behaviour patterns
- Overtrading / churning — too many deals opened within a short time
- Scalping / HFT — many deals closed fast, each with a small price move and a short hold
- Profit concentration — the result comes mostly from a watched symbol list such as gold, silver and Bitcoin
Every rule has sensible defaults — for example, 5,000 USD closed PnL in 60 seconds or 20% of balance lost — so the pack is useful from day one.
From trade servers to alerts in about a second
Data flows from the MT servers through the connectors to the Central Risk Service, where the engine runs the rules — each hit becomes an alert in the UI.
MT4 / MT5 connectors
Windows services installed on the broker’s side, one per trade server. They connect through the Manager API and stream account state, deals and balance operations to the central service, and answer its requests for history, symbols and conversion rates.
Central Risk Service
A Linux gRPC service. It keeps the state of every account, computes the metrics each rule needs for its time windows and runs the Lua rules. Active accounts are recalculated within about a second of a deal; idle ones are parked until something happens.
Web UI
A React single-page app behind nginx with HTTPS and Basic Auth, with tabs for alerts, rules, an expert script view and settings. Works from any browser — nothing to install on the risk team’s machines.
Built for the daily routine of a risk team
Everything happens in one web UI with four tabs — Alerts, Rules, Script (expert) and Settings — behind nginx with HTTPS and Basic Auth. Any browser, nothing to install.
Alerts
- Live feed at the top chimes on every new episode; the bell mutes it per browser
- Filter by status — New, Acknowledged, Resolved, Dismissed, Expired — and by rule name
- Each row shows rule, login, server, latest message, status, occurrences, last seen and last IP
- Bulk buttons act on every alert matching the current filters, not just the visible page
Alert lifecycle
- New → Acknowledged → Resolved or Dismissed, with an optional comment on every change
- One open alert per server, rule and login: repeat hits update it instead of spamming
- Quiet alerts expire automatically — the TTL counts from the last hit, not from creation
- Click a rule name for the full alert: first and last seen, the complete message and the status history
Accounts
- Click a login to open the account card: balance, equity, free margin, credit and leverage — in the account currency and in USD
- Engine metrics for every window the rules use: 60 s, 300 s, 1 h and 1 d by default
- Hover any metric for what it means; a toggle reveals zero values
- Alert times in each trade server’s own time zone; UTC offsets are measured automatically
Rules
- Enable or disable each rule; set its alert name, group and server masks and thresholds
- The header shows the mode badge and who applied the configuration, and when
- Reload, Revert, Preview script and Apply — changes take effect without a restart
- Export and Import configurations, with the module library underneath
Expert tools: view the Lua source of any shipped module, clone it into a custom copy, or hand-edit the assembled script.
Want your risks watched around the clock?
Tell us what your risk team needs to see. Our team is available 24/7.