Prop trading platform FAQs: pricing, CRM, challenge engine and launch.

No software-provider entitlement should be assumed. Confirm the legal contracting party, permitted platform use, market-data permissions and any third-party licence separately. MT5 main-platform rights are distinct from another vendor's white-label terms.

Potentially. We need supported API documentation, rate limits, sandbox access, account-event mapping, identity permissions, data ownership and a signed compatibility scope. Migration and cutover require explicit reconciliation.

Supported devices depend on the selected platform and vendor rights. A web trader area, branded application, custom desktop experience and app-store publication are different deliverables and should be quoted separately.

Multi-brand support requires actual platform rights, segregated tenants, consistent permissions, financial data boundaries and documented support controls. It is not promised solely by choosing a package tier.

TRADE OS Platform monthly package prices are Basic $2,500, Turnkey $4,000 and Server $5,000. These are our published selling prices. Your written offer confirms account bands, included features, optional add-ons, setup fees, third-party licensing and payment terms.

Not necessarily. Request separate amounts for design, migration, one-time integrations, custom rules, hosting, ongoing per-account or usage fees, processor reserves, maintenance and termination services.

Optional items are priced separately where supported. Core scope is subject to the final TRADE OS package order, confirmed feature entitlements, account volume bands and vendor dependencies.

It should list the legal contracting entity, licensing rights, inclusions and exclusions, billing units, volume bands, delivery stages, support SLAs, security responsibilities, vendor dependencies, acceptance criteria and migration/exit assistance.

Define whether the base is balance or equity, the reset timezone, treatment of unrealised P&L, commissions, swaps and deposits, and the timestamp ordering. Replay controlled trade data and retain rule-version history.

It should not. Payment integration needs idempotent webhook handling, a durable ledger, manual-review states, refund matching, account entitlement checks and explicit failure tests.

Use auditable approvals, verified identity and eligibility, trade-history reconciliation, documented exception handling, appeal evidence and immutable decision timestamps. Payout capital and processor fees are separate from software scope.

No universal permission can be presumed. Customer terms, payment eligibility, promotional restrictions, data handling and potential regulatory requirements vary by market. Obtain qualified local legal advice before selling.

No fixed timeline is promised. Readiness depends on legal and payments checks, vendor onboarding, platform rights, integration availability, acceptance tests and operational approvals.

Test account provisioning, challenge resets, simulated price events, stale feeds, duplicate payments, risk breaches, permissions, data exports, backups, incident escalation and controlled rollback.

The contract should distinguish controller/processor roles, operational data ownership, transfer formats, access control, retention, backup, third-party systems and deletion or export on termination.