Both products let you describe rules in words
NexusTrade stores a portfolio as explicit conditions and trading actions. Aurora can research a company, create the rules and submit historical backtests. A separate paper deployment records simulated behavior going forward. Python and TypeScript SDKs and MCP tools expose the same account workflow.
Capitalise.ai uses text to define automated trading strategies, including technical indicators, time conditions and repeated strategy loops. Its help material describes historical backtests, simulation and live execution. Tradable assets depend on the broker connection.
Compare what you need to build
| Authoring | Aurora conversation with an inspectable portfolio definition | Text-based strategy conditions |
| Evaluation | Historical backtests and forward paper observation | Backtesting and simulation described in the help center |
| Research context | Company research, disclosures and watchlists alongside rules | Evaluate the data and conditions offered by your broker-linked setup |
| Developer workflow | Python/TypeScript SDKs and MCP tools | Review current integration options for your broker and client |
No matching rows. Clear the filter to see all records.
Start with broker and instrument eligibility
Check Capitalise.ai current broker selection before building the rule. Its asset guide makes broker support part of instrument availability, so a rule that works for one connection may not transfer to another. In NexusTrade, inspect the selected broker capabilities and account approval for the asset you intend to trade.
Do not assume either product supports an account because it appears in an old comparison or tutorial. The current broker and asset documentation is the useful starting point.
Translate one rule before comparing charts
Write the instrument, entry condition, lookback period, position size, exit and evaluation timing without product-specific language. Build that definition in each product, then inspect how each handles repeat triggers, unavailable indicator values and a position already being open.
Align the historical period and simulation assumptions before comparing results. Capitalise.ai help material identifies backtest limitations around execution, slippage and fees; inspect the model rather than treating the curve as a live fill record.
Who each workflow may suit
Consider Capitalise.ai when your broker currently supports it and your priority is text-based rule automation in that connection. Consider NexusTrade when the work also needs company research, saved portfolio definitions or access from a coding assistant through MCP or an SDK.
Neither authoring style proves a strategy has an edge. The decision is whether the product can express and observe the rule you want to test.
Costs, account eligibility and comparison scope
Check the current subscription, compute charges, brokerage fees, supported country and account permissions for the workflow you intend to use. A platform capability does not establish that your account can trade a particular instrument.
This comparison describes workflows checked October 10, 2026. We have not run matched strategies or live accounts across the products, so it contains no ranking of returns, fill quality or execution speed.