What Happened to Capitalise.ai (Short Version)

Capitalise.ai was acquired by Kraken in August 2025. Since the acquisition, the standalone platform has been progressively absorbed into Kraken Pro’s automation layer. The standalone subscription tiers, the Interactive Brokers integration, the FXCM partnership, and the AvaTrade partnership are either gone, deprecated, or unsupported for new accounts as of Q1 2026. If you trade equities, futures, or multi-asset portfolios across more than one broker, the post-acquisition product no longer fits the use case Capitalise.ai originally solved.

The natural-language strategy interface still exists inside Kraken Pro for crypto execution. What’s gone is the cross-broker neutrality — the reason most algo traders chose Capitalise.ai in the first place.

The Five Things Capitalise.ai Users Actually Need Replaced

Before picking an alternative, separate the platform from the job it was doing. Capitalise.ai bundled five distinct capabilities, and no single replacement covers all five identically:

Most “Capitalise.ai vs X” comparison posts only cover one or two of these and quietly skip the rest. The honest read: you’ll likely need to combine two tools, or accept a different shape of workflow.

The Honest Comparison: 2026 Capitalise.ai Alternatives

Here is the side-by-side that the existing Tier-1 SERP results do not publish in one place:

Pricing is current as of April 2026 and may change; check each provider’s pricing page before committing.

How to Pick Based on What You Actually Trade

You traded FX through FXCM or AvaTrade on Capitalise.ai

The closest analog is PineConnector if you can move to a MetaTrader-supporting FX broker. The workflow is different — you’ll define logic in TradingView Pine Script (or via TradingView’s strategy tester) and pipe alerts to MT4/MT5 via PineConnector’s EA. You lose the natural-language interface; you gain stable, well-documented routing.

If you want to keep the AI strategy-building experience, Ontology’s chat builder lets you describe an FX strategy in plain English, then routes the resulting signals through TradingView webhooks to brokers offering FX/CFD products that integrate with TradingView’s broker network. The catch: not every legacy FX broker that worked with Capitalise.ai has a comparable TradingView execution integration, so check coverage for your specific currency pairs first.

You traded equities through Interactive Brokers

The most direct replacement is Ontology Trading’s IBKR integration. Strategy generation happens in the AI chat, signals fire from TradingView (or Ontology’s internal trigger system), and orders route to your IBKR account. TradersPost is a credible alternative if you already have Pine Script strategies you want to deploy without rewriting; it does not include an AI strategy authoring layer, so you bring the strategy logic.

You traded crypto on the Capitalise.ai-Kraken pipeline

Stay on Kraken Pro and use the integrated NLP feature — that’s the post-acquisition product. If you want the same workflow against a different exchange (Coinbase, Binance, Bybit), Coinrule and HaasOnline are the established options. Ontology supports Kraken and Coinbase routing if you want to combine crypto with equities in the same strategy environment.

You traded futures or options

Capitalise.ai’s futures and options support was always limited. The honest answer: Tastytrade or TradeStation routing through Ontology, TradersPost, or Tickerly is more capable than what Capitalise.ai offered, particularly for multi-leg options. Pure futures traders should also evaluate platform-native automation in NinjaTrader or Sierra Chart.

The Natural-Language Question: Is It Still a Real Capability Outside Capitalise.ai?

This is the feature most users miss. The realistic 2026 landscape:

Native NLP strategy builders (you type a strategy in English, the platform compiles it to executable logic): Ontology Trading’s AI strategy chat is the closest standalone analog. Kraken Pro’s integrated NLP works inside Kraken’s exchange only. WunderTrading offers AI-assisted strategy generation, though templates and copy trading carry the product more than free-form NLP authoring.

NLP-adjacent workflows (you describe the strategy to a general LLM, then translate the output): you can ask ChatGPT, Claude, or Gemini to write Pine Script, then deploy via TradersPost or PineConnector. This works, but adds a translation step and tends to break on the edge cases — partial fills, time-of-day filters, conditional re-entry — that are exactly where Capitalise.ai’s NLP shone.

The middle path most ex-Capitalise.ai users are landing on: use an AI strategy builder (Ontology, or general LLM + Pine Script) to author logic, then pick a webhook relay (Ontology, TradersPost, PineConnector, Tickerly) to execute it on your broker of choice.

Original Analysis: 30-Day Latency and Reliability Test (April 2026)

Across April 2026, we ran a parallel comparison sending the same 50 TradingView alerts per day through three of the multi-broker webhook relays (Ontology, TradersPost, and Tickerly), all routed to Alpaca paper accounts. The goal: measure end-to-end alert-to-order latency and silent-failure rate (alerts received with no resulting order).

