Source-aware field guide · 20 answers
Trading Platform Comparisons
A disclosed buyer framework for comparing RTX5, MetaTrader 5, cTrader, Match-Trader and TradeLocker with evidence and acceptance tests.
Published · reviewed for scope, source visibility and answer ownership
How to use this guide
A useful platform comparison begins with the operator's workflows, permissions and dependencies rather than a generic feature score. MetaTrader 5, cTrader, Match-Trader, TradeLocker and RTX5 are described by their publishers in different ways and may be sold through different commercial arrangements. Compare the exact proposals received for terminal access, administration, CRM, payments, liquidity, bridge, market data, hosting, integrations, implementation, support and exit rights.
This guide uses official public product material to define questions, but a public page cannot establish the package available to one buyer. If official material does not publish a current price, the price is not publicly disclosed and must be obtained in writing. Record the source URL and review date for every factual comparison, then reconcile it with the signed scope. Test the short list with the same accounts, instruments and failure scenarios so the evidence is comparable.
FxTrusts offers and implements RTX5 through its platform relationship with ORRNN. That relationship creates a commercial interest, and this collection states it directly rather than claiming neutrality. Buyers should independently verify RTX5 and every competing offer with its publisher or authorized counterparty. No platform ranking, performance result, saving, service level or included integration should be inferred from this guide; the final decision should identify assumptions, exclusions and unresolved evidence.
How to Build a Trading Platform Requirements Matrix
List required trader workflows, channels, instruments, account models, order behavior, administrator permissions, APIs, reports, integrations, capacity assumptions and operating controls. Give each requirement an owner, priority, evidence request and pass criterion before viewing demonstrations.
- Use it to
- Score only evidence from the exact proposed configuration and keep unmet, optional and unknown items separate from confirmed capability.
- Check the boundary
- A broad product claim may be accurate but irrelevant to the contracted edition, deployment model or third-party services in the buyer's proposal.
How to Weight Trading Platform Selection Criteria
Weight criteria according to business risk and operating need, such as regulatory fit, workflow coverage, control access, integration evidence, data portability and recoverability. Approve weights before scoring suppliers and document any later change.
- Use it to
- Use a decision log showing raw evidence, evaluator comments, weighted score and unresolved assumptions rather than publishing a universal winner.
- Check the boundary
- A score can create false precision when evidence quality differs; mark unverified claims unknown instead of awarding provisional points.
How to Compare Trading Platform Contract Models
Compare the contracting entity, license or hosted-access basis, permitted brands and business models, environments, usage measures, renewal, suspension, termination, data export and transition assistance. Map third-party contracts separately.
- Use it to
- Convert each proposal into one normalized contract table and have legal, commercial, technical and operational owners approve their sections.
- Check the boundary
- Similar trader interfaces can sit behind materially different rights and responsibilities, so product names alone are not comparable contract units.
How to Separate Platform, CRM and Portal Scope
Identify whether account onboarding, KYC, funding, IB management, support and lifecycle actions live in the platform, a CRM, a client portal or connected services. Name the source of truth and interface owner for each record.
- Use it to
- Test one client journey across every boundary and require logs that connect the same client and account identifiers throughout.
- Check the boundary
- Terms such as ecosystem or all-in-one do not prove that CRM, portal or integration services are included in the quoted contract.
How to Normalize Trading Platform Pricing
Normalize setup, recurring access, volume or account usage, environments, integrations, branding, market data, hosting, support, migration, training and exit work over the same scenarios and currencies. Preserve every supplier assumption.
- Use it to
- Where an official public source does not state a current price, record the price as not publicly disclosed and request a dated written quote.
- Check the boundary
- Do not compare a bundled total with a platform-only line or publish remembered numbers as current prices; inclusions and commercial terms can change.
How to Compare Trading Platform API Evidence
Request the applicable API documentation, authentication model, permission scopes, rate or capacity constraints, sandbox access, version policy, sample errors and support boundary. Prove each required operation in a controlled environment.
- Use it to
- Run identical account, order, position and report scenarios where supported, then store requests, responses and reconciliation results.
- Check the boundary
- The existence of an API does not establish entitlement to every endpoint, production access or support for a buyer's intended automation.
How to Compare Platform Administrator Access
Create a role-by-role matrix for user management, account operations, risk, symbols, groups, reports, integrations and audit. Ask each supplier to demonstrate allowed and denied actions using the actual proposed permission tier.
- Use it to
- Evaluate whether critical daily work requires provider intervention and include that dependency in operating procedures and incident routing.
- Check the boundary
- A demonstration performed with supplier-level access may overstate the permissions delivered to the buyer under a hosted arrangement.
How to Compare Platform Web, Desktop and Mobile Channels
List the supported channels in the exact proposal and test login, charting, order entry, modification, account data, statements, notices and recovery on approved devices and browsers. Record channel-specific differences.
- Use it to
- Use one device matrix and the same test accounts so a missing workflow cannot be hidden by switching to another client.
- Check the boundary
- Public screenshots or app listings do not prove that a branded channel, store publication or every feature is included in the contract.
How to Compare Algorithmic Trading Scope
Define the required automation language or interface, development tools, testing environment, deployment method, permissions, data access, logging and operational restrictions. Verify a representative strategy lifecycle rather than counting marketing labels.
- Use it to
- Record build, test, deployment, stop and audit steps, including who supports the runtime and how a problematic strategy is disabled.
- Check the boundary
- Automation capability, marketplace access and third-party code compatibility vary by platform and arrangement; confirm current official documentation and contract scope.
How to Compare Copy and Social Trading Scope
Compare provider onboarding, follower consent, allocation rules, minimum sizes, risk limits, divergence handling, fees, reporting, disconnection behavior and audit records. Identify whether the function is native, integrated or separately contracted.
- Use it to
- Test partial fills, insufficient margin, symbol differences, deposits, withdrawals and provider closure with the same documented expectations.
- Check the boundary
- A copy-trading label does not establish legal suitability, identical execution or inclusion in the base platform proposal.
How to Compare Platform Liquidity and Bridge Boundaries
Map market data, liquidity contracts, bridge or routing, symbol translation, execution, risk handling, reconciliation and monitoring for each proposal. Name the supplier and support owner at every boundary.
- Use it to
- Trace test orders from client request to downstream report and back, then reconcile identifiers, timestamps, prices, quantities and final status.
- Check the boundary
- Platform availability does not mean liquidity, a bridge or a particular routing model is included; require those dependencies in writing.
How to Compare Platform Risk Control Access
Document the required views, limits, group controls, exposure reports, manual actions, approvals and audit records. Demonstrate each control with named roles and confirm which changes the operator can make without supplier intervention.
- Use it to
- Run normal and threshold scenarios, capture configuration before and after, and test that unauthorized roles cannot perform the action.
- Check the boundary
- Risk terminology differs among products; compare the operational outcome and evidence rather than assuming similarly named settings are equivalent.
How to Compare Platform Prop Firm Workflows
Map purchase, account provisioning, rule evaluation, pass, breach, retry, payout review, notice and dispute evidence. Separate trading-platform events from CRM, rule-engine, payment and operator decisions for every candidate.
- Use it to
- Execute the same edge-case accounts and require a reconstructable timeline showing source values, rule version and responsible system.
- Check the boundary
- A platform marketed to prop firms may still rely on third parties for checkout, CRM, evaluation logic or payouts; verify the signed responsibility map.
How to Compare Trading Platform Migration Readiness
Compare export and import coverage for clients, accounts, balances, positions, orders, history, credentials, reports and audit records. Assess mapping tools, rehearsal environments, reconciliation, cutover support and rollback feasibility.
- Use it to
- Request sample files and run a representative migration before scoring portability or assigning a production date.
- Check the boundary
- Migration scope depends on both source and destination rights; a supplier cannot guarantee access to data controlled by another provider.
How to Compare Platform Data Export Rights
List every operational, client, transaction, configuration and audit dataset needed during service and at exit. Compare format, frequency, completeness, identifiers, retention, delivery method, fees and contractual use rights.
- Use it to
- Obtain a sample export and prove that an independent reviewer can reconcile it to the platform records and downstream systems.
- Check the boundary
- A dashboard download is not necessarily a complete or contractually reusable export; confirm scope and rights before vendor selection.
How to Compare Platform Branding Rights
Compare permitted names, domains, logos, colors, legal notices, emails, applications and store accounts across each supported channel. Record who owns and controls every digital asset during service and after termination.
- Use it to
- Require a channel-specific branding schedule and test the full set of client states, including errors and automated communications.
- Check the boundary
- A white-label description does not prove complete rebranding or ownership of app-store listings, domains and source assets.
How to Compare Platform Security and Hosting Scope
Request the applicable hosting boundary, access controls, logging, monitoring, backup, recovery, change process, incident notification and independent assurance evidence. Map buyer responsibilities beside supplier responsibilities.
- Use it to
- Test restore or recovery evidence, privileged-access workflows and escalation using the same materiality assumptions for each candidate.
- Check the boundary
- A hosting location or security badge is not a complete control assessment; confirm evidence scope, dates, exclusions and subcontractors.
How to Compare Platform Support Responsibilities
Define supported users, channels, hours, severity rules, response commitments, escalation levels, maintenance notice, language and third-party handoffs. Match each incident category to the party that can diagnose and resolve it.
- Use it to
- Submit representative support scenarios during evaluation and record the route, evidence requirements and contractual answer rather than assuming an SLA.
- Check the boundary
- This guide makes no support SLA claim; only the current executed agreement can establish service commitments and remedies.
How to Run a Common Platform Acceptance Test
Use identical personas, accounts, instruments, expected results and failure cases across shortlisted platforms. Cover onboarding handoff, trading, administration, reporting, integration, recovery and exit evidence, with deviations approved in advance.
- Use it to
- Keep screenshots, logs, exports and defect decisions in one indexed pack so reviewers can trace every score to observable evidence.
- Check the boundary
- A scripted supplier demo is useful discovery but is not buyer-controlled acceptance testing of the proposed environment and permissions.
How to Write a Trading Platform Decision Record
State the business context, candidates, sources and review dates, requirements, weights, evidence, contract assumptions, test results, total cost scenarios, risks, conflicts of interest, unresolved items and approval conditions. Name decision owners.
- Use it to
- Disclose that FxTrusts offers and implements RTX5 through ORRNN whenever FxTrusts prepares or contributes to an RTX5 comparison.
- Check the boundary
- The record should not claim neutrality, market leadership, performance, savings or included service levels unless current, attributable evidence supports that exact statement.
Primary and official references
These sources establish definitions, standards or official product behavior used across this guide. Follow the exact source and check its current version before a live implementation.