White-label vs in-house — and vs a thin WL.
Lease the engine. Own the relationship. Most first firms should not build a challenge platform. They also should not stitch a CRM, a partner widget, a consumer journal, a generic ESP, and a rented terminal onto a challenge engine.
Typical white-labels do not ship the operating stack.
Challenge + risk is table stakes. The painful layers — CRM, affiliates, native terminals, journal, marketing — are what firms bolt on later, or never. OneProp keeps them in the same tenant. Scale and Command bundle the growth pack; Launch adds the modules you actually run.
| OneProp | Typical white-label | |
|---|---|---|
| Admin CRM | Prop-native. Plans, KYC, payout queues, promo codes, branding. Same objects as risk. | A forex CRM with a challenge plugin, or a spreadsheet |
| Affiliates | Multi-tier, S2S, partner-owned codes, clawbacks, a ledger separate from trader payouts | Last-click widget. Serious IBs walk |
| Native terminals | Platform5 and TradeHub in the same tenant — included on Scale and Command, selectable on Launch. Bridges for names you already promised | Rent MT / someone else's desktop. Policy risk is theirs |
| Trade journal | In-portal. Same fills the risk engine scored | Traders leave for a consumer app |
| Marketing | Flows on checkout, fail, reset, funded, payout. The account already has the events | Generic ESP, two days late |
| Same tenant | Yes. One login. One rule graph. | Five vendors pretending to be one firm |
White-label vs in-house.
| White-label (OneProp) | In-house | |
|---|---|---|
| Time to market | Weeks of configuration if entity, brand, and a PSP show up | 9–18 months before a single sale |
| Upfront | Low five figures + monthly license | Six to seven figures |
| Monthly | Launch $2,490 / Scale $4,990 / Command $8,990, plus selectable modules. Caps + overage explicit. No revenue share | Engineers, infra, on-call, vendor licenses anyway |
| Margin at scale | Lower than a surviving build | Higher if you survive the build |
| UX / rules | High: brand + plan objects + locale. Invisible vendor | Total |
| Terminals | Platform5 + TradeHub default, plus bridges you already paid for | You still rent MT / futures data unless you truly own a stack |
| Exit | Export traders, fills, affiliates, rule versions | You already own the repo — if it is finishable |
| Best for | First launch, fast validation, brokers adding a prop line, creator desks that must not become the risk desk | Funded, proven firms with a reason to own the cron |
When to lease
You do not yet have a payout model that survives a bad month. You need partners, contests, and e-commerce that already know resets. You should not bet the firm on a single terminal vendor. You want to sell a SKU this quarter, not debug a fill path.
When to build
You have a proven book, a reason the engine is the differentiator, and a budget that assumes 9–18 months of no sales. Even then, native terminals and PSP rails remain a procurement problem. We will not pretend otherwise.
Figures follow the 2026 operator cost stack used across the industry press. They are ranges, not a quote. Cost essay →
Most first firms should not build the engine — or five extra vendors.
Build brand, partners, and payout discipline instead.