Strategy automation
Translate rules you supply into configured signals and order conditions. Review each trigger before deciding whether to use it with a live broker connection.
Broker connections with visible controls
Will your strategy reach your broker as intended?
Connect signals, order rules and broker responses in a workflow you can inspect before enabling live execution.
See the path from signal to order
A trading rule is only one part of an automated workflow. The broker connection must also handle authentication, instrument mapping, rejected orders and interruptions. Cabinetgrabs puts those steps where you can review them instead of treating a submitted order as the end of the story. Start with a strategy definition, test it against historical data, set execution limits and inspect broker responses. Live markets can behave differently from a test, and you remain responsible for deciding whether a strategy is suitable for you.
Who benefits from a visible broker workflow?
For you if…
You already have trading rules and want to examine how they become broker orders.
You need a record of rejected orders, connection changes and control-triggered stops.
You can review tests critically and supervise a live strategy.
Not for you if…
You want software to choose investments or design a profitable strategy for you.
You need a broker account, personalised financial advice or managed trading.
You cannot monitor your account or accept losses from market activity.
Want to compare plans before connecting?
Review the available tool limits and support options before discussing a setup.
View pricingFive parts of one trading workflow
Backtesting
Replay rules against historical data and examine assumptions, costs and periods that may change how a test reads.
Risk controls
Set order-size limits and stop conditions around execution. Controls can restrict actions, but they cannot remove market or technology risk.
Broker integration
Map the supported broker connection, account permissions and order responses so failures are easier to identify and investigate.
Monitoring
Inspect connection status, signals, orders and alerts in a dashboard designed for active supervision.
A successful connection test tells us that messages can travel. It does not tell us that a strategy will behave well when prices move, liquidity changes or a broker rejects an order.
Cabinetgrabs product team
From account check to supervised execution
Step 1
Describe your rules and identify the broker account, instruments and permissions involved. We check whether the proposed connection is supported before planning configuration.
Step 2
Configure signals, order mapping and limits in a test environment. Record assumptions that may affect the interpretation of historical data.
Step 3
Run tests and review order events, exceptions and control behaviour. Amend the configuration where the records reveal a mismatch.
Step 4
If you choose live use, enable the connection and monitor it. You can pause execution when conditions or your plans change.
During our setup, the order log showed that one instrument code did not match the broker's format. We corrected the mapping in the test environment before considering live execution. Seeing the rejected request alongside the signal made the issue straightforward to investigate.
Daniel Mokoena, independent trader