Prop Firm Drawdown Protection: Where It Actually Runs

Read the sales pages in this category and they all say a version of the same thing. Daily loss protection. Drawdown limits. Automatic pause before you breach.

Now try to find one that tells you where that limit is being watched from, and what happens to it the moment your internet drops. You won't. The feature is on every page. The failure mode is on none of them, and the failure mode is the part that decides whether the protection is real.

A daily loss limit has to be calculated somewhere, and there are only two places it can be: inside the trading terminal on your own machine, or on a company's servers. Terminal-side keeps working if the vendor goes down, but can only ever see that one terminal. Server-side can watch several accounts and several venues at once, but it needs a live connection to act. Neither is better in the abstract. What matters is that you know which one you bought and what it does when the link between the two breaks.

Where can a limit actually be watched from?

Two places. That's the whole list.

On your machine. A program sits inside your MT5 terminal, watches the account, and closes trades or blocks new ones when a number is reached. Everything happens locally.

On a server. A company's system holds the picture of your account, does the arithmetic, and sends instructions down to whatever is connected to your broker or exchange.

That single choice decides everything else about how the protection behaves, and it's the thing least likely to appear anywhere in the product's marketing.

What each one can and can't do

The pattern is consistent. The closer the protection sits to your terminal, the less it depends on anyone else being alive, and the less it can ever see beyond that one account. The further away it sits, the more it can coordinate, and the more it depends on a connection.

If you run one MT5 account and nothing else, terminal-side has a genuine argument. The moment you have a second account, or a crypto exchange alongside your prop account, it stops being able to do the job at all, because a daily loss across two accounts is a number neither terminal can see.

Why nobody publishes this

Because the honest answer has a hole in it, and a sales page doesn't want one.

Every system in this category has a moment where the protection isn't running. Terminal-side has it when your laptop sleeps. Server-side has it when the connection drops. There is no architecture without the gap, and any product claiming its limits hold through a disconnection is describing something that can't happen.

So the useful question isn't which product has no gap. It's which one tells you how big theirs is, what it does while it's open, and what it does when it closes. Vagueness on those three is itself an answer.

Here are ours.

What happens the moment the connection drops

The account is paused. Not the strategies themselves, which carry on doing their own thinking. What stops is anything they decide reaching your broker.

In practice that means:

Nothing new opens on that account. No entries, no additions to a position, no fresh orders of any kind while the link is down.

Your open positions stay exactly where they are. Your broker is still holding them, and the stop loss and take profit attached to each one are real orders sitting on your broker's own systems. They execute whether we're connected or not. That protection doesn't depend on us and never did.

Signals that fire during the gap are discarded, not saved up. This one is worth being clear about because the assumption usually runs the other way. Nothing queues. A signal that would have triggered while you were disconnected does not fire when the connection returns.

That's deliberate. A queue that empties on reconnect would place trades against prices that have moved, on a setup that may have already played out, at a moment you weren't watching. The choice is between missing a trade and taking a bad one, and missing it is the smaller cost.

What happens when it comes back

Three things, before your account is allowed to trade again.

It reads your broker, not its own memory. Positions, balance, equity, and the record of every trade that happened during the gap. That last part is how it learns that a stop was hit while you were offline.

Where its picture and your broker's disagree, the broker wins. Always. Your account is whatever your broker says it is, and anything the platform believed before the drop is discarded in favour of what actually happened.

It checks whether it missed any price history. If bars are missing from the gap, the indicators a strategy relies on are rebuilt from the repaired history rather than carried forward from an incomplete picture. And the rebuild itself never produces a trade. Repairing the data can't trigger a signal.

Only after all three does execution resume.

The claim that comes out of that is narrow and it's the one worth holding us to: a strategy that starts again after an outage acts on what your broker actually did, not on what we last remembered.

What if you breached a limit while disconnected?

The halt fires late, and it fires on what genuinely happened.

