True story · Risk management · 3 min read

Server stop vs on-screen stop: the difference that saves accounts

Let us tell you about a real night in July. Several funded accounts open, the market on the move… and suddenly the data feed freezes. The charts, dead. The screen, lying. Any protection living on that PC was as blind as we were.

What did NOT fail

The physical stops planted on the broker's server never even noticed the blackout: when price touched them, they filled perfectly, across every account. Because they didn't depend on our screen, or our internet, or our PC — they lived on the exchange's infrastructure.

The lesson, in one sentence

An "on-screen" stop (the one your platform sends when it's hit) is a promise from your computer. A server stop is an order already delivered. When everything goes fine, they're identical. The night something fails, one exists and the other doesn't.

How to automate it

• Always trade with an ATM (a bracket with a server stop from second one).
• And for the day a bot fails or something slips through: a watchman that detects any position without a stop and plants a physical one automatically at the distance you define.

That watchman exists and it's called Jackson Guardian: gatekeeper against naked positions, emergency server-side SL, daily cap with automatic panic and a panic button on your phone. In 3 minutes:

10-day trial for room members · cancel online whenever you want · jackson-guardian.com