Broker integrations and execution flow

What this page explains

This page is meant to clarify how FlyTradr thinks about broker integrations without overstating live availability. The platform separates strategy validation from execution and treats broker connectivity as a later-stage workflow, not the starting point.

FlyTradr is not the broker

FlyTradr does not replace the broker account itself. It helps users build, test, simulate, and paper trade strategies, then connect those strategies to supported broker workflows where configured. Public messaging should remain precise: broker, country, market, and mode availability can vary by release status and integration maturity.

The staged broker workflow

1. Build the strategy visually.
2. Backtest on historical data.
3. Simulate difficult periods and review assumptions.
4. Paper trade with virtual capital.
5. Only then move toward broker-connected execution where supported.

Connection model

• Users add broker credentials through a dedicated connection flow.
• Credentials are encrypted before storage.
• Connections can be tested before session launch.
• Live workflows rely on logs, risk events, and kill-switch-oriented controls for operational visibility.

Availability guidance

Some broker connectors may be production-ready, some may be feature-gated, and some may still be scaffolded or in progress. This page should not be read as a guarantee that every named broker, market, or mode is universally available to every user at every time.

Why this matters

Many trading tools collapse strategy creation and execution into one marketing promise. FlyTradr is stronger when it explains the transition honestly: build first, validate carefully, then move toward broker-connected execution only when the workflow and risk discipline justify it.

Educational note: broker-connected execution does not remove market risk, slippage, or integration constraints. It is the final stage of a validation workflow, not a shortcut around it.