Start with the responsibility you want to automate
Automated trading software can mean a scanner that surfaces candidates, a strategy builder, an alert-to-order relay, an execution framework or a complete operated workflow. Comparing them only by monthly price can hide the most consequential differences.
This guide compares architectural categories and buyer questions, not a ranked list of brands. It is published by Automatic Day Trader, a software vendor, and explains ADT’s own boundaries openly. No competitor testing, independent certification or comparative performance result is claimed.
Compare the operating model
| Category | Typical responsibility | What the operator should establish |
|---|---|---|
| Scanner or research tool | Surface instruments, analysis or alerts | Whether it can submit orders at all; what happens after an alert |
| Alert-to-order relay | Translate an external signal into a broker request | Signal authentication, duplicates, sizing and responsibility for exits |
| Strategy builder | Let the operator define rules | Supported logic, testing assumptions and live execution differences |
| Developer framework | Supply components for custom systems | Engineering ownership, deployment, broker adapters and maintenance |
| Defined workflow application | Operate a specified research and execution process | Constraints, supported accounts, controls, recovery and operator duties |
Products may span categories. Ask for an end-to-end demonstration showing a decision, submitted order, fill, protection, exit and recovery. Establish which component owns each step instead of inferring it from a feature label.
Broker and instrument fit
Confirm the actual broker integration, API path, account eligibility, permitted instruments and order types. “Supports stocks” does not answer whether the system supports your venue, account, position size or preferred session behavior.
ADT currently integrates with IBKR through a local Gateway or TWS connection. Its workflow supports long-only eligible US stocks and broad ETFs, whole shares, and configured entry, concurrency and capital limits. Software scenarios cover up to 100 lifecycles; actual broker/data capacity is lower and must be rehearsed. It is not a multi-broker routing platform. The IBKR guide lists the connection requirements and limitations.
Ask whether the product is broker-endorsed only if a verifiable relationship is claimed. ADT uses the broker’s name to describe compatibility; it does not claim IBKR endorsement or certification.
State handling and recovery
Ask the vendor to explain a partially filled order, a restart after submission and a manual broker intervention. Useful answers identify what evidence is saved, how orders are matched and when the system blocks further activity.
Inspect the distinction between a connected socket and a reconciled account. Determine whether protection is held at the broker or monitored locally, what happens during an outage and how an operator verifies the result of a flatten request.
ADT’s reconciliation guide describes its approach. The risk-controls page shows the actual interface. Those mechanisms define behavior and limits; they are not guarantees against loss.
Testing and evidence
Separate a rendered demonstration, broker paper session, backtest and verified live record. They establish different things. Ask which software version, configuration, data and costs produced any reported result, and whether the method can be examined.
ADT’s public screenshots and walkthrough are actual UI with fictional fixture data. They show the product’s surfaces without implying a trading record. Paper rehearsal and live readiness are addressed during setup. No public returns, win rate or profitability claim is made.
Use a paper test matrix that includes failure cases. A polished interface is useful, but recovery evidence and understandable controls are also part of the purchase evaluation.
Local software versus a hosted service
Local operation places availability responsibilities on your computer, power, network and authenticated broker software. A hosted service moves some infrastructure responsibility to the provider, but introduces its own account access, availability and data-processing questions. Neither arrangement is automatically the correct one for every operator.
ADT uses a local service with a separate desktop interface. Closing the UI leaves the service running, while turning off the computer prevents local processing. Review the architecture and system requirements against the environment you can maintain.
For any service, ask where credentials are stored, what data leaves the machine, who can access the broker account and how to revoke that access. Do not send credentials to a sales inquiry form.
Compare the complete cost and agreement
Request a written breakdown of subscription or license charges, setup, support, updates, broker fees, data subscriptions, research usage and hardware. Determine whether one seat covers one machine, whether support has defined hours, and what cancellation or renewal actually changes.
ADT publishes its subscription and guided setup separately. Broker, data and research-provider charges remain customer-paid. The pricing page also identifies the workstation as a planned proposal, not a currently shipping offer. An access inquiry is not a purchase or a reservation.
Do not equate a perpetual license with lifetime hardware replacement, unlimited API costs, all future major versions or indefinite support unless the written agreement explicitly includes them.
A decision record worth keeping
Before choosing, write down the required instruments and broker, the workflow you intend to operate, the controls you need, unresolved test cases, total recurring dependencies and who handles an incident. Compare each candidate system against the same record.
ADT is a potential fit when its defined local workflow and IBKR integration match those requirements. It is not a fit for every strategy, broker or asset class. Review the product, operator documentation and commercial terms process, then request clarification about your specific environment.