Two business models, two technology stacks
An evaluation (challenge) firm sells a test: the trader pays a fee, trades a demo or simulated account under rules, and earns a share of profits on a funded account if they pass. Volume is in the thousands of small accounts, and the technology problem is rules, payments and support at scale.
A capital-backed firm puts its own money behind a smaller number of vetted traders, often on live accounts, with discretionary limits. Volume is low, exposure per trader is high, and the technology problem is risk aggregation, execution control and research tooling. Many firms run both, which is why the checklist below covers both.
The eight-system checklist
| System | Buy or build | What to check before signing |
|---|---|---|
| Trading platform (MT5, cTrader, DXtrade, Match-Trader) | Buy | Licence terms for prop use, server location, Manager API access, cost per account, second-platform option. |
| Evaluation and rules engine | Buy, then customise | Real-time enforcement of drawdown, daily loss and consistency rules; rule versioning; what the trader sees and when. |
| CRM with KYC and payouts | Buy | KYC before first payout, profit-split calculation, payout approvals, affiliate tracking, full audit log. |
| Payment stack (fees in, payouts out) | Buy | Card dispute handling for fees; stablecoin and bank rails for payouts; reconciliation into one ledger. |
| Risk and exposure console | Buy or build | Aggregated exposure across funded accounts, per-symbol limits, kill switches, approval workflows for interventions. |
| Support desk | Buy | Tickets that show the trader's account, rule breaches and payout state without a second lookup. |
| Research tools for funded traders | Buy | Something traders value enough to stay: a research co-pilot, data and analytics, a community. |
| Recordkeeping and messaging | Buy | Retention of rule decisions, trader communication and payouts; exportable on request. |
The rules engine: where firms win or lose
Rules are the product and the risk. A static drawdown is measured from the starting balance; a trailing drawdown follows the account's high-water mark on balance or on equity, and the difference between those two words decides whether a trader is breached mid-trade. Daily loss limits reset at a defined time in a defined time zone. Consistency rules cap how much of total profit one day may contribute. News-trading and weekend-holding rules depend on a calendar the software must own.
Every rule must be evaluated continuously against live prices, logged with the price and time that triggered it, and shown to the trader in the same words the terms use. Firms that check rules by hand after the fact lose disputes and lose traders.
Payments in both directions
Evaluation fees arrive by card, local payment methods or stablecoins. Card payments can be disputed for months after the fact, so keep evidence of what the trader bought and agreed to. Payouts to funded traders go out by bank transfer or stablecoin and cannot be reversed, so they sit behind KYC, a profit-split calculation the software performs and a human approval with a four-eyes rule above a threshold.
USDT on TRC20, BEP20 or ERC20 has become a common payout rail because it settles in minutes to any country. If you offer it, run the wallet and the reconciliation on infrastructure you control, screen addresses before sending and keep a ledger that ties every payout to the account and the rule decision that allowed it.
Risk aggregation and execution control
Funded accounts add up. A hundred traders long the same index on an announcement is one position, not a hundred, and the firm's exposure must be visible per symbol and in total. An operations console that reads exposure from the platform, enforces per-strategy and per-account caps and offers a kill switch with an audit trail is the difference between a bad day and a closed firm. Where the firm runs its own systematic strategies, an execution engine with a dry-run sandbox and promotion to live with caps keeps experiments away from capital.
Regulatory watch-points
Prop firms have drawn regulatory attention in the United States and Europe since 2023, mostly around how evaluations are marketed, whether simulated accounts are presented as real, and whether payouts are honoured. The technology consequences are concrete: say clearly in the product whether an account is simulated, keep every rule and payout decision on record, and be able to show a regulator what a trader saw at each step. Structure the entity with counsel in the jurisdictions you sell into; this guide is engineering guidance, not legal advice.
Where EntropyX Labs fits, and where it does not
EntropyX Labs supplies four of the eight systems as products: SignalDesk as the research co-pilot funded traders use, EA Panel as the risk and exposure console with approval workflows and an audit log, Brokerage CRM with KYC and roles (profit splits and trader payouts are built on request), and EntropyX Tickets for support with account context. Two more cover part of a system: EntropyX Chat for retained internal messaging, and EntropyX PSP for the stablecoin side of payouts. FX Auto-Pilot, in beta, adds an MT5 execution engine with sandbox-then-live promotion and caps; it runs beside the trading platform rather than replacing it.
We do not sell a trading platform or a packaged evaluation rules engine. Where a firm needs rules enforcement built around its own terms, we build it under a custom engagement on top of the same account layer, with the rule log and trader-facing explanations described above.
Sources and further reading
This guide is engineering and product guidance from EntropyX Labs, a technology provider. It is not legal, regulatory or investment advice.