Leverate Integrates xChart Engine for Unified Broker-Controlled Trading
Leverate deployed xChart on August 24 as the default chart engine across desktop and mobile, routing chart orders through the broker's existing infrastructure, per FX News Group and TradingView.
Garrett Croft·updated August 24, 2026

Chart-originated orders running on a separate execution route from the broker's standard ticket flow add monitoring overhead and risk-check drift. Leverate deployed xChart on August 24 as the default chart engine across desktop and mobile, routing chart orders through the broker's existing infrastructure, per FX News Group and TradingView. Confirmation and execution speed are configurable per account group from the Broker Portal; new accounts default to confirmation ON, and prop-account orders remain under Leverate's risk engine in-flight. Execution speed is a broker-set parameter, not a fixed platform spec; no latency benchmark or test results were supplied.
Execution routing parameters
- Order path: chart orders use broker's existing infrastructure; no parallel route
- Risk checks: inherited from platform-level controls; identical to ticket orders
- Confirmation: account-group toggle via Broker Portal; new accounts default ON
- Execution speed: broker-set parameter at account-group level
- Prop accounts: Leverate's risk engine governs orders in-flight
- Branding: broker-controlled UI surface across chart, ticket, mobile
- Multi-book routing: one execution path across instrument books
Platform specification
| Parameter | Desktop | Mobile |
| Charts | Up to 8 independent | Swipe, one at a time (no grid) |
| Layouts | 10+ | Single-chart focus |
| Chart types | 6 | 6 |
| Timeframes | 9 | 9 |
| Drawing tools | 11 | 11 |
| Indicator groups | 4 | 4 |
| Layout persistence | Auto-save | Synced from desktop |
| Drawings / settings | Carry to mobile | — |
| Localization | Number / date formats, RTL | Number / date formats, RTL |
| Touch targets | — | Enlarged SL, TP, Entry handles |
| Bulk actions | Labeled buttons | Labeled buttons (no hidden gestures) |
| Order types | Pending, market, Close All, Cancel All, docked ticket | Same set |
Comparable single-screen chart-trading releases: Devexperts DXtrade (March 18, 2026) merged mobile chart with order-entry panel; Match-Trade Match-Trader (May 7, 2026) added drawing tools and pattern recognition alongside its existing TradingView integration; Spotware cTrader has routed TradingView orders through broker risk controls since 2024; SiRiX added an embedded TradingView option in March 2025. Per Idan Stambulchik, promoted to Head of Product in May 2025, early feedback describes the workflow as faster and more natural — a qualitative claim with no accompanying latency data.
Deployment checklist
1. Broker Portal: locate account-group confirmation toggle and execution-speed field
2. Prop desk: map risk-engine handoff for in-flight chart orders
3. Mobile: validate SL drag without page scroll; confirm bulk-action button placement
4. Cross-device: test layout auto-save and drawing sync desktop ↔ mobile
5. Audit: chart-originated order path vs. ticket order path — confirm identical route and risk checks
6. Branding: confirm broker UI surface persists across chart, ticket, mobile views