TradeReign Tradovate Compatibility & Performance

TradeReign uses a Tradovate Custom App OAuth authorization flow. The trader signs in through the provider's authorization process and grants TradeReign access to the supported account workflow. TradeReign does not ask the trader to generate and paste a standard API key.

Broker authorization tokens stored by TradeReign are encrypted at rest. TradeReign also supports authenticator-app two-factor authentication for the TradeReign account itself. Broker availability, authorization, and permissions remain controlled by the relevant external provider.

TradeReign is designed for supported personal and prop firm accounts made available through the authorized Tradovate login. A prop firm's use of Tradovate does not automatically guarantee that every account type or permission set will be available to every third-party application.

Compatibility should therefore be verified with the actual account during TradeReign's trial. TradeReign is an independent software product and is not affiliated with, endorsed by, or sponsored by Tradovate or any prop firm. Provider access can change independently of TradeReign.

A Tradovate login may return more than one account, and TradeReign can load and switch among those accounts. Rules and monitoring state are scoped to the selected account and environment.

At present, one selected account per Demo or Live environment is actively monitored and enforced at a time. TradeReign does not synchronize one rule change across multiple copied evaluation accounts and is not a simultaneous multi-account trade copier.

TradeReign does not sit between the trading platform and Tradovate as an upstream order router. A trader's entry can reach the broker before TradeReign learns that it violates a configured rule.

After detecting supported prohibited activity, TradeReign can respond through actions such as canceling related working orders, closing or liquidating a violating position, restoring a protected stop or target, recording a violation, and maintaining a configured lockout. Because this process is reactive, temporary market exposure, price movement, partial fills, and slippage are possible.

An internal operational sample covered 58 TradeReign worker enforcement exits on connected Tradovate Demo accounts recorded from July 1 through July 27, 2026. The measured interval began when TradeReign sent the close command and ended when Tradovate acknowledged the request. The minimum was 65 ms, the median was 120 ms, the 90th percentile was 1.829 seconds, and the maximum observed outlier was 11.783 seconds.

That command-to-acknowledgement interval is not the same as the full violation-to-filled-flat interval. It excludes any time needed to detect and classify the violation before sending the command, and it does not guarantee when the market will fill an accepted order. A separate guarded Demo scenario recorded one prohibited entry detected and flattened in 878 ms end to end. These observations are test evidence, not an SLA or a promise of future performance.

Enforcement timing and availability can vary with Tradovate connectivity, WebSocket health, REST fallback, provider rate limits, cloud networking, market conditions, exchange state, account permissions, order status, and the specific rule's detection requirements.

TradeReign is an additional discipline layer, not a substitute for broker risk controls, exchange protections, prop firm rules, or responsible position sizing. Traders should not assume that software can eliminate all loss, latency, slippage, connectivity, or execution risk.