AI Universe
Find your asset universe
Tell our AI your goals. It instantly filters 70,000+ assets to what fits you.
rchitect like a quant team.
Smart Ranking
Rank & select assets
Select a quant model. We score and pick the best assets for your strategy.
Intelligent Allocation
Allocate the portfolio
Review your optimized allocation and send it to your broker in one click.
udit before investing.
How a medium risk profile behaves
Strategy
Benchmark
Annual Return
+20.6%
Max Drawdown
-15.4%
Sharpe Ratio
1.24
Risk Tolerance
MediumIllustrative model output, not actual returns. Not indicative of future performance.
You decide how much it does.
Connecting Trading 212 is optional, and connecting it does not hand over control. You choose the mode: keep it on one-click approval so it prepares orders and waits for you, monitor without trading, or let it rebalance unattended. Acubic reads your live positions, compares them against the target weights of the strategy attached to that connection, and trades only the difference; positions already at target are left alone.
How the connection runs
Each scheduled rebalance prepares the order set and stops there. You review the trades and approve them before anything reaches Trading 212, and nothing is sent while an approval is pending.
Leave rebalancing switched off and Acubic tracks the account's live positions, drift from target, and performance without ever placing an order.
Available directly on your Trading 212 Invest account. The API key is scoped to the whole account, so there is no separate sub-account to fund. Scheduled rebalances execute without a per-order prompt, behind the same safety guards as one-click: one order in flight at a time, round-down sizing, and a managed-value sanity breaker.
You connect with an API key and secret you generate inside the Trading 212 app; your login is never shared. Stored credentials are encrypted at rest and never returned to the browser or written to logs. Disconnecting, or revoking the key in the app, stops Acubic sending orders and leaves every existing Trading 212 position untouched; it does not liquidate anything. Every order Acubic places is recorded in an audit log you can review after the fact.
Common questions
No. Acubic is an independent product operated by Acubic, Inc., a Delaware corporation, with no partnership, sponsorship, or reseller agreement with Trading 212, and Trading 212 does not endorse or take responsibility for the portfolios Acubic produces. Acubic connects to a Trading 212 account you already hold, using an API key you generate yourself and can revoke at any time. Trading 212 is a trademark of its owner.
No. You generate an API key and secret in the Trading 212 app and paste them into Acubic; your login is never shared. The key can be revoked in the app at any time, and stored credentials are encrypted at rest, never returned to the browser or written to logs.
Yes. Disconnect in one click, or revoke the API key in the Trading 212 app. Existing positions remain in your Trading 212 account; Acubic simply stops sending rebalance orders. Disconnecting never liquidates or modifies a position.
Yes. A Trading 212 key is scoped to your whole Invest account, so unattended rebalancing runs directly, with no separate sub-account to fund. It runs behind the same safety guards as one-click and logs every order. You can also keep it on one-click approval or monitoring-only instead.
Invest and Stocks ISA accounts. Acubic reads live positions and places equity orders through the official Trading 212 API; it does not use Pies or CFD accounts.
It compares your live Trading 212 positions against the target weights of the strategy attached to that connection and trades only the difference. Positions already at target are left alone, so a rebalance is not a liquidate-and-rebuild: it is the smallest set of orders that closes the gap.
The failure is recorded against that rebalance run with the broker's reason, and the remaining orders are handled independently rather than the whole run being silently abandoned. You can review what filled, what did not, and why, in the connection's execution history.