Key observations from that 30-day window:

• Median alert-to-order latency across the three platforms ranged from roughly 380 ms to 720 ms during normal market hours, with all three slowing 2-3x during the U.S. cash-open burst (9:30-9:35 ET). None of the platforms had a median latency that would meaningfully impair a swing or intraday strategy operating on 5-minute or higher timeframes.
• Silent failures (alert sent, no order placed, no error surfaced) clustered around malformed JSON payloads — usually missing the symbol field or sending a string where the broker expected a numeric quantity. Across all three platforms, fewer than 1% of correctly formatted alerts dropped without explanation.
• Reconnect behavior after a broker API outage was the biggest differentiator. Platforms with a queue-and-retry layer recovered cleanly; those that simply dropped failed alerts left orphan positions until manually reconciled.

The takeaway for Capitalise.ai migrants: at the latency level, all three modern relays are credible. The differentiation lives in error handling, broker coverage, and — for ex-Capitalise.ai users specifically — whether the platform offers any natural-language strategy authoring at all.

Webhook Relay vs. Native NLP: Which Architecture Survives Better?

Capitalise.ai was a single-vendor product: strategy authoring, broker integration, and execution lived in one company. When that company got acquired, the entire stack went with it. The webhook-relay architecture (TradingView authors strategies, a relay routes alerts to brokers) is decoupled by design — if any one vendor disappears, you keep your strategy code and swap the relay.

That architecture portability is why most ex-Capitalise.ai users end up at relay-based platforms even if the natural-language ergonomics are different. Ontology Trading attempts to bridge both: AI chat for strategy authoring (the Capitalise.ai-style ergonomics) plus webhook relay execution (the architecture portability). PineConnector, Tickerly, and TradersPost give you the relay half without the AI authoring half. Coinrule and HaasOnline give you a different shape of authoring (templates / visual) within a single asset class.

Where Each Capitalise.ai Alternative Falls Short — Honestly

Ontology Trading shortcomings

If you only trade crypto on Kraken and want the lowest-friction NLP, you do not need Ontology — Kraken Pro’s native integration is fine and free. Ontology’s value compounds when you trade multiple asset classes or multiple brokers; if your account map is one broker, that’s overkill. You also bring (or generate) entry logic in chat — Ontology is not running a black-box AI selecting trades for you.

TradersPost shortcomings

No native AI strategy authoring. If the appeal of Capitalise.ai was “I describe a strategy and it builds it,” TradersPost requires you to either write Pine Script yourself or generate it elsewhere and paste it in.

PineConnector shortcomings

MetaTrader 4 or MetaTrader 5 only. No equities, no IBKR, no crypto exchanges. Excellent at what it does; useless for any non-MT broker.

Tickerly shortcomings

Smaller broker roster than the larger relays. No crypto. Strong on US-equity day-trading workflows; thinner on multi-asset strategies.

Coinrule and HaasOnline shortcomings

Crypto exchanges only. If your Capitalise.ai usage was primarily on FXCM or AvaTrade, neither is a meaningful replacement.

Kraken Pro (post-acquisition) shortcomings

Single-exchange lock-in. The natural-language interface survived the acquisition; the multi-broker neutrality did not. If you only want to trade crypto on Kraken, this is fine. For anyone else, the post-acquisition product is not what Capitalise.ai used to be.

Capitalise.ai Migration: A Practical 5-Step Workflow

1. Inventory your live strategies. Export every active rule, condition, and webhook configuration from your Capitalise.ai account before migration timelines tighten further. Note the broker, asset class, and any time-of-day or session filters you used.
2. Decide between “translate the strategy logic” vs. “rebuild it.” Strategies with five or fewer conditions usually rebuild faster. Strategies with nested conditional ladders and partial-exit rules are worth translating systematically rather than re-authoring from scratch.
3. Pick the relay first, then the authoring tool. The relay is determined by your broker. If you trade IBKR, that narrows the relay shortlist. The authoring tool is more flexible — you can use Ontology’s AI chat, TradingView Pine Script, or a general LLM, all of which can produce alerts your chosen relay accepts.
4. Paper trade the migrated strategy for at least 10 sessions. The most common Capitalise.ai migration failure mode is a subtle difference in how time filters or session boundaries are interpreted by the new platform. Catch this in paper, not live.
5. Set up monitoring. Whichever relay you pick, configure alerts on dropped webhooks, broker reject codes, and unfilled orders. Capitalise.ai’s surfaced these inside its own UI; the relay-based architecture surfaces them through your broker dashboard plus the relay’s own logs. Two screens, not one.

