AlgoBuilt from systematic trading, not as a generic software project.
AlgoRoute was developed from a real execution requirement: keeping strategy research and signal generation in MultiCharts while routing execution to MetaTrader 5 environments.
Quantitative researcher, systematic trader & trading infrastructure developer.
My work sits at the intersection of quantitative research, strategy engineering and live automated execution.
I hold a Bachelor’s degree in Statistics, Finance and Insurance from the University of Bologna. My professional focus is the research, development and live execution of rule-based trading strategies across futures, equities, currencies and CFD environments.
My work covers the complete systematic trading process: market and time-series research, strategy design, backtesting, robustness validation, portfolio construction, automated execution and live monitoring. The objective is not simply to produce a backtest, but to build trading models that can be deployed and maintained in real trading environments.
I have worked in quantitative research and systematic trading roles for trading companies, advisory firms and private projects, developing strategies and execution infrastructure used on real capital. My current activity combines systematic portfolio management, quantitative advisory and trading-technology development.
My main technology stack includes MultiCharts, MultiCharts .NET, Python, MetaTrader 5, Interactive Brokers and broker/API infrastructure. I work across the full pipeline, from research and historical-data preparation to VPS deployment, broker connectivity, automated execution and ongoing monitoring.
A central part of my work is building diversified portfolios of independent trading models rather than relying on a single strategy. Each model is developed, tested and monitored as part of a broader systematic infrastructure designed for live execution.
Why I built AlgoRoute
AlgoRoute came directly from that operational work. I needed to keep MultiCharts as the environment where strategies are researched, maintained and generate signals, while executing those same strategies on MetaTrader 5 accounts without rebuilding every model in MQL5.
The first version was developed for my own trading infrastructure, including Darwinex, FTMO Swing and CFD broker environments. The same architecture now allows strategy generation and MT5 execution to remain modular, even when terminals run on separate computers or VPS machines.
I am not only the developer of AlgoRoute — I am also one of its primary live users. All of the public CFD track records available through my Beacons profile were built using this infrastructure to transmit and execute my systematic strategies from MultiCharts to MetaTrader 5.
That is an important part of how I evaluate the product myself: AlgoRoute is not software I built only to commercialize. It is part of the infrastructure I use in my own day-to-day systematic trading activity, across live MT5 environments and multiple accounts.
The public track records provide a transparent real-world example of the same execution architecture being used continuously outside a demo environment.
Built for my own trading. Tested through real-world use. Now available to other systematic traders.
From research to live execution.
AlgoRoute reflects the same workflow I use in systematic trading: keep the research stack robust, keep execution modular and make the infrastructure understandable. The same infrastructure is used behind my publicly available CFD track records.
Strategy logic stays in MultiCharts. Execution is routed to MT5.
Built from a real trading need and used in the live infrastructure behind my public CFD track records.
