Skip to content
Broker news. Connected. RSS feed
FXBROKERS

A clearer view of the broker industry.

Evenox joins iSAM’s Apex bridge, adding another liquidity route for CFD brokers

Brokers using Apex can add the provider alongside existing liquidity relationships. Routing rules and reconciliation determine how that connection feeds through to pricing and hedging.

Evenox has connected its liquidity offering to iSAM Securities’ Apex bridge, giving CFD brokers using the technology another provider they can add alongside existing relationships. Finance Magnates reported the integration on 21 October; iSAM’s own announcement confirms that the connection is available.[1][4]

iSAM says brokers can add Evenox without replacing their execution infrastructure. The provider, formerly LP Prime, offers more than 2,500 instruments across currencies, metals, equities, indices, energies and ETFs.[1]

A connection, a liquidity pool and a routing decision

Process01

Roles in the integrated service

Roles in the integrated service
LayerPublished function
EvenoxSupplies liquidity assembled from multiple institutional sources and tailored to broker requirements.Source 3
ApexAggregates providers and applies the broker’s rules for pricing, order routing and hedging.Source 2
BrokerCan add the new relationship alongside current providers while retaining execution choices.Source 1

Evenox’s own service description supports FIX and API connectivity, MetaTrader 4 and 5 bridges or gateways, and aggregation systems. Its customization covers trading volumes, flow characteristics, infrastructure and execution requirements. The Apex connection supplies another way to distribute that service; it does not turn a provider’s entire catalogue into an identical retail offer at every connected broker.[3]

A broker assessing the connection needs to compare it with the flow it actually handles: instrument, ticket size, trading session and execution conditions. The published instrument count describes the provider’s range; the broker’s routing rules determine which orders use that range.[1][2]

Where the bridge affects the outcome

Apex documents routing rules based on variables including instrument, client or group, volume, direction, leverage, order source, location and time. It also supports A-book and B-book configurations, so a connection to another provider does not mean every customer trade will be externally hedged.[2]

Its LP reconciler compares actual A-book, B-book and provider positions with the positions expected under the routing configuration, flagging discrepancies. The platform also exports reporting data through SQL and Amazon S3 for internal or third-party analysis.[2]

Together, routing records and reconciliation provide a way to compare the intended exposure with the hedge that exists after execution. A useful review follows the order from the applicable rule to the accepted trade and resulting provider position.[2]

The integration release supplies no matched-flow execution study. Acceptance rates, slippage and completed hedge cost for comparable orders would show the commercial effect of adding the route. Those measurements are separate from the fact that the technical connection is available.[1]

Provider diversification also needs to be assessed below the brand level. Because Evenox describes a pool drawn from several institutions, a second provider connection need not represent wholly different underlying liquidity. The published service description does not identify those sources, leaving brokers to establish the overlap in their own commercial arrangements.[3]

Follow the evidence

Sources & further reading

  1. Evenox institutional liquidity Evenox · Accessed 29 Oct 2026

Report an error or submit an update