A prop firm rule engine that checks every tick.

A rule engine that polls equity every few seconds lets a fast market carry an account straight through its limit between two checks. Here every tick is judged against every open account as it arrives, and a breach is recorded, with the equity that caused it, before the next tick is looked at.

Order-time rules (position count, lot size, hedging, trading hours) run inside the transaction that writes the order, after it has taken that account’s order lock. Two orders sent at once are judged one after the other, never both against the same stale picture.

Rule sets are versioned and append-only. Changing one creates a new version and never edits the old one, and each trading account keeps the version it was created with. You can tighten the rules for next month’s traders without moving the goalposts on this month’s.

Build a rule set visually in the admin panel. Each rule can breach the account, reject the order, or flag it for your review.

When is a drawdown breach detected?

On the price tick that causes it. Every tick is judged against each open account's rules as it arrives, in order, and a breach is written before the next tick is judged. There is no polling interval for a trader to slip through.

What happens to running accounts when I change a rule set?

Nothing. Editing a rule set creates a new version. Each trading account keeps the exact version it was created with for life, so a trader is never judged by rules they did not sign up to. New accounts get the new version.

How is the daily loss limit measured?

From the start of each UTC day, on the higher of the account's balance and its equity at that moment. An account carrying a floating loss overnight therefore does not get a fresh allowance measured from the loss.

Can a rule stop an order instead of failing the account?

Yes. Each rule has an action: breach the account, reject the order before it fills, or flag it for your review and let it through. Position and exposure rules are checked inside the transaction that writes the order, so two orders at once cannot both slip past a limit.