Four layers between your bot and a blown account

AlgoProven doesn't trade for you. It sits between your strategy and the prop firm's rule-set and makes sure a good system doesn't die on arithmetic. Here is exactly what each layer does.

Your bot / your handAlgoProvenBroker / prop firm
01

Rule engine, per firm

Every firm's rule-set modeled exactly — daily loss limit, trailing drawdown, consistency percentage, minimum days — and turned into a single number: your live distance to each breach.

Why it matters
Most algos fail on rule math, not strategy. A trailing drawdown moves with your equity; a consistency rule silently raises your target after a big day. You can't track that in your head.
How it works
We encode each firm's exact formula (Topstep, Apex, FundedNext…) and recompute distance-to-breach on every fill, so the bot always knows how much room it really has.
02

Pass-lock

The moment profit target + consistency + minimum-days are all satisfied, the cockpit flattens the account and halts trading. A pass you can't give back.

Why it matters
The cruelest way to fail is to hit the target on Tuesday and hand it back on Thursday. The math says you passed; the account says you didn't.
How it works
A continuous check on all pass conditions. When they go green together, flatten + halt fire automatically — before the next trade can undo it.
03

Guard layers

Independent safety rails that fire regardless of what the strategy wants: daily loss cap, second-trade guard after a losing leg, and disaster-stop supervision if a bot misbehaves or a position runs.

Why it matters
One wild gap, one stuck order, or one crashed bot can end an account in seconds. Strategy logic alone won't save you — you need rails that don't depend on it.
How it works
Enforced at the cockpit level, outside the strategy. If the daily cap trips, the second leg simply never opens — as shown live on the demo's down-day account.
04

Broker-truth accounting

Every trade reconciled to the cent against the broker fill and the broker's fee schedule — not the bot's own guess. The number that matters is the one the firm sees.

Why it matters
A bot that books the signal price is wrong by a few dollars on a good day and hundreds on a bad one. A breach is measured against broker P&L, so guessing in either direction is dangerous.
How it works
We pull the real fill and real fees, compute broker_net, and reconcile it against the bot's synthetic number. You can see this on our own live analytics.

Connects to your stack

Built around the futures prop ecosystem. Execution stays where it is — AlgoProven adds the rule layer on top via account data and webhook events, so it slots in next to an execution bridge rather than replacing it.

TopstepXRithmicTradovateProjectXWebhook in/out

Building an execution or automation product? The rule layer is complementary — let's talk integration.