Because reconnecting reads your account's trade history, a loss taken during the gap is counted. So a daily loss limit that was breached while you were offline halts the account when the link returns, rather than being quietly missed. The halt applies before execution resumes, so a breached account doesn't get to place one more trade and then stop.

There's an honest edge to this and it matters. A breach that happened and reversed while the connection was down isn't enforced retroactively. If your equity dipped through the limit at 14:40 and recovered by 14:45 while we couldn't see the account, there's nothing left to halt on when we come back. The limit protects you against a position, not against a moment nobody observed.

That's a real limitation of any server-side system, including this one, and it's a direct consequence of the same gap the whole article is about.

How long is the gap?

Under a minute, and I'm not going to give you a tighter number than that yet.

The connection has its own timeout, and detection is bounded by it. "Seconds" isn't something I can currently support with evidence, and "instant" isn't true of anything. Once we've measured it properly on a controlled disconnection, the measured figure gets published here with the date on it.

That number is the size of your unprotected window, so it deserves a measurement rather than a marketing adjective. Treat any competitor who gives you a confident figure without saying how they got it the same way you'd treat a backtest with no data.

You do find out it's happening. A dropped connection triggers a notification, which is the part that actually matters day to day. The specific danger of automation is silence, and no trades looks exactly like no signals until you check.

Why crypto doesn't have this problem

This is the part most traders haven't put together, and it changes how you think about where to run what.

An exchange account connects over the internet directly. Nothing has to be installed, nothing has to stay open, and your computer has no role in it. So a daily loss limit on a Binance or Bybit account keeps running with your laptop shut, your phone in your pocket, and you asleep. The connection is between two servers and neither of them is yours.

MT5 is the exception, and it's the only one. The terminal is a program on a machine, it only talks to your broker, and nothing can reach into it from outside. So automating MT5 means something runs in that terminal, and that terminal has to stay awake. Your machine or a rented one, but somewhere, always on.

Which produces an uncomfortable asymmetry worth knowing before you plan around it: the account type with the strictest rules and the hardest consequences, the funded prop account, is the one running on the only platform that needs your computer to be alive. Crypto, where nobody terminates your account for a bad day, is the one that needs nothing from you at all.

The practical reading. If you're automating MT5, where the terminal lives is a risk decision, not an IT one, and a machine you close at night is a machine your protection sleeps with.

The honest limitation

No arrangement of this removes the gap. It only moves it.

Server-side protection can't act while it can't reach your account, and the reconnect behaviour described above is damage control rather than prevention. Terminal-side protection can't be taken down by a company's outage, and it also can't see a second account, can't span venues, and stops entirely when the machine does.

What actually reduces your exposure isn't picking a side. It's putting the protection that has to survive everything at the venue itself. A stop loss placed as a real order at your broker executes with nothing else in the world running, and it is the only layer with that property. Daily limits, account halts and kill switches all live somewhere that can be disconnected from.

Build with that ordering in mind and an outage is an inconvenience. Build without it and an outage is an open position with nothing watching it.

What to check on whatever you're using

Four questions, and any vendor should answer all four without hedging.

Where is the limit calculated? In my terminal, or on your servers.

What happens the moment you lose the connection? Specifically: does anything still open, and do my existing stops survive.

What happens to signals during the gap? Queued or discarded. Both are defensible. Not knowing isn't.

What happens on reconnect? Does it re-read my account from the broker, or carry on from what it last remembered.

A product that answers those clearly is telling you it has thought about the failure case. One that answers them vaguely is telling you something too.

Vectorhelm runs limits at strategy and account level on our side, across MT5 brokers and crypto exchanges in the same account view. That's why the disconnect behaviour above is written out rather than left off the page. It isn't open yet. Early access is here if you want it when it is.

Vectorhelm is execution software. It runs the rules you define on accounts you own and control. Nothing here is trading advice, and no configuration of risk limits prevents losses.