Every prop firm makes the same promise to itself: no account gets funded, and no payout gets approved, unless every rule was respected. Whether that promise holds depends on one unglamorous piece of software — the rules engine. It is the part of the stack traders never screenshot and founders rarely demo, yet it decides more of your P&L than the storefront ever will. A rules engine that misses a breach by twelve hours doesn't just fail one account; it funds a trader who should be out, and eventually wires them a payout.
This is a tour of how a real-time engine actually works — using the Singuard Prop Firm CRM's engine as the working example — and of the failure modes that separate real enforcement from a nightly batch job with a dashboard in front of it.
The Loop: Position Sync Every 500 Milliseconds
Enforcement begins with data freshness. The CRM pulls every open position and every closed trade from the trading platform — eTrader natively, or MT4, MT5, cTrader, DXtrade, NinjaTrader, Match-Trader and TradeLocker over one-click bridges — every 500 milliseconds. Each sync recomputes the account's state: equity, running and maximum drawdown, exposure per instrument, position sizes, holding times. Then the rule set attached to that account's challenge type is evaluated against the fresh numbers.
The half-second cadence matters because the rules it feeds are intraday by nature. Daily drawdown is breached by a floating loss at 14:03, not by the balance at midnight. A mandatory stop-loss rule has a grace measured in moments. An overnight-holding cutoff is a specific UTC instant. Check those once a day and you are not enforcing them — you are reporting on them, after the fact.
Per-challenge Rule Sets, Not Global Settings
A serious firm doesn't run one rulebook; it runs one per product. In the engine, every challenge type carries its own settable rule set — daily and overall (trailing) drawdown, profit target, minimum trading days, minimum trades, inactivity limit, per-challenge leverage — plus the advanced layer: max position size, max exposure per instrument, lot-size variance, mandatory stop-loss grace, overnight cutoff (UTC), news-trading windows, no-weekend-holding, single-day consistency caps and prohibited-strategy detection for HFT, grid, martingale and hedging.
Crucially, funded accounts get a separate post-funding rule set per challenge type, drawn from the same library but with independently chosen consequences — fail the account, reset the balance, or do nothing. Evaluation rules select traders; funded rules protect capital. An engine that can't distinguish the two forces you to compromise one or the other.
Configurable Consequences — The Engine Acts, You Decide How
Detection without a decision is just logging. For each rule you choose the consequence in advance — pass, fail, flag, suspend or do nothing — and the engine applies it within your thresholds the moment the condition is met. In practice that produces three automatic behaviors:
- Auto phase advance — a trader who meets the profit target with all conditions satisfied is promoted to the next phase, or funded, without a staff member touching anything.
- Auto breach with the reason attached — a violated hard rule fails the account and emails the trader the exact rule and numbers behind the decision. That single email eliminates the largest category of support tickets a prop firm receives: "why was I breached?"
- Flag for review — softer signals (a suspicious pattern, a borderline consistency score) route to staff instead of auto-failing, so human judgment is spent only where it's needed.
Vendor question that settles everything: "When exactly does a breach fire, and what did the account's equity read at that moment?" A real-time engine answers with a timestamp and a number. A batch engine answers with tomorrow.
The Audit Log: Every Decision, Permanently on Record
Automation you can't reconstruct is automation you can't defend. Every decision the engine takes — and every staff action around it: phase changes, payouts, refunds, leverage edits, bans — is written to a permanent, searchable audit log that no one can quietly edit, recording who (or what) did it and when. When a trader disputes a breach, you replay the record: the rule, the threshold, the tick that crossed it. When a payment processor or partner asks how decisions are made, you show a system, not a spreadsheet. Disputes end at the log.
Real-time Engine vs Overnight Job
| Overnight batch job | Real-time engine (500ms) | |
|---|---|---|
| Breach latency | Up to 24 hours | The moment it happens |
| Intraday rules | Invisible between runs | Enforced continuously |
| Consequences | Staff apply next day | Applied automatically, per your config |
| Trader communication | Manual emails, delayed | Instant email with the exact reason |
| Exposure window | A breached account keeps trading overnight | Closed in seconds |
| Evidence | Reconstructed from exports | Permanent audit log per decision |
The exposure window is the line that costs real money. Between a batch engine's runs, a breached account is still live — still trading, still able to dig deeper or, worse, recover and later claim a payout on an account that was already dead under your own rules. Firms discover these cases at payout review, argue them in public, and lose either the money or the reputation. A 500ms loop simply never opens that window.
What the Engine Feeds Beyond Enforcement
Because the engine holds a live, per-tick picture of every account, everything downstream inherits it: the account analyzer shows each rule pass/fail against a live equity curve, drawdown progress updates as the market moves, payout eligibility is pre-checked before a request is even allowed, and leaderboards rank on numbers that are seconds old rather than yesterday's. One data loop, every 500ms, drives the entire firm — which is exactly why it ships pre-wired in the bundle instead of as an integration project.
"We sync positions every 500 milliseconds because a rule enforced after the fact isn't a rule — it's an apology."
— Alex Onta, Executive Director, eTrader & Prop Firm CRM
Key Takeaways
- Positions and closed trades sync every 500ms — intraday rules like daily drawdown and stop-loss grace are unenforceable at overnight cadence.
- Rule sets attach per challenge type, with a separate post-funding set — and you choose each rule's consequence: pass, fail, flag, suspend or nothing.
- Breaches fail the account and email the trader the exact reason automatically — killing the biggest source of disputes and support load.
- Every automated decision lands in a permanent audit log — enforcement you can replay is enforcement you can defend.
Frequently Asked Questions
Does the Rules Engine Work with MT4/MT5 or Only with eTrader?
Both. The engine is platform-agnostic: eTrader connects natively, and MT4, MT5, cTrader, DXtrade, NinjaTrader, Match-Trader and TradeLocker bridge in one click — with the same rule library and the same enforcement behavior across all of them.
Can I Override an Automated Decision?
Yes. Staff can review flags, reinstate accounts and adjust outcomes from the back office — and every override is itself written to the audit log with who did it and when, so discretion never becomes invisibility.
What Happens If a Trader Breaches While Staff Are Offline?
Nothing different — that's the point. The engine runs server-side around the clock: the account is failed within the sync cadence, the trader receives the reason by email, and your team finds the case closed and documented in the morning, not open and compounding.