PropLabel Review: Pricing, Migration & Due-Diligence Passport
PropLabel positions a hosted white-label operating stack combining CRM, risk tooling, KYC/AML, payout workflows, automation and integrations with major trading platforms.
| Standard onboarding | €3,900 in currently tracked pricing material |
|---|---|
| Priority onboarding | €5,900 in currently tracked pricing material |
| Ongoing model | Revenue-linked model with a minimum; exact current step-down structure should be reconfirmed in writing. |
| Trading platforms | Match-Trader, TradeLocker, MT5, MT4, cTrader and DXtrade are publicly listed. |
Buyer Dependency Layer
| Dependency layer | Current evidence state | What the buyer still needs to establish |
|---|---|---|
| Exit & portability | unknown | Migration is marketed, but buyer exit rights, full export schema/format/timing, retention and deletion terms are not publicly specified. |
| Control & authority | partial | Automated rule enforcement, payout workflows and audit trails are published; exact approval and override authority requires contract review. |
| Integration dependency | partial | Platform/API integrations are published; general buyer-facing API/export rights, credential ownership and termination portability need confirmation. |
| Operational continuity | partial | Zero-disruption migration is provider-stated; no reviewed contractual SLA, rollback rights or post-termination support terms establish full continuity. |
See the Buyer Dependency Model methodology →
PFV Due-Diligence Passport
| Area | PFV evidence state | Buyer implication |
|---|---|---|
| Data ownership | Unknown / needs contract | Full customer/trader data ownership and permitted use are not sufficiently established by the public product pages used here. |
| Exit / full data export | Unknown | PropLabel markets migration, but a complete public export schema, format and post-termination access window were not located. |
| Technology ownership | Vendor-owned hosted stack | Do not assume source-code ownership from white-label branding or customization. |
| Migration | Provider-stated | Public migration material describes assessment and seamless/zero-disruption transition. Buyers should require source-to-target mapping, reconciliation and rollback criteria. |
| Platform/API integrations | Provider-stated, specific | Public material lists Manager/Open/REST API integrations for multiple trading platforms; general buyer-controlled export/API rights still need confirmation. |
| Auditability | Provider-stated | PropLabel says rule changes, overrides, account closures and payout approvals are logged. Test retrieval, retention and export of those audit records. |
| SLA / resilience | Unknown / not publicly evidenced enough | Do not infer a contractual SLA from infrastructure or uptime marketing. |
| Dependency concentration | Medium-high | CRM, risk, KYC, payout workflows and trading integrations can be concentrated in one vendor. |
| Risk / payout authority | Partial / needs contract | Automated rule enforcement and payout workflows are public features; final human/vendor authority should be written. |
Why auditability matters
PropLabel publicly emphasizes logging around rule changes, manual overrides, account closures and payout approvals. For buyers, the key test is whether these records can reconstruct a dispute end to end and whether they remain accessible/exportable during a provider switch.
Questions to close before signing
- Current setup fee, minimum recurring charge and exact revenue-share definition/step-down.
- Full trader/account/trade/payout/KYC/affiliate export schema and machine-readable format.
- Audit-log retention, export and access after termination.
- Who owns and controls domain, merchant/KYC credentials and integration accounts.
- Contractual SLA, incident escalation and third-party outage responsibility.
- Final authority for breach overrides, payout approvals and account closures.