Choose an authorized signal source and an execution route. Each destination below links to its setup, device requirement, supported lifecycle, and current limitations. The dependency register then shows what cannot be completed by code alone.
Execution destinations
Supported describes the route—not universal broker compatibility. Limited and beta routes must pass the full lifecycle on the exact demo account.
EA on your PC/VPS or eligible Cloud provider
Open route detailsEA, Desktop bridge, or eligible Cloud provider
Open route detailsLocal beta cBot; Cloud unavailable / unverified
Open route detailsCloud public-API adapter; broker validation required
Open route detailsDesktop plus local Client Portal Gateway
Open route detailsCloud market entry with one TP and hard USDT cap
Open route detailsCloud market entry with one TP and hard USDT cap
Open route detailsSignal inputs
External dependency register
4
Need credentials / sandbox
2
Need vendor access
4
Need outside validation
1
Explicitly not promised
execution
No production connector. DXtrade availability depends on the broker or prop firm exposing API access.
A sandbox lifecycle test and a named supported broker move this route to beta.
Official access sourceexecution
No production connector. The platform publishes trading APIs, while access and enabled functions remain broker/server specific.
Broker-sanctioned demo credentials and a recorded order lifecycle move this route to beta.
Official access sourceexecution
Official REST Trade API and NinjaScript surfaces exist; TradeJournal Pro has not connected or certified one yet.
Simulation-account order, modify, partial fill, cancel, and close tests move this route to beta.
Official access sourceexecution
Official REST/WebSocket and OAuth paths exist; no TradeJournal Pro connector is deployed.
OAuth review plus a demo lifecycle test moves this route to beta.
Official access sourceexecution
ProjectX publishes a Gateway API, but TradeJournal Pro has no approved user credentials or production connector.
A named firm, sanctioned test account, and recorded full lifecycle move this route to beta.
Official access sourcedistribution
CI requires a valid Authenticode signature on the app and installer unless a release is explicitly marked unsigned, and always publishes versioned and stable SHA-256 files. No publisher certificate has been supplied yet, so current installers are unsigned and Windows shows an Unknown publisher warning.
Windows shows a verified publisher, CI verifies the signature, and both published SHA-256 sidecars match.
distribution
Native wrappers are not described as store-approved until the stores complete review.
A public listing from the relevant official store.
trust
Internal tests and hardening are not an independent audit or penetration test.
A report or attestation issued by the independent assessor, with scope and date.
evidence
Generic MT4/MT5 paths compile and are tested, but every broker has its own symbols, limits, filling modes, and account rules.
A dated lifecycle receipt for the exact broker/server/account mode.
evidence
No quotes, returns, or identities are invented. Real review widgets remain empty until customers submit reviews.
A review on an independent platform or a consented, attributable case study.
execution
The shipped IBKR route uses the official local Client Portal Gateway and therefore needs a running, authenticated device/session.
A separate IBKR-approved server-side integration—not a workaround around Gateway login or 2FA.
Official access source