What happens if AlgoProven is offline?

A fair question before you put anything near a funded account. The short answer: by design, an outage on our side can't stop your bot or move your account.

TL;DR — Read-only mode never sits on your order path, so if we're slow or down, your bot keeps trading exactly as it would without us. Guard mode uses a fallback you configure — continue, reduce, or halt — and that fallback is decided locally, with no call to us. AlgoProven holds no credentials and places no orders, so there is nothing on our side that can trap or drain your account.

By mode

READ-ONLY Default — tracking & decisions

We read account state and answer "can this trade pass the rules?". This lives beside your bot, never in front of its orders. If AlgoProven is unreachable, your bot never even notices — it sends orders through its own broker path as always. The only thing you lose during an outage is the live dashboard view and new audit records (which resume on reconnect).

GUARD Opt-in — acts only through your own bot

Guard mode can send a halt / flatten instruction to your own bot or authorized execution bridge when a rule is about to break. It never places orders itself. Because the action runs through your infrastructure, you decide what happens when our signal doesn't arrive:

CONTINUE

Bot trades on its own local risk rules — same as no AlgoProven.

REDUCE

Bot drops to a conservative size / tighter local cap until we're back.

HALT

Bot flattens & pauses on its own — the safest default for a strict account.

The fallback is evaluated on your machine, so it works even if our API is completely unreachable.

The order path never depends on us

your strategy → your bot → your broker   |   AlgoProven reads state + advises, beside the path — not in it

The synchronous check() call your bot can make before an order is built with a timeout + fail-open default: on any timeout or error it returns "no objection" and your bot proceeds on its own local rules. A rule check should only ever tighten risk — never add a new way to fail.

What about my audit trail?

Do I lose events during an outage?
Events that couldn't be written during an outage are simply not recorded — the audit() path is fire-and-forget and fail-open, so it never blocks or retries into your order path. Recording resumes automatically on reconnect.
Could an AlgoProven outage breach my account?
No — an outage removes a safety check; it can't create risk. Your bot's own stops and local limits are unchanged. For strict accounts, set Guard's fallback to HALT so "unsure" defaults to "flat".
Is this a guarantee my account won’t breach?
No. A rule check reduces preventable mistakes — it is not a guarantee against a breach, a loss, or a gap / slippage event, and it does not override your prop firm’s own enforcement. You stay responsible for your bot, your stops and your account. Rule data is illustrative and firms change rules often; see the risk disclosure.
Does AlgoProven ever hold my broker login or money?
Never. No credentials, no custody, no order placement on our side — see the security & architecture page.

A safety layer that can't become a liability

Because we sit beside your order path and never hold credentials, the worst case of an AlgoProven outage is "you're back to trading without us." Try the runtime on a chart you control.

More on trust: security & architecture · status · risk disclosure · terms