Editorial comparison
TradersPost vs Capitalise.ai: signals, rule writing and account access
Compare external signal routing with plain-English strategy creation, check current Capitalise.ai onboarding routes, and plan testing, costs, monitoring and shutdown.
Choose where you want the trading rules to live
Assess TradersPost when you already have a source producing entry and exit signals. Its configuration determines how those signals become orders in a connected account. Capitalise.ai provides a plain-English strategy wizard with testing and execution modes. It also documents TradingView alerts as conditions, so the choice need not be between charts and written rules.
The useful question is where you want to maintain the logic. If a script already defines your strategy, copying its conditions into another wizard creates another version to check. If English rules suit your process, establish whether the wizard interprets them correctly and whether the selected account permits execution.
Define the instrument, quantity and exit first. A system accepting sentences or JSON still needs an unambiguous instruction. Easier rule entry does not establish profitability or suitability for your risk limits.
What the Kraken acquisition establishes
Kraken announced the acquisition of Capitalise.ai's assets and technology in August 2025 and described a future phased rollout within Kraken Pro. That announcement does not establish that rollout is complete or that your account currently has the capabilities it discussed.
The practical checks are the current onboarding route and the controls in the specific account. Avoid opening an exchange account solely on a historical integration promise. Identify the active product, execution permission and available tools before transferring a strategy.
A broker appearing in an older tutorial or glossary is also insufficient evidence of current onboarding for new customers. Start with the current directory and the wizard for the broker route. Historical partner lists can help frame a support question; they cannot authorize a connection.
The onboarding directory separates analysis from execution
Capitalise.ai's public directory labels CFI, FXCM and Interactive Brokers for analysis, signals and execution. Fidelity is labelled for analysis and signals, without execution. The Interactive Brokers route directs users to subscribe through the IB client portal. These are descriptions of public routes, rather than confirmation that a particular signup or account link succeeded.
Scroll the table horizontally to read every column.
| Check |  TradersPost | Capitalise.ai |
|---|---|---|
| Rule source | External system's signal | English rules or webhook conditions |
| Execution link | Account connector and strategy subscription | Broker route that enables Execution |
| Testing without live funds | Built-in Paper or suitable paper connection | Backtest or Simulate within route scope |
| Options and equity futures | Connector and asset dependent | Unsupported in the asset guide |
| Customer acceptance | Account provider's decision | Account provider's decision |
Reading an English or Hebrew comparison does not establish residence acceptance, permissions or availability.
Filter by instrument before comparing price
Capitalise.ai's asset guide limits the stock category to US equities and ETFs. It also lists FX, CFDs, cryptocurrencies and perpetual futures, depending on the broker, and excludes equity futures and options. A crypto perpetual and an exchange-traded equity futures contract are different products despite both sometimes being described as futures.
For TradersPost, check the connector's asset support, the selected account and that account's permissions. Connecting a stock account at a broker offering futures does not guarantee orders reach the appropriate futures account. A broker's overall product catalogue may be broader than its automation connector.
Before authoring a strategy, record the exact symbol, venue, account type and required actions: entry, exit and any quantity adjustment. If the connection misses a required action, a lower software bill cannot resolve the mismatch.
Test rule meaning before testing returns
In Capitalise.ai, define entry and exit conditions in the wizard and deliberately choose Backtest, Simulate or Live. Backtest uses historical data; Simulate runs against current conditions without committing live funds; Live activates the execution route. Read the resulting rule and confirm its timing, quantity and exit match your intention.
With TradersPost, have the signal source represent the same conditions, then inspect what the subscription will send to the account. Distinguish a quantity included in the signal from a subscription default. If both are involved, write down which setting should determine actual size and verify it in demo.
Do not compare strategy returns between experiments that use different data feeds, bar-confirmation times, trading sessions or execution costs. Begin with the sequence of events. Once entries and exits occur in the intended order, investigate differences in results. This is a proposed verification process; we did not run a strategy for this article.
Also distinguish a condition remaining true from a crossing event. Write what should happen if price stays on one side of a threshold for several bars, and what follows an exit when that condition still holds. Compare the wizard's event sequence with the signal source's sequence. A wording difference can change the number of entries even if quantity per order stays constant.
A TradingView combination needs clear ownership of exits
Capitalise.ai can use a TradingView webhook as a condition. You can retain a chart-based trigger at the source and assign another part of the process to the automation service. TradersPost interprets external signals through strategy and subscription settings. In either route, establish which component decides the exit so competing systems do not send conflicting instructions.
For a design exercise, list who produces each event, who receives it and the account state expected afterwards. Include a late signal and a duplicated message. Determine whether a condition remaining true begins another cycle or waits for a new event. Capitalise.ai's Once and In Loop choice matters here.
Do not paste a TradersPost payload into a Capitalise.ai field. Use the format generated or documented for the destination and recheck its target identifier after changing a strategy. Keep webhook destinations and keys private rather than adding them to a shared working log.
Total cost depends on the account route
Capitalise.ai's public directory describes signup as free without requiring a trading account. That does not establish that every execution route, market-data entitlement or broker charge is included. Check the selected route and the order confirmation or broker portal.
TradersPost prices capacity by accounts and asset classes, and live automatic submission has different scope from paper testing. Use the plan guide to define required capacity, then check the actual billing period. This comparison does not quote a personal account tariff or declare either product universally cheaper.
Add signal-source, data and brokerage charges. Separate fixed costs from charges dependent on trading activity. If you require an external webhook source, include it too. Rule testing and incident monitoring also consume time, even though there is no fixed monetary amount we can responsibly assign to that work.
An incident procedure and a shutdown procedure are different
When an order is missing, establish whether the condition triggered, inspect the automation event and then check the execution account. A successful signal is not a broker fill. Assign an incident owner, specify the evidence to retain and decide how to prevent fresh entries while account state is being investigated.
In Capitalise.ai, Stop includes a choice about existing exposure. The documented default closes associated positions and cancels pending orders. Selecting Keep open positions and pending orders leaves them for management through the trading account; the strategy stops managing them and cannot be restarted. Changing In Loop to Once waits for the next exit, then finishes.
Read the confirmation before stopping and inspect the broker afterwards. If the intention was to block new entries while preserving a protective order, verify what remains active. Revoking the connection is a separate step after deciding who will manage exposure.
Questions that settle the choice
Can Capitalise.ai strategies be written in Hebrew?
The reviewed workflow documents English rules. This does not establish Hebrew strategy syntax. Check how the wizard interprets your sentence even if the original idea was expressed in Hebrew.
I have Fidelity. Can every signal become an order?
The public directory labels that route for analysis and signals without Execution. Do not rely on automatic order placement without explicit current confirmation from the product and broker.
Does the Kraken acquisition guarantee access to every Kraken asset?
The acquisition announcement described a plan. Current account capability needs separate verification. The announcement does not establish that every asset type or service is already available.
How do I choose if both routes support my account?
Define one entry-and-exit test, then compare sizing, logs, stopping behaviour and the effort needed to maintain rules. The automated trading guide expands the operating process. For an MT5 account, read the PineConnector comparison. For an existing signal-routing need, begin with the TradersPost overview.
