If you trade futures evaluations at more than one firm, there’s a good chance several of them run on the same rails without telling you. That shared plumbing is ProjectX, and understanding it changes how you copy between accounts.
What ProjectX is and which firms use it
ProjectX is a futures trading infrastructure and API layer that a number of prop firms build their evaluations on top of. Instead of each firm writing its own order routing and account management, they license the platform and apply their own rulebook — targets, drawdown model, payout terms — on top of a common execution engine.
For a copier this is a gift and a trap. The gift: a single ProjectX integration can talk to accounts across multiple firms through one API surface. The trap: the shared platform does not mean shared rules. Two ProjectX firms can differ on drawdown type, consistency requirements, and product limits while looking identical at the order level.
Firms such as MyFundedFutures, Tradeify, and Bulenox are commonly associated with ProjectX-style infrastructure — but which platform a firm uses and what it permits can change, so confirm the current setup with each firm directly before you wire anything together.
API-driven copying without a chart
The most important practical difference from an MT5-style copier: ProjectX copying happens through the API, not through a chart or a terminal EA. There’s no need to keep a platform window open, no expert advisor loaded on a symbol, no VPS running a GUI just to relay fills.
That means:
- A copier can subscribe to master fills and push slave orders server-side, closer to the exchange, with fewer moving parts to crash.
- You aren’t tied to one machine being awake. The relay logic lives in a service, not on your desktop.
- Order state — fills, rejects, position — is queried directly, so reconciliation is exact instead of scraped off a chart.
Fewer hops usually means less latency and fewer silent failures. It also means the copier’s risk logic can sit in the path and reject an order before it ever reaches the exchange if it would breach an account’s limit, rather than reacting after the fill.
Whole-contract scaling across account sizes
Futures copy in whole contracts — there is no fractional contract — so scaling across differently sized ProjectX accounts runs into the same rounding wall as any futures copier. A 50% copy of 3 contracts is 1.5, which doesn’t exist.
The practical moves:
- Trade in micros where possible to get ten times the granularity before rounding forces you to over- or under-size.
- Pre-compute each account’s contract count from its risk budget and the trade’s stop distance, then round with a consistent rule (down is the conservative choice on trailing accounts).
- Accept that small master sizes barely copy. A 1-contract master fill can only land as 0 or 1 on a slave — there’s no proportional half.
If you want the arithmetic laid out, the multi-account position sizing approach starts from risk-per-account and works backward to a contract count, which is the only order that keeps proportionality honest.
Trailing-threshold divergence between firms
Here’s the ProjectX-specific hazard. Because you’re copying across different firms, each account may use a different drawdown model even though the orders route through the same platform. One account might trail on end-of-day balance; another might trail intraday on unrealized equity; a third might use a static line.
Copy the same trade into all three and the exact same fill has three different risk consequences:
- On the static-line account, an open drawdown is temporary and recovers.
- On the intraday-trailing account, the same drawdown can pull the line up and lock in a tighter ceiling before price comes back.
- On the end-of-day account, the timing of your exit relative to the close decides whether the loss counts against the trail.
This is why “just mirror everything” quietly fails across firms. The copier has to know each account’s model and hold each to its own limit — which is exactly the kind of hard per-account risk enforcement worth insisting on rather than eyeballing.
Rule differences to map before you copy
Before you connect a single account, build a small map of where the firms disagree. Don’t trust that shared infrastructure means shared rules.
- Drawdown model — trailing (intraday vs end-of-day) or static, and how the line moves.
- Consistency requirement — whether a single big day can disqualify an otherwise passing account.
- Product and session limits — which contracts are allowed and whether positions must be flat around certain windows.
- Payout mechanics — minimums, timing, and whether copy trading must be disclosed.
Confirm every one of these with the firm directly; published rules change and third-party summaries lag. Once mapped, a copier that respects each account’s constraints turns a messy multi-firm setup into something you can actually run.
Shibiki captures fills across every connected ProjectX account automatically, tracks live edge health per strategy with a Wilson confidence interval so a hot streak on twelve trades doesn’t get mistaken for an edge, and lets you enforce the same hard risk limits per account regardless of which firm’s model it lives under — so the difference between firms becomes configuration, not a landmine.
Related: ProjectX integration · MyFundedFutures rules · Tradeify rules