PropsEngine Review: Pricing, Ownership & Due-Diligence Passport
PropsEngine publishes clear plan pricing and unusually detailed public terms. PFV keeps the provider on verification hold because legal-identity/contact questions remain unresolved; this page is research, not an active recommendation or introduction route.
Current PFV status: verification hold — research only. Public contract evidence can still be useful to buyers without changing that status.
Published pricing
| Plan | Monthly | Setup |
|---|---|---|
| Starter | €2,000 | €7,500 |
| Growth | €3,500 | €7,500 |
| Enterprise | €5,000 | €7,500 |
Buyer Dependency Layer
| Dependency layer | Current evidence state | What the buyer still needs to establish |
|---|---|---|
| Exit & portability | unknown | Client controller status is public, but complete exit-export rights, schema, timing, retention and deletion terms are not publicly established. |
| Control & authority | partial | Client responsibility for funds is stated and risk/payout tooling is included; exact operational decision and override authority requires contract review. |
| Integration dependency | unknown | General integrations do not establish buyer API/webhook rights, credential ownership or termination portability. |
| Operational continuity | partial | A monthly uptime target is stated with exclusions; exit migration, remedies, rollback and post-termination support are not publicly established. |
See the Buyer Dependency Model methodology →
PFV Due-Diligence Passport
| Area | Evidence state | Buyer implication |
|---|---|---|
| Data role | Primary-source evidenced | Terms say the prop-firm client acts as data controller while PropsEngine processes trader data on the client's behalf. |
| Technology ownership | Primary-source evidenced: vendor-owned | Terms retain platform/software/underlying technology IP with PropsEngine; client branding/content remains client property. |
| Full exit export | Unknown | No complete public machine-readable exit-export specification was located. This remains a contract question. |
| Uptime | Provider-stated target | Terms target 99.5% monthly uptime, excluding scheduled maintenance and named external causes. Buyers should distinguish a target from a remedy-backed SLA. |
| Support | Provider-stated | Terms state email response target within 24 hours and faster Telegram targets for higher tiers. |
| Trader funds | Primary-source evidenced boundary | Terms state PropsEngine does not manage trader funds on behalf of clients. |
| Migration / exit | Unknown | Onboarding timing is published, but complete termination migration assistance and post-termination access are not publicly specified. |
| Dependency concentration | Medium-high | Dashboard, challenges, KYC flows, payout tooling, liquidity integration and risk tooling may sit in the same stack. |
| Risk authority | Partial / contract needed | Risk and payout tools are included, but exact override and approval authority should be documented. |
Verification issues remain separate
PFV's earlier review did not establish a sufficiently clear public contracting legal identity and a prior outreach route failed. This does not prove misconduct; it means a buyer should resolve the entity, jurisdiction, contact route and enforceable agreement before paying setup fees or migrating data.
Minimum written evidence before purchase
- Contracting legal entity, registration and governing jurisdiction.
- Complete data-export objects, format, timing and retention after termination.
- SLA measurement method, exclusions, remedies and incident escalation.
- Third-party hosting, liquidity, KYC and payment dependencies.
- Migration-away assistance and fees.
- Risk-rule override, payout approval and audit authority.
Compare these issues using the PFV due-diligence framework, data ownership guide and PropsEngine vs FXPropTech comparison.