Works with your stack

AlgoProven isn't another execution tool, copier or journal. It's the rule layer that sits in front of whatever you already use — deciding if the next trade is allowed before it's sent.

Your strategy / bot→ AlgoProven · ALLOW / BLOCK→ Your execution tool→ Broker
Execution suite

CrossTrade

Webhook automation + account manager for NinjaTrader 8 / Tradovate.

→ AlgoProven decides if the trade is rule-safe before CrossTrade sends it.
Webhook / copier

PickMyTrade · TradersPost

Route TradingView / signal webhooks to your broker.

→ Gate the webhook through AlgoProven first — block the ones that breach.
Trade copier

Tradecopia · Thor

Mirror trades across your funded accounts.

→ AlgoProven says which account should take it — not just copy into all.
Broker / platform API

TopstepX · Rithmic · Tradovate

The order path to your funded account.

→ Read-only account state in, rule verdict out — no credentials held.
Your code

Python bot

Three lines: ask the rule gate before every order.

→ pip install algoproven — see the gate.
Journals

TradesViz · TradeZella

Tell you what happened, after.

→ Complementary — they review; AlgoProven prevents.

The one-line difference

Execution tools send trades. Copiers duplicate them. Journals record them. AlgoProven decides whether the next trade is allowed under your exact prop-firm rules — and works alongside all of them.

Add the rule layer to what you already run

Keep your broker, your bot, your copier. AlgoProven just makes sure the next trade can't break the account.

How it works · Bot policy · Can I take this trade? · Embed the rule check