TL;DR
StockHero allocates capital through a base order and extra orders within a deal; NexusTrade actions specify cash, buying power or units and can reference selected fills. Match those rules and exit priority before comparing strategies. The October 13, 2026 free StockHero signup reached the builder and test controls, but no accepted or completed run was verified. The page's NexusTrade cooldown result is a separate demonstration, not a paired performance test.
Compare the bot setup with an editable portfolio
NexusTrade also has a native visual condition builder, strategy discovery and a paper-copy workflow. Its marketplace supports portfolio filters and comparison, while the saved rule view displays nested conditions. StockHero's bot setup and these NexusTrade controls are both visual workflows. The incomplete StockHero run above leaves their relative setup time and result quality unmeasured.
Work through StockHero’s documented $10,000 bot allocation
Show the table · 3 rows, 3 columns
Scroll sideways to compare all columns. Select a heading to sort.
| Fund allocation | $10,000 | Capital allocated to this bot |
| Base order limit: 20% | $2,000 | First order in the deal |
| Two extra orders | $4,000 each | Remaining $8,000 divided equally |
No matching rows. Clear the filter to see all records.
Arithmetic from StockHero’s terminology example. These are configured amounts before actual fills, fees and market movement.
A bot can add trades within one deal before its exit completes the deal. Compare this allocation with the exact units in a NexusTrade action: percent of current buying power, cash amount or units. Equal-looking percentages can produce different order quantities.
We reached the free builder, but did not verify a completed test
Show the table · 6 rows, 2 columns
| Step | Observed free-account workflow |
|---|---|
| Register | No-card signup succeeded; the account opened with $10,000 paper cash. |
| Choose a manual strategy | Exited the welcome wizard, then Create New Bot → Create my own bot → Simple. Other choices were marked Premium or Pro. |
| Select the instrument | Looked up SPY and selected SPY/USD, excluding SPYG/USD. |
| Configure sizing and costs | $10,000 allocation, 100% static base order, zero extra orders, zero transaction fee. |
| Inspect the test controls | Run Backtest appeared before bot creation; date presets included 3M, and Summary/Trades tabs were visible. |
| Attempt the run | Clicked the enabled control with an RSI entry and 5% take-profit/stop-loss. No accepted run, finished curve, trade ledger or visible error was verified. |
No matching rows. Clear the filter to see all records.
Actual manual Simple-bot workflow observed October 13, 2026. The draft retained its 15-minute default. Exact dates and RSI period/threshold were not confirmed, so this is an incomplete attempt rather than a reproducible backtest.
StockHero made its five setup stages visible: Asset, Trade Parameters, Entry Conditions, Exit Conditions and Create Bot. We reached historical-test controls without saving or activating a bot. A visible control did not establish a completed free test in this attempt.
StockHero'sbacktesting guide places custom historical date/time controls on Professional. The free builder we inspected exposed date presets. That matters when your experiment requires the exact January 2 to March 20 window.
The unresolved test action establishes neither a speed comparison nor a missing feature. A matched January 2 to March 20 experiment would still need exact dates, equivalent entry rules and a returned report. No bot, broker connection or trading activation was used to overcome this unresolved step.
Separate live bot frequency from historical replay data
Show the table · 4 rows, 3 columns
Scroll sideways to compare all columns. Select a heading to sort.
| Historical run | Minute or Day with explicit dates and completed history. | Historical backtests with preset windows; Professional supports custom date/time selection. |
| Live evaluation frequency | Deployment timing is a separate configuration from historical interval. | Professional Advanced Bots document one-minute trading frequency and extended hours. |
| Condition logic | Nested conditions can use market inputs and selected previous order events. | Multiple AND/OR entry/exit indicators, extra-order behavior and trailing exits are documented. |
| Paper inspection | Inspect the paper portfolio’s own orders and history after deployment. | Paper exchange starts with a $10,000 virtual wallet and simulated market execution. |
No matching rows. Clear the filter to see all records.
Reviewed October 13, 2026. StockHero’s live one-minute feature does not by itself establish historical data granularity or fill equivalence.
StockHero is more than a single-trigger bot. Its Advanced Bots include active trailing and minimum profit for an indicator-triggered exit. Match those settings and exit priority when translating a strategy. Take Profit and Stop-Loss have precedence over indicator-based exits in its setup guide.
Test an explicit previous-fill cooldown
Show the table · 3 rows, 4 columns
Scroll sideways to compare all columns. Select a heading to sort.
| 29 days after a matching $100 buy fill; current price $94 | No | Yes | No |
| 31 days after that fill; current price $96 | Yes | No | No |
| 31 days after that fill; current price $94 | Yes | Yes | Yes |
No matching rows. Clear the filter to see all records.
Constructed rule worksheet, not a recorded stock trade or matched StockHero run. First-entry and no-matching-order behavior need their own policy.
In NexusTrade, select the same asset, Buy side and Filled status for DaysSinceOrder and LastOrderPrice. The first reads elapsed calendar time from the fill timestamp; the second reads its filled price. This is an explicit order-event reference, separate from an indicator rebound or trailing-stop setting.
StockHero documents its own active-trailing reset behavior. Require an equivalent rule and its evaluated result before treating that behavior as the same cooldown. Its deal-level state and a selected prior filled-order event can represent different histories.
Inspect a completed stock cooldown test
Show the table · 4 rows, 2 columns
| Actual October 7 through 9, 2026 stock test | Returned result |
|---|---|
| Saved entry | $1,000 of SPY when DaysSinceOrder >= 1, restricted to Buy and Filled. |
| Requested interval / saved cadence | Minute / every 60 seconds |
| Status / retained history | COMPLETE / 51 stored hourly observations, not every evaluated minute |
| Ending NAV / fees / closed trades | $10,008.399 / $3 / zero closed trades |
No matching rows. Clear the filter to see all records.
Actual Claude Code execution captured October 13. A three-day order-state example; it does not validate future performance or an additional LastOrderPrice condition.
Claude Code created the inactive strategy, set its cadence, submitted one accepted test and read the completed result. The retained receipt records cash and position values separately. Inspect that actual output before adding the price condition from the constructed worksheet.
The longer five-dividend-growers example supplies a separate screen and full recorded historical curve. Its rebalance also references a filled-buy cooldown. Audit its original input vintages separately from the strategy narrative. Neither example is a matched StockHero bot test.
Compare filled trades and costs during paper testing
For StockHero web paper testing, its guide locates virtual funds in Settings > Paper Wallet; the mobile guide uses Portfolio. Retain the paper deals and trades before changing the strategy. Its documentation distinguishes filled and partially filled quantities.
For NexusTrade, inspect the deployed paper portfolio’s own history and orders. A new historical backtest starts from its specified balance and modeled fills, so it cannot substitute for observing what the paper portfolio actually did.
Show the table · 4 rows, 2 columns
| Keep in your test record | What to verify |
|---|---|
| Capital and order units | Allocated funds, first order, extra orders, fractional quantity and remaining cash. |
| Rules and priority | Entry, re-entry/reset, trailing settings, minimum profit, stop and exit precedence. |
| Timing and fills | Decision time, selected input value, submitted order, completed fill, fill price and quantity. |
| Costs and selection | Commission/spread assumptions, original configuration and a later unselected period. |
No matching rows. Clear the filter to see all records.
Paper-review specification. The page performs no bot deployment, brokerage order or paired performance test.
Choose the workflow, then inspect one exact rule
Inspect the request
Choose StockHero when its base/extra-order stock bots, advanced trailing settings and brokerage workflow fit your plan. Choose NexusTrade when you want selected fill-state conditions connected to research inputs, saved configuration, historical results and retained condition audits.
Connect Claude Code and inspect the saved example before approving any new run. Detailed NexusTrade event generation costs 5 times the normal research tokens; the traces are retained for 3 days. Account changes and simulations need explicit scope.
No comments yet.