Priced off a venue, not cleared through an exchange
A CME futures program uses licensed exchange data, priced by exchange and usage. A perpetual program usually prices off a venue feed, governed by API limits rather than a per-group licence. That changes what the firm pays for data, and it also changes what the firm is responsible for defining itself.
Funding is a rule you have to write
CME positions carry no explicit overnight charge. Perpetual positions pay or earn funding at every interval. A firm has to decide whether funding applies to simulated accounts at all, whether it uses the venue's actual rate or a fixed approximation, and how it affects drawdown.
Ignore funding and a trader's edge looks better than it is. Apply it inconsistently and you invite disputes. Either way, it is a cost decision hiding inside a rule.
One price, two definitions of breach
A real perpetual venue liquidates on mark price and maintenance margin. A prop firm's drawdown rule is a separate system. That means a trader can be inside the firm's limit while the venue would already have closed the position, or the other way round.
The price you choose to trigger a breach, mark or last, decides who wins a later dispute. It needs to be written down, applied the same way every time, and explained to traders before they buy.
No weekend means no reset
A CME program has a weekend. It gives the firm a scheduled point to review exposure, process payouts and fix problems. Perpetuals never close. Breach review, monitoring and payout processing have to run around the clock, including during thin liquidity when abuse is easiest.
That is an operating cost, in people or in systems, and it belongs in the business case before launch.
Regulation covers less than it seems
US approvals of cleared perpetual products govern where those products can be listed. They do not directly govern simulated prop accounts priced off offshore feeds. Firms should not read a regulatory headline as cover for their own program design.
What this means for firms adding perps
Before launching a perpetual program, write the funding rule, the breach price definition and the 24/7 operating plan, and model them against your payout assumptions. A lower data bill does not mean a lower total cost. Getting these rules right before launch is far cheaper than defending them in a dispute after.