Live enablement is explicit
Paper and live settings are separate, and live operation requires a deliberate enablement step rather than simply connecting to a broker.
Trading software product
IBKR Trading Bot Engine for a Single Strategy
An IBKR-connected Trading Bot Engine for paper and client-controlled live order workflows, with configuration controls, recorded order states, and an operator dashboard.
Implementation scope
What this product implements
The build is intentionally scoped to one account and one strategy per deployment, making the configuration and operational boundary explicit rather than presenting a generic multi-tenant trading platform.
The service accepts API-key-authenticated signals, records the selected paper or live environment, and supports the agreed order types and time-in-force selections.
The operator interface includes separate paper and live settings, a persisted pause state, an emergency-stop control, recent-order views, and a broker-status snapshot that is refreshed manually.
Engineering choices
Clear boundaries in the application design
Failures remain visible
When a configured execution attempt fails, the order record can retain a FAILED state so an operator has a local event to investigate.
Operational controls are server-enforced
Pause and emergency-stop controls are part of the persisted runtime configuration rather than relying only on a dashboard toggle.
Validation approach
How the product can be reviewed
- Configuration can be reviewed without submitting a broker order, allowing the intended environment and run controls to be checked first.
- Paper-mode review supports the defined application workflow; broker connectivity and live order handling still require environment-specific validation.
Current boundaries
Important limitations
- The product supports paper and client-controlled live order workflows. Live operation is separately configured and deliberately enabled by the account holder; it is not enabled merely by connecting to IBKR.
- A working IBKR integration depends on TWS or IB Gateway connectivity. Fills, rejects, account synchronisation, and recovery from interruptions need environment-specific validation and operating procedures.
- The status view is manually refreshed, not a claim of continuous real-time account synchronisation. Paper verification checks defined software behaviour only; it does not establish profitability or future live results.
- Sun Cluster provides software engineering, not investment advice, brokerage, custody, or discretionary trading services.