compare

Footnotes

1. Modern, full-functional and visually appealing.
2. Functional but less visually appealing. Important: functionality listed for the desktop app; browser and especially mobile versions have substantially less functionality.
3. Visually appealing but functionally limited.
4. In progress.
5. Trader's hardware only (local or rented VPS).
6. Limited direct broker integration, intended primarily for analysis or ad-hoc trades.
7. Limited functionality (full available as a desktop application). ~70% available in web, ~60% in app ~50% in mobile web, 60% in app. Broker customizatios for destop app are not available in other platforms, duplication required. No customizations for mobile app.
8. While it tracks different assets well, integration of portfolio performance across different asset classes might require additional manual tracking or third-party plugins.
9. Advanced risk management orders like trailing Take-Profit Orders are not natively supported; traders need to use custom scripts or Expert Advisors (EAs) to implement trailing take-profit strategies.
10. Portfolio tracking and customization can be complex and might require scripting knowledge (MQL4/MQL5).
11. Limited broker integration means that executing complex order types (like trailing take-profit) might not be directly supported; you often need to switch to the broker’s platform for execution.
12. TradingView does not natively track margin levels across different brokers, which can be a limitation for margin trading. Users need to rely on broker platforms for accurate margin tracking.
13. If you are using TradingView to trade through an integrated broker, you will see the broker’s specific spreads and any changes in real-time. However, TradingView’s general market data may not reflect the exact spreads offered by your broker.
14. Advanced customization and automation, which are needed very often, require knowledge of MQL scripting, and broker-specific nuances can complicate implementation.
15. Brokers that are integrated with TradingView, usually do not provide the full range of order types and execution features available on their native platforms. General market data might differ from broker-specific data, particularly in terms of spreads and execution prices, leading to potential discrepancies in analysis versus actual trading conditions. Advanced order types and execution features may be limited or require switching to the broker’s platform for full functionality.
16. TradingView users typically need to check their broker’s platform or statements to see detailed fee information after trade execution.
17. Generally does not show fees before order submission.
18. Automatic and manual, with different available levels and actions.
19. Realtime, cross-asset, netted + sided.
20. Manual and automatic with different options available(shifting to agent execution, increasing margin requirements, increasing margin maintenance requirements, stopping taking new positions etc) - based on ticket side, netted or sided exposure to a trading pair, asset or asset-class.
21. Stop-loss orders only.
22. Including individual positions' metrics and tracking MAE/MFE, historical performance charting.
23. Ability to preview an effect of a potential trade on the portfolio risk profile using pro-grade metrics (VaR, CVaR, Sharpe and Sortino ratios).
24. Yes, consumer grade, not suitable for high-frequency trading.
25. Planned to be released before general availability.
26. MT4: forex only; MT5 - wider support incl. forex, stocks, and futures.
27. Supported via pluggable modules, no lock-up to platform or news feed vendors.
28. Supported via pluggable modules with built-in FIX support + WebSockets, and custom protocol handlers. This feature allows runtime/configurable switching between multiple exchanges or liquidity providers. Traders or staff (configurable) can select the preferred provider in cases where a security is tradable on multiple platforms. For broker-managed selection, a customizable algorithm chooses the best provider based on Level 2 (L2) information. New modules (for new providers) can be developed by broker or Lyra (for reuse).
29. Yes, plus a base currency can be any assed incl. crypto etc.
30. Require switching to the broker’s platform.
31. Limited customization; expensive; custom scripting; n/a to all platforms (like browser/app).
32. All that is offered is a "broker integration panel" that can show current balance, unrecognized PnL, etc.
33. Invoke call/chat; arbitrary notifications (targeted and broadcast).
34. Only client-side functionality can be implemented by adding from-scratch functionality; not supported by platform itself.
35. Consider calculation of profit or loss when trading CHF/JPY on an EUR-denominated account: This feature accounts for the impact of shifts in both CHF/JPY and EUR/JPY exchange rates. Without it, take-profit and stop-loss orders can have undesired effect, triggering early (take profit) or liquidating with more losses than expected (for stop-loss).
36. The chaining mechanism applies to take-profit, stop-loss, limit, and stop orders, ensuring that all non-market order types are triggerred (or not) when any security in the chain changes price inasmuch as the trigger condition is satisfied.
37. Allows for flexible and customizable combinations of fees, including fixed/floating fees per trade, commissions (in pips or basis points), and spread markup. These combinations can be tailored for trade side, asset class, individual trading pairs, and personalized for specific user groups or even individual accounts. The same level of customization is available for margin ratios and requirements, including position closeout procedures during margin calls. This grouping capability enables both broad, easy assignments and precise, surgical adjustments as needed, ensuring optimal fee and margin management.
38. Selectable/customizable E-mail, SMS, in-app for all order lifecycle events as well as localizable periodic statements etc.
39. Not a product: custom development only.
40. Brokers can customize the look and feel of the trading platform to align with their brand identity, incorporating logos, color schemes, personalized themes, location and modality of UI elements, rearrange, hide, and introduce new UI elements as the visual layer is specifically designed for such customization.
41. Integrates with broker's exisring system.
42. Pluggable module to track customer transactions to detect and flag potential money laundering, terrorist financing, and other financial crimes. It uses advanced algorithms and real-time analysis to identify suspicious patterns and behaviors, ensuring compliance with regulatory requirements.
43. Locked-in through proprietary pricing interface only
44. This feature allows support staff to verify personal information, such as SSNs, by entering the data provided by the customer and receiving a correct/incorrect response, without viewing the actual information.
45. Separate (duplicative) customizations for web & mobile web
46. Llimited functionality, separate (duplicative) customizations mobile app.
47. The platform is marketed as universal, but in fact there are three separate platforms -" equities" (stocks, optons, futures, bonds, mutual funds), FX/CFD, Crypto
48. [Missing]
49. Primitive "routing wheel" based on asset class only.
50. Customizations are duplicative and completely separate for web UI, iOS and Android.
51. Limited to similar asset classes (3 separate groups, see DXTrade's "Universal asset class support" above").
52. Crude homegrown "Risk profile" that "simulates changes to security parameters, such as price and volatility to estimate potential P/L"; no industry standard metrics.
53. Only if supported by liquidity ptovider.
54. Varies, but never full support across all asset classes from equity to crypto.
55. Direct websocket connection from OMS to clients limits maximum amounts of connected users.
56. Obvious from screenshots.
57. Using commercial cloud.
58. What is called by "Broker Risk management framework" is in fact crude user-based settings limiting vakues like number of positions for a trading account.
59. Limited and customizable during implementation only (seems to be cardcoded).
60. Limited tracking functionality.
61. Based on order/position lifecycle events and arbitrary staff-initiated messages..
62. Customizable and localizable templates.
63. Apparently the branding is not full as there is a whole section and FAQ directung customers to their broker instead.
64. Separate "customer portal".
65. Planned for the next major version, currently can be traded as CFDs.
66. Lacks options/futures pricing engine.
67. FX/CFD only.
68. Cash accounts only.
69. Account balance only.
70. As CFDs.
71. During implementation.
72. Generic + Some countries (U.S. 1099) + implementation.
73. Through margin management tools.
74. Not out-of-the-box.
75. Fixed and floating fees can be managed but granularity is only asset class and accont group; no possibiluty for spread markup (spread widening).
76. Logo and color scheme only.
77. Limited functionality.
78. FX/CFD only, Crypto as afterthought, no equities or othe asset classes. Stocks futures, and commodities advertised are in fact CFDs.
79. MT4 only.
80. Without transparent/real-time evaluation of "via" pairs (compare to #35)
81. Some elements only: exposure->manual hedging.
82. The only action available is stoppng acceping new positions
83. Can only route to vendor's partners via a proprietary product (LxCapital).
84. Limited customizarion; anything beyond logo and fonts breaks support.
85. The system can adapt to different margin requirements based on the asset class being traded, such as fixed margin on equities and constantly adsjusting on FX
86. Two applications, limited functionality each
87. FX,Crypto;crude support for equities
88. Own provider only
89. Limited support, no advanced order types
90. Logo and colors only
91. Broker-level decision; margin trading crude
92. Impractical due to fixed exposure limits
93. Fixed, static routing
94. No flexible granularity support
95. Limited information, some reporting present - but no real risk reporting
96. With included liquidity provider only (franchise model)
97. App is publishe by vendor; links to the vendor throughout
98. Support varies: good for FX and CFD, worse for spot crypto and equities
99. Requires manual integration with broker systems
100. [Missing]
101. Required: cTrader is a UI and UI support system that relies on trader's OMS
102. Relies heavily on brokers' systems
103. Client-side only
104. This is the only possible option