Platform · Trading Tools
Tools that read from your fills.
A scanner that does not know your positions, and a journal you have to fill in by hand, both decay within a week. Raptor tools read from the same event stream as your execution.
- What it is
- The analysis layer around execution: charting, instrument scanners, alerting, a trade journal populated from fills, and execution analytics.
- Who it is for
- Traders who review their own performance, and desk managers who need that review to be based on data rather than recollection.
- Why it matters
- Improvement needs measurement. Manual journals stop being accurate exactly when they matter — after a hard week.
- How it connects
- Alerts can target the terminal, email or a webhook. Journal entries are created by the fill, then annotated by the trader.
- What happens next
- Look at the journal and analytics views with a representative set of trades behind them.
Migration
Bring the strategy you already wrote.
The hardest thing about leaving a platform is not the platform — it is the years of work that only runs there. An expert advisor written for MT5 goes through a pipeline rather than a rewrite, and the conversion is tested against the original before anyone trusts it.
What it does
- Reads the MQL5 source and builds a syntax tree rather than pattern-matching text
- Identifies the trading constructs — entries, exits, money management, indicator reads
- Emits TypeScript that runs natively, and Pine for anyone who still charts elsewhere
- Backtests the conversion against the original and reports where the signals diverge
- Deploys to paper, demo or live, and can be listed for other traders if you choose
Why it matters
- An expert advisor is usually years of a trader’s own work; asking them to abandon it is asking them not to move
- Signal parity is reported, not assumed — a conversion that does not match is a conversion you can reject
- The bridges to MT5 and cTrader stay available, but they are migration paths rather than dependencies
The ecosystem
Build it, or buy it from someone who did.
Scripting, backtesting and a marketplace sit inside the terminal rather than beside it, so a strategy can go from idea to live without leaving the window.
Build
- A scripting environment in the terminal rather than a separate application
- Backtest and parameter optimisation against the platform’s own price history
- Strategies and robots managed from a panel beside the chart
- Templates for charts and for orders, so a setup is set up once
Buy and share
- A marketplace for strategies, indicators, signal providers and plugins
- Free and paid listings, with the performance record attached to the listing
- A converted expert advisor can be listed, so migrating work can become work that pays
What is inside
Charting
Multiple timeframes, drawing tools, saved templates, and indicators computed locally.
Scanners
Screen instruments on price, volatility, range and relative strength across asset classes.
Alerts
Price, indicator and exposure alerts delivered in-app, by email or to a webhook.
Trade journal
Created automatically from fills, with session, hold time and excursion attached.
Execution analytics
Slippage, fill quality and time-of-day performance measured from real fills.
Templates
Workspace, indicator and alert templates that can be pushed to a whole desk.
Measure the desk, not the anecdote
We will walk through the analytics views using a book that looks like yours.