Begin with the account-platform combination
A platform is the software used to view prices, manage orders and inspect an account. The broker and contracting company supply the account and execution arrangement. A platform brand therefore cannot tell you which legal entity holds the relationship, which instruments are available or what fees apply.
Write a comparison as “entity + account type + platform”, not just “MT4 versus web”. That longer label prevents a common mistake: attributing one account’s fees or product library to every interface available under the broker’s brand.
Check instruments and specifications
OANDA’s UK platform page gives a concrete example: its comparison separates web, mobile, TradingView, MT4 and MT5, with different product-availability rows. CMC’s UK documentation also separates its own platform and a MetaTrader page. Those are useful starting points, but an application’s current account documentation remains the relevant source.
For each instrument you intend to inspect, record the symbol, contract size, quote precision, minimum transaction size, trading hours and financing reference. Two screens can display similarly named markets without using identical contract units. A calculator result is only useful if its inputs match the contract.
Try a repeatable workflow in a demo
Use the same non-funded task on each interface. Locate an instrument, inspect its specification, open an order ticket, read the units, and cancel before confirming. Check whether buy and sell prices are clearly distinguished and whether a chart displays the bid, ask or midpoint. Then find the statement and explanation of charges.
This is a usability exercise, not a performance trial. It does not establish live fills, withdrawal speed or service quality. A demo can reveal a confusing unit label; it cannot prove that an order will execute at a particular price when real markets become volatile. Our demo checklist keeps those conclusions separate.
Treat automation as a compatibility question
If you already use an indicator or automation file, identify its supported platform version and runtime from its own documentation. Do not assume that similarly named platforms run the same file or reproduce results identically. Check whether the broker permits the workflow on the intended account, and review any hosting or add-on costs.
A backtest is a model built from assumptions about data and execution. It is not evidence that an automated approach is suitable, robust or likely to make money. PipBriefing does not supply trading robots, signals or instructions for connecting a live account.
Give reporting and access a place in the decision
A useful interface makes it possible to identify a position’s size, costs and account company. Check statement export formats, timezones, transaction identifiers and where financing appears. Verify the supported device through the provider rather than downloading an installer from a search advertisement.
Document how access is recovered and how the provider communicates service interruptions. Do not send account credentials to comparison sites or third-party support contacts. PipBriefing never asks for broker logins.
The comparison tool lays out the platform options found in our five broker sources. “Listed” means the source names that platform; it is not a promise of access for every resident, account or product. Establish identity with the entity checklist and then compare the exact account terms.