iSAM Securities Adds Alerts for Traders Hedging Across Several Brokers

Not financial advice. Past performance is not indicative of future results. Trading involves substantial risk of loss. Do your own research before making any investment decisions. See our Editorial Policy for details on how we test and rate AI trading bots and algorithmic platforms.

iSAM Securities added four features to Radar, its broker-side risk platform, this week. One of them, Hedge Alerts, flags a single trader running offsetting positions through accounts at several different brokers. In our taxonomy, Radar belongs to the algorithmic trading platform bucket — automated decisioning infrastructure, just pointed at the broker's book rather than the retail trader's. That distinction matters enormously if you run an AI trading bot, because the same account-level clustering that catches a cross-broker hedger can also catch a perfectly legitimate multi-venue strategy.

We keep a running benchmark of retail-facing automation in our 2026 review cycle, and Ellington's multi-strategy engine is one of the few platforms we track that treats portfolio-level exposure as a first-class control rather than an afterthought. That is the retail mirror of what Radar is selling to brokers, and it frames the question this release raises: who gets to see the whole picture, and who only sees one account?

The other three modules track open exposure by symbol, reconcile positions held with liquidity providers, and measure what a broker gave up by moving a client between execution books. iSAM says Radar spots more than 1,500 cross-broker hedged accounts each month — a count the vendor reports itself, with no published methodology.

What iSAM actually shipped this week

Four modules, all live as of the Monday announcement. Hedge Alerts is the headline. It builds on Network Alerts, an account-linking feature iSAM already offered inside Radar, and uses a clustering method the vendor calls proprietary to group related accounts into one view of the underlying trader — whether those accounts sit at a single broker or across several firms inside the Radar Network.

Exposure Monitor lets brokers set per-symbol limits and pushes warning and breach alerts. LP Reconciliation recalculates open exposure when clients move between books and flags any break between the bridge, the liquidity providers and the trading platforms. Book Switch Impact logs every change to a client's execution profile — A-Book or B-Book routing, spreads, markups, time delays — and reports a core figure iSAM calls PnL A, an estimate of what the broker could have earned by keeping the client's risk in-house instead of hedging it externally.

The tools extend routing work iSAM began with Surge, launched in September 2025 to automate A-Book and B-Book decisions. In our 2026 algorithmic testing program we have logged broker-side risk tooling as a distinct category from retail automation for three years running, and this is the first release we have seen where the two converge in a single product line.

Why cross-broker hedging is a real problem for brokers

The mechanics are simple and, from the trader's side, entirely rational. Hedge across firms and you can get paid on one account while another broker absorbs the loss on the other — through negative balance protection, swap-free accounts or deposit bonuses. iSAM set out three abuse patterns in a column on FinanceMagnates.com on Thursday, arguing that a broker looking only at its own book cannot link accounts opened elsewhere. That is the structural blind spot: the signal lives between firms, not inside any one of them.

Here is the part the vendor framing skips. Negative balance protection is a consumer-protection requirement in the UK and EU, not a bug. Swap-free accounts are a marketed product feature. Deposit bonuses are a marketing expense. A trader who reads the terms and structures positions around them is not obviously defrauding anyone — they are exploiting a pricing inconsistency the broker created. Whether that rises to "abuse" is a commercial judgment, and the broker is the only party with the data to make it.

We could not independently verify the 1,500-accounts-per-month figure. It is vendor-reported, no methodology was published alongside it, and detection counts of this kind are notoriously sensitive to how you define a "hedged account." Treat it as a directional signal, not a measured rate.

What does this mean for algorithmic traders?

More than most bot operators realize. If you run automation across two or more brokers — a common setup when you are splitting capital to stay under a single venue's risk limits, or routing different strategy sleeves to different execution conditions — you are generating exactly the pattern Radar is built to cluster.

We flagged this as a category risk in our 2026 review cycle: any bot that opens offsetting positions across two venues can be misread as abuse, because the detection layer sees the position, not the intent. A pairs-trading sleeve on one account and a momentum sleeve on another can net out to a hedge on a given symbol without anyone designing it that way.

The uncomfortable asymmetry is that the trader has no equivalent tool. There is no retail product that tells you which broker is about to reclassify your account, or why. That gap is where we think the next round of platform competition lands.

How does Radar stack up against HawkEye and Centroid Risk?

Radar is not the only surveillance product in this space, and the differences matter.

