Company
Where the MultiPrimeX product line is heading
The products in this range were built to be taken individually, and most deployments still start that way. The direction of travel is that the layer underneath them — accounts, payments, reporting — becomes progressively more shared, so that adding a second product is a configuration rather than a second integration.
One account model beneath several front ends
A client record, a wallet and a trading account mean the same thing regardless of which product a firm is using. That is the design decision everything else follows from, and it is the reason a brokerage can run its own terminal alongside an integrated third-party platform without doubling its operations work.
It is also what makes the platform choice reversible. Changing the front end a trader sees does not require rebuilding the brokerage behind it.
Connectivity as a separate layer
Aggregation and routing deliberately sit apart from the liquidity itself. A firm should be able to use our pricing through somebody else's bridge, or somebody else's pricing through ours, and neither should be a special case.
Keeping those two things separate costs a little architecturally and avoids the situation where a commercial decision about liquidity is constrained by a technical decision about connectivity.
Risk in two places, for two audiences
Monitoring a firm's own exposure and running an evaluation programme sold to traders are different problems that are frequently bundled together. Keeping them as separate products means neither is compromised to fit the other.
Firms that need both get a consistent data layer underneath; firms that need one are not made to carry the other.
What this means for an existing deployment
Nothing that is running needs to change. The shared layer is additive, and the account model, reporting and API surfaces are held stable precisely because deployments depend on them.
The practical effect is that adding a product later should be less work than it would have been earlier — which is the opposite of how most stacks age.
In short
What to take away
A shared account model is the foundation, not a feature
Connectivity and liquidity stay separable by design
Firm risk and trader evaluation remain distinct products
Existing deployments are not required to change
Read next
Start with the piece you are missing
Most firms do not need the whole range. Tell us what you run today and we will map what would actually add something.