Prop Firm Rules

Liquidity Provider (LP)

Where the prices on your screen actually come from, and whether the firm behind them is running its own infrastructure or reselling someone else's.

What it is

Most prop firm challenges, and most funded accounts too, are simulated: no order you place ever reaches a real exchange or broker on your behalf. That doesn't mean the price feed is invented. A firm still needs a live, real-time stream of actual market prices to know what you should be filled at, mark your open positions, and calculate your drawdown correctly, even on a purely internal ledger. The liquidity provider (LP) is whoever that price stream actually comes from, and in the smaller number of cases where trades really are hedged or passed through to a real venue, the LP is also who's actually executing on the other side.

Broker LP vs. prop firm LP, and why the difference matters

A retail ECN or STP broker's job is to actually route your order somewhere in real time, weighing several live liquidity pools at once and picking the best price available at that instant. Done well, this occasionally works in the trader's favor: brokers like IC Markets are good enough at this that negative spreads genuinely show up in real, if uncommon, scenarios, the routing found a better price than the raw quoted spread would suggest.

Prop firms generally aren't built to do any of that, and mostly don't need to be. Since the account is simulated, all the infrastructure actually has to do is receive a price feed and fill a simulated order against it. There's no real order to route anywhere, and no competing liquidity pools to choose between.

That simplicity comes with a real cost, and it lands on the firm, not the trader. A broker with genuine ECN routing can offload its own exposure into a live, deep market in real time, if market gaps happen, that hedge absorbs a meaningful part of the damage. A prop firm running a single simulated feed has no equivalent: every gap between what the feed shows and what a real market could actually have filled is a cost the firm eats directly out of its own pocket the moment a funded trader gets paid on it.

That asymmetry is a large part of why so many prop firms restrict or outright ban trading around high-impact news. A live ECN fill during a news spike still reflects real, if ugly, liquidity: wide spreads, slippage, requotes. A simulated fill often doesn't reflect any of that, the feed can print a clean, tradable price straight through an event that would have been unfillable, or filled far worse, on a real venue. Banning news trading isn't only about protecting the trader from volatility, it's frequently the firm protecting itself from having to pay out on fills its own infrastructure was never built to price correctly in the first place.

Why it doubles as a white-label check

A large share of "prop firms" aren't running their own trading infrastructure at all. They license a ready-made back office, price feed, and dealing platform from a bigger provider, then put their own logo and rules on top. There's nothing dishonest about that by itself, most retail brokers do the same thing one layer further up the chain. But it means the LP question can surface something the marketing never will: which firms are genuinely independent operations, and which are one of several differently-branded storefronts sitting on the exact same shared backend.

The major white-label backends

A handful of specialized vendors show up repeatedly behind different-branded "prop firms," and they're not all the same kind of company. FPFX Tech is a prop-firm risk specialist: it powers infrastructure for multiple firms, and its own marketing is explicit about what it provides, automated risk tools, identification of "toxic" trading behavior across a portfolio, and hedging run on the firm's behalf. Eightcap is a multi-regulated broker running an actual retail (B2C) business alongside its white-label (B2B) arm, which offers full backend office systems built on Eightcap's own existing liquidity-provider relationships. Match-Trade Technologies sits at a different layer entirely: it makes the MatchTrader platform itself, as a pure B2B technology vendor with no retail brokerage of its own, and firms like FPFX Tech integrate MatchTrader as one of several platforms they offer, a customer of the platform, not the company behind it. Easy to conflate since the two show up together often, but they're unrelated companies at different points in the same stack.

Both play a double role: platform vendor and de facto risk manager at the same time. That's a genuine advantage, not just a shortcut. A firm running purely on a marked-up spread with no real hedging is running a raw b-book against its own traders, and whoever manages that risk carries the conflict of interest. Handing the function to a specialized backend means the aggregate exposure is being priced and hedged professionally in a real market by someone whose whole business is doing that well, and it moves the liability for getting it wrong off the front-facing brand and onto the infrastructure provider instead.

The downside is duplication: platform quirks and execution behavior can show up identically across several, differently-branded firms running the same backend, because it genuinely is the same system underneath. And running on shared infrastructure doesn't mean identical trader-facing terms, each firm negotiates its own contract with the backend provider, so spreads, costs, and how risk gets split between the firm and the provider can differ meaningfully even when the plumbing is the same.

More on this, including how SwingFish has been approached directly with this exact white-label pitch, in The Six Ways a Prop Firm Actually Makes Money.

How to actually check it

  • Platform server name: open a demo account and look at the server name shown at MT4/MT5/cTrader login. It often names the actual back-office/bridge vendor rather than the firm itself, that mismatch is usually the clearest tell.
  • Terms of Service / FAQ language: some firms name a specific LP, bridge provider, or "powered by" partner outright. Most don't, silence here is the norm, not the exception.
  • Support: worth asking directly, but treat a non-answer as the default outcome rather than a red flag on its own, this is exactly the kind of question front-line support is rarely equipped to answer.
Not a red flag by itself. Licensing infrastructure instead of building it in-house is normal, and cheaper infrastructure isn't automatically worse infrastructure. What's actually worth flagging is a firm marketing itself as though it has unique, purpose-built technology while it's really a reskin of a shared backend used by several competitors, or a firm that won't answer a straightforward question about where its pricing comes from at all.

Related