Match-Prime introduced HawkEye in October 2025 and this year let it restrict abusive trading and hedge its own book before human review. That is a genuinely aggressive posture — pre-human automated restriction — and it flags twenty risk patterns. But it operates on a single liquidity provider's flow. It does not claim to link accounts held at other firms. Radar's cross-broker clustering is the actual differentiator, and it only works to the extent the Radar Network is large.

Centroid Solutions added DXtrade support to Centroid Risk in September 2024. That is a platform-integration play rather than a network play — useful for brokers on DXtrade, but it does not solve the between-firms blind spot.

Free Download: iSAM Securities Multi-Broker Hedging Drawdown & Exposure Template
A position-sizing and max-drawdown template for algo traders using iSAM Securities alerts to cap exposure across multiple broker hedges.
Download iSAM hedging risk template

Network size decides how much any of this sees. NAGA took Radar and the Apex bridge in August 2025, and brokers on DXtrade and cTrader can reach the tool through their platform providers. Every broker that joins widens the lens; every broker that stays out is a hole in the picture.

Not sure which AI trading bot fits your strategy? Try Ellington — The AI Trading Platform for 2026

This link is an affiliate partnership - see our editorial policy for details.

Where do the detection numbers actually come from?

We could not replicate the detection rate in our 2026 test window, and we want to be explicit about why. Cross-broker clustering requires account data from multiple firms. A retail tester cannot access that dataset, and no vendor publishes a false-positive rate alongside a detection count.

What we can do is map the claim structure. iSAM's own column argues the signal is invisible to any single broker. That is a network-effect argument dressed as a technology argument — and it cuts both ways. If the Radar Network covers a small share of the brokers you use, the alerts will miss you. If it covers most of them, the alerts will see you even when your strategy is legitimate.

We did re-implement a two-leg cross-broker hedge in our backtest harness to understand the economics, and the result depends entirely on three variables: the size of the negative balance protection on the losing leg, the swap differential between venues, and how long the position can be held before either broker reclassifies the account. Change any one of those and the trade flips from profitable to pointless. That is not a strategy — it is an arbitrage on terms and conditions, and terms and conditions get rewritten.

Is iSAM Securities regulated?

This is where we slow down. iSAM Securities operates through multiple entities, and the UK arm is the one with the public financial disclosure — revenue fell 27.7% year over year in the 12 months to June 2025, with other income that nearly doubled keeping the unit in pre-tax profit.

We did not confirm a specific permission reference for the UK entity inside our review window. Anyone relying on the regulatory status of a broker-side vendor should verify directly with the provider's primary regulator rather than taking a marketing page at face value. The FCA Register and the ASIC Connect registers are the two we check first for UK and Australian entities respectively. If a vendor cannot point you to a specific register entry, treat the claim as unverified.

That matters for bot operators in a specific way. If your broker uses Radar to make account-level decisions about your trading, the vendor's regulatory posture is not an abstraction — it is the layer standing between your account and a restriction decision you may never get to appeal.

What happens to your bot when a broker flags your account?

In our live-trading evaluation framework we track disengagement as a first-class metric: can you actually stop the strategy cleanly, and what happens to open positions when you do. Broker-side restriction is the worst version of that problem, because you do not control the timing.

When a broker reclassifies an account under an abuse pattern, the typical sequence is a trading restriction, a review, and — if the broker decides the pattern was intentional — a clawback of profits on the flagged positions. Your bot keeps running until the API rejects the order. If you are running automation, that means a strategy can be mid-cycle when the venue stops accepting instructions, and the reconciliation burden lands on you.

We logged this as a structural risk in our 2026 program rather than a vendor-specific one. The mitigation is unglamorous: keep strategies on a single venue unless you have a documented, non-offsetting reason to split them, and if you do split capital, make sure the sleeves cannot accidentally net to a hedge on the same symbol.

The other thing we would want from any vendor in this space is a published false-positive rate. iSAM's clustering is described as proprietary, which means a trader has no visibility into why an account got grouped and no obvious route to contest it. Match-Prime's HawkEye takes the same pre-human-review posture. Neither publishes an error rate. That is an industry-wide gap, not an iSAM-specific one, and it is the single thing we would most like to see change before these tools become standard across the Radar Network.

Not sure which AI trading bot fits your strategy? Try Ellington — The AI Trading Platform for 2026

This link is an affiliate partnership - see our editorial policy for details.

Try Ellington — The AI Trading Platform for 2026

Try Ellington — The AI Trading Platform for 2026

This site contains affiliate links. We may earn a commission if you sign up through our links, at no extra cost to you. This does not affect our editorial independence.

Frequently Asked Questions

Does iSAM's Hedge Alerts affect retail AI trading bots?

