FXPropTech Review: Pricing, Platforms & Due-Diligence Passport
FXPropTech sells an all-in-one prop-firm infrastructure stack with unusually visible public pricing and technical documentation. PFV keeps commercial fit separate from evidence quality and dependency risk.
Buyer snapshot: public plans start at $1,000/month plus $1,500 setup. Official material lists MT5, cTrader, Match-Trader and TradeLocker among supported platform options.
Verified public pricing
| Plan | Monthly | Setup | Account allowance |
|---|---|---|---|
| Startup | $1,000 | $1,500 | Up to 500; $2.50/account after limit |
| GrowUp | $2,500 | $3,000 | Up to 2,000; $2.50/account after limit |
| ScaleUp | $5,000 | $6,000 | Unlimited |
Buyer Dependency Layer
| Dependency layer | Current evidence state | What the buyer still needs to establish |
|---|---|---|
| Exit & portability | partial | Ownership and machine-readable post-termination export are publicly evidenced; exact export scope, timing, cost, retention and deletion terms still require the signed agreement. |
| Control & authority | unknown | Exact contractual authority over breach, risk-rule override and payout decisions is not publicly established in the reviewed evidence. |
| Integration dependency | partial | REST/WebSocket/API and webhook documentation is public; buyer should confirm read/write/event scope, rate limits, credential ownership and termination access. |
| Operational continuity | partial | Availability and migration/wind-down assistance are publicly described, but contractual remedies, rollback and post-termination support scope require agreement review. |
See the Buyer Dependency Model methodology →
PFV Due-Diligence Passport
| Area | PFV evidence state | Buyer implication |
|---|---|---|
| Client data ownership | Primary-source evidenced | Public terms state the client retains ownership rights in Client Data. |
| Exit / data export | Primary-source evidenced, scope to contract | Public terms/FAQ describe machine-readable post-termination export and a wind-down path; confirm exact objects, timing and assistance in the signed agreement. |
| API & webhooks | Public technical documentation | REST/WebSocket/API and webhook capabilities reduce opacity, but buyers should test the exact endpoints needed for portability. |
| Technology ownership | Vendor-owned | Client-data ownership is separate from ownership of the underlying platform/software IP. |
| SLA / reliability | Provider-stated | 99.9% availability claims are useful evidence signals, not independently measured PFV uptime. Confirm contractual measurement, exclusions and remedies. |
| Migration | Provider-stated | Migration/wind-down assistance is described publicly; acceptance criteria should still be written. |
| Dependency concentration | Medium | A broad stack simplifies operations while concentrating several workflows. Map which platform/KYC/payment relationships are direct versus vendor-mediated. |
| Risk / payout authority | Unknown / needs contract | Do not infer final breach or payout decision rights from feature descriptions. |
Platform and implementation
Official material names MT5, cTrader, Match-Trader and TradeLocker. Buyers should confirm licensing, account provisioning, bridge dependencies, pass-through costs and the production configuration in writing. Launch timing is provider-stated and should not be treated as a guaranteed implementation SLA.
Questions to close before signing
- Exact platform and market-data licensing responsibility.
- Complete export schema for traders, accounts, trades, breach state, payouts, KYC status and affiliates.
- Contractual uptime measurement, exclusions and remedies.
- Direct versus vendor-mediated third-party accounts and credentials.
- Who has final authority over risk breaches, overrides and payout approvals.
- Termination notice, migration assistance and deletion timeline.
Commercial relationship disclosure
FXPropTech publishes recurring affiliate economics. Referral compensation is tracked separately from research conclusions, provider status and Get Matched scoring.