TradeOS / Bring Your Platform
Platform compatibility is earned through governed validation.
TradeOS follows a Bring Your Platform model. You retain your own broker or trading platform; TradeOS may use a governed connector or native add-on only after that platform passes its validation path. This directory is a readiness record, not a connection screen.
Current boundary
No platform is connected, supported, available for account linking, or released for read-only, paper, shadow, or live trading.
Priority paths
First-five platform readiness
Each capability below is a public declaration of what is and is not released today.
Validation focus: Owner-controlled TWS or IB Gateway read-only account, positions, orders, and health evidence.
Read-only prerequisite: Approved machine pairing, account allowlist, local emergency stop, fresh reconciliation, and verified local bridge evidence.
| Capability | Status | Declaration |
|---|---|---|
| Discovery / research | Directory available | The compatibility directory documents the governed validation path; it does not provide a platform connection. |
| Connector availability | unavailable | No governed Interactive Brokers connector or native add-on has been released. |
| Account linking | unavailable | Unavailable. TradeOS does not collect credentials, account identifiers, API keys, or OAuth material. |
| Read-only | unavailable | Not released. Any future read-only validation requires separate governed evidence and authorization. |
| Paper | unavailable | Not released. |
| Shadow | unavailable | Not released. |
| Live | unavailable | Unavailable. No live trading or order-routing capability is released. |
Validation focus: Controlled local NinjaTrader bridge health and read-only futures account snapshot.
Read-only prerequisite: Desktop bridge design review, owner-approved machine/account allowlist, and fixture conformance before any local connection.
| Capability | Status | Declaration |
|---|---|---|
| Discovery / research | Directory available | The compatibility directory documents a future validation path only. |
| Connector availability | unavailable | No governed NinjaTrader connector or native add-on has been released. |
| Account linking | unavailable | Unavailable. TradeOS does not collect credentials, account identifiers, API keys, or OAuth material. |
| Read-only | unavailable | Not released. Any future read-only validation requires separate governed evidence and authorization. |
| Paper | unavailable | Not released. |
| Shadow | unavailable | Not released. |
| Live | unavailable | Unavailable. No live trading or order-routing capability is released. |
Validation focus: Governed OAuth/API surface review followed by a controlled read-only futures account validation runner.
Read-only prerequisite: Approved provider OAuth lifecycle, encrypted local-or-server secret reference design, account allowlist, and conformance fixtures.
| Capability | Status | Declaration |
|---|---|---|
| Discovery / research | Directory available | The compatibility directory documents a future validation path only. |
| Connector availability | unavailable | No governed Tradovate connector or native add-on has been released. |
| Account linking | unavailable | Unavailable. TradeOS does not collect credentials, account identifiers, API keys, or OAuth material. |
| Read-only | unavailable | Not released. Any future read-only validation requires separate governed evidence and authorization. |
| Paper | unavailable | Not released. |
| Shadow | unavailable | Not released. |
| Live | unavailable | Unavailable. No live trading or order-routing capability is released. |
Validation focus: Controlled local MT5 bridge health and read-only account/position snapshot.
Read-only prerequisite: Terminal bridge architecture, machine/account allowlist, broker-specific symbol mapping, and fixture conformance.
| Capability | Status | Declaration |
|---|---|---|
| Discovery / research | Directory available | The compatibility directory documents a future validation path only. |
| Connector availability | unavailable | No governed MetaTrader 5 connector or native add-on has been released. |
| Account linking | unavailable | Unavailable. TradeOS does not collect credentials, account identifiers, API keys, or OAuth material. |
| Read-only | unavailable | Not released. Any future read-only validation requires separate governed evidence and authorization. |
| Paper | unavailable | Not released. |
| Shadow | unavailable | Not released. |
| Live | unavailable | Unavailable. No live trading or order-routing capability is released. |
Validation focus: Controlled API surface review followed by an owner-approved read-only account and reconciliation validation runner.
Read-only prerequisite: Scoped credential-reference design, account allowlist, rate-limit policy, and fixture conformance.
| Capability | Status | Declaration |
|---|---|---|
| Discovery / research | Directory available | The compatibility directory documents a future validation path only. |
| Connector availability | unavailable | No governed Alpaca connector or native add-on has been released. |
| Account linking | unavailable | Unavailable. TradeOS does not collect credentials, account identifiers, API keys, or OAuth material. |
| Read-only | unavailable | Not released. Any future read-only validation requires separate governed evidence and authorization. |
| Paper | unavailable | Not released. |
| Shadow | unavailable | Not released. |
| Live | unavailable | Unavailable. No live trading or order-routing capability is released. |
Request discipline
Platform-request intake is not released.
A secure governed intake has not been released. TradeOS will not store a platform request until it can record only a platform name and high-level use case safely.
Never send credentials, account numbers, API keys, OAuth codes, or sensitive financial information to TradeOS through this page.
The future intake scope will be limited to a platform name and high-level use case. Submission remains disabled until the governed storage path exists.
Authorized internal users
The broker-readiness workbench remains a read-only, fixture-only validation context. It does not connect a platform.