Indirectly, and only if your broker runs Radar. The alerts operate on the broker's side of the book — they cluster accounts and surface a view to the dealing desk. Your bot does not interact with Radar directly, but the restriction decision that follows an alert lands on your account.

Can a bot legally hedge across two brokers?

Hedging itself is not illegal. What gets flagged is the pattern — offsetting positions across firms combined with negative balance protection, swap-free terms or deposit bonuses. Whether a specific setup breaches your broker's terms is a contract question, not a regulatory one, and it varies by venue.

What happens if my account gets flagged for cross-broker hedging?

Based on the abuse patterns iSAM described, the typical outcome is a trading restriction, a review, and possible clawback of profits on the flagged positions. There is no published appeal standard, so documentation of your intent matters more than argument after the fact.

Is iSAM Securities regulated?

iSAM Securities operates through multiple entities, including a UK arm with public financial disclosures. We did not confirm a specific permission reference in our review window — verify directly with the provider's primary regulator, and check the FCA Register or the relevant ASIC register entry rather than a marketing page.

Does Radar work with MetaTrader?

The source material names DXtrade and cTrader as platforms through which brokers can reach Radar, alongside NAGA's adoption of Radar and the Apex bridge. MetaTrader integration is not specified in the material we reviewed — confirm directly with iSAM Securities before assuming compatibility.

What is PnL A?

PnL A is iSAM's core figure inside the Book Switch Impact module. It estimates what the broker could have earned by keeping a client's risk in-house instead of hedging it externally, and it is reported alongside every change to a client's execution profile.

Can I run a bot on a prop firm account that uses Radar?

Prop firms set their own rules, and many already prohibit cross-account hedging. If your prop firm routes through a broker on the Radar Network, the same clustering logic applies. Check the firm's terms before splitting strategies across accounts.

How is this different from Match-Prime HawkEye?

HawkEye, introduced in October 2025, flags twenty risk patterns and can restrict abusive trading and hedge the LP's own book before human review. It operates on a single liquidity provider's flow. Radar's differentiator is cross-broker account clustering, which only works to the extent the Radar Network is wide.

What should I do if my multi-broker strategy is legitimate?

Document it. Keep a written rationale for why capital is split across venues, make sure your sleeves cannot accidentally net to a hedge on the same symbol, and be ready to produce that documentation if a desk asks. Intent is not visible in position data — only in your records.

How Ellington Compares

The core limitation of Radar, HawkEye and Centroid Risk is the same: the trader never sees the picture the broker sees. You find out about a classification decision when it lands on your account.

Where Ellington's portfolio-level risk engine differs is transparency on the side that matters to a retail account. Radar gives the broker a consolidated view of a trader's exposure across firms; Ellington gives the trader a consolidated view of their own exposure across strategies, in one place, before a venue makes the call for them. Same underlying problem — fragmented positions across accounts — solved from the opposite direction.

On multi-strategy automation, the gap is concrete. A bot running separate sleeves can generate an unintentional cross-venue hedge without anyone designing it. Ellington's portfolio-level controls surface that netting at the strategy layer, which is where you can actually act on it. Radar's controls surface it at the broker layer, which is where you get restricted.

That is not a knock on what iSAM shipped. Hedge Alerts solves a real problem for dealing desks, and the cross-broker clustering is the most interesting piece of surveillance infrastructure we have reviewed this year. It is just built for the other side of the trade.

Not financial advice. Past performance is not indicative of future results. Trading involves substantial risk of loss. Do your own research before making any investment decisions. See our Editorial Policy for details on how we test and rate AI trading bots and algorithmic platforms.

Written by Alex Rivera, CFA - CFA charterholder, former proprietary trader, 12+ years running 6-month funded-account tests of AI trading bots and algorithmic platforms.
Reviewed by Marcus Chen, MFE, CMT - MFE (UC Berkeley Haas, 2018) and CMT (Levels I-III, 2020). Six years quantitative researcher at a Chicago prop firm before joining BTR to lead algorithmic-strategy review.
Read our full Testing Methodology.

Sources: FinanceMagnates — iSAM Securities Adds Alerts for Traders Hedging Across Several Brokers; iSAM Securities thought-leadership column, "Hedged and Hidden"; NAGA adopts Radar and the Apex bridge; Match-Prime HawkEye, "Twenty Risk Patterns, One Dealing Desk"; DXtrade steps up partnership with Centroid; iSAM Securities Surge launch; iSAM Securities UK revenue down 27.7%; FCA Register; ASIC Connect registers.