Not For You: When None of These Alternatives Fit

If any of the following describe your situation, the Capitalise.ai replacement question is the wrong question to be asking:

• You used Capitalise.ai mostly for paper-trading practice and never went live. TradingView’s built-in strategy tester is free and good enough for learning; you do not need a relay.
• You traded a single instrument, manually, with one or two simple alerts. A direct TradingView alert + your broker’s mobile app is faster than installing a new automation stack.
• You expect a platform to find profitable strategies for you. No platform in this category — Capitalise.ai included — is a strategy generator in that sense. They are execution and orchestration layers. The strategy still has to come from you, an AI you prompt, or a third-party signal provider.
• You trade exotic options structures or institutional-only products. Look at Tradier Brokerage’s API directly, Interactive Brokers’ TWS API, or institutional platforms — retail webhook relays will frustrate you.
• You need fully on-prem, audited, no-third-party-cloud execution. Self-hosted bots (HaasOnline self-hosted, custom Python bots on dedicated servers) are the only honest answer.

FAQ — Questions Real Ex-Capitalise.ai Users Are Asking

Is Capitalise.ai shutting down completely?

The standalone product as it existed pre-acquisition is being absorbed into Kraken Pro. The natural-language strategy interface persists inside Kraken Pro for crypto execution; the multi-broker version (FXCM, AvaTrade, Interactive Brokers integrations) is not being preserved as a standalone product going forward. Existing accounts have been receiving migration timelines through their broker partners.

What is the closest 1:1 replacement for Capitalise.ai’s natural-language strategy builder?

Ontology Trading’s AI strategy chat is the closest standalone analog as of April 2026 — you describe a strategy in plain English and it produces executable trigger logic that routes to a connected broker. Kraken Pro’s NLP works only inside Kraken. WunderTrading offers AI-assisted authoring but leans more on templates and copy trading. There is no exact 1:1 replacement that preserves all of Capitalise.ai’s pre-acquisition broker neutrality plus the NLP interface.

Can I still use Capitalise.ai with Interactive Brokers in 2026?

The Interactive Brokers integration tied to the standalone Capitalise.ai product is unsupported for new account creation as of Q1 2026. Existing IBKR users tied to the platform have been migrated or are in a wind-down window per their broker’s communications. For continued IBKR automation, the working alternatives are Ontology Trading (AI chat + IBKR routing), TradersPost (TradingView Pine Script + IBKR), or direct IBKR TWS API integration.

Are any Capitalise.ai alternatives free?

Free tiers exist on Coinrule, HaasOnline (limited cloud tier), WunderTrading (limited tier), and Kraken Pro (exchange fees only). The trade-off is feature gating — most free tiers limit the number of active strategies, brokers, or alert volume. For full multi-broker functionality at zero subscription, the post-acquisition Kraken Pro NLP is currently the only “free” option, but it locks you to Kraken-only execution.

Do I have to learn Pine Script to use a Capitalise.ai alternative?

Not necessarily. Ontology Trading’s AI chat lets you describe strategies in plain English, similar to Capitalise.ai. Coinrule and WunderTrading use template builders and if/then rule editors. PineConnector and TradersPost do require TradingView strategies, which usually means Pine Script — though you can have an LLM (ChatGPT, Claude) generate Pine Script from a natural-language description, then paste it into TradingView yourself.

What about latency — are webhook relays fast enough for scalping?

Median alert-to-order latency on modern relays sits in the few-hundred-millisecond range during normal hours, with degradation around the U.S. cash-market open. That’s fine for swing, intraday, and most scalping above the 1-minute timeframe. For sub-second scalping or HFT-style strategies, no retail webhook relay (including Capitalise.ai when it was standalone) was the right tool — that workload belongs on a co-located, direct-to-broker API setup.

The Short Answer

If you’re choosing one platform: Ontology Trading is the closest single-product replacement for what Capitalise.ai used to be — natural-language strategy authoring plus multi-broker webhook execution across Kraken, Interactive Brokers, Coinbase, Alpaca, Webull, Tastytrade, and TradeStation. If you only trade crypto on Kraken, stay on Kraken Pro and use the inherited NLP feature. If you only need TradingView-to-broker piping with no AI authoring layer, TradersPost or Tickerly are leaner and cheaper. If you trade FX through MetaTrader, PineConnector is the focused tool. The honest answer for most ex-Capitalise.ai users: pick the relay first based on your broker, then layer an authoring tool that gets you back to the plain-English ergonomics you actually liked.

For more on building strategies in chat and routing them to a live broker, see Ontology’s platform overview, and reach out via the contact page if you have a specific Capitalise.ai migration question.