MesoSim v2.12 and MesoLive v1.0
Introβ
We're excited to announce the dual release of MesoSim v2.12 and MesoLive v1.0. This marks a major milestone for us: we are now capable of live trading the strategies developed using MesoSim.
Since the last official update, we have implemented over 80 changes in MesoSim and more than 250 changes in MesoLive. These updates were continuously rolled out to the service.
MesoSim related changes:
- UX Improvements:
- Updated documentation site with video tutorials
- Job Definition Reference now visible in the Job Editor
- API Enhancements (Institutional plan only)
- Improved Handling of Missing Data with advanced heuristics
- MesoLive compatibility related refactorings
MesoLive related changes:
- Support the full trade lifecycle using IBKR brokerage:
- Entry
- Monitoring
- Adjustments
- Exits
- Documentation site with video tutorials
Case for MesoLiveβ
One key achievement is that MesoLive's trade selection and management use the same codebase as MesoSim, to the greatest extent possible.
This is a critical feature, highlighted by Ernie Chan in his Algorithmic Trading book:
This ease of switching between backtesting and live execution is more than just convenience: It eliminates any possibility of discrepancies or errors in transcribing a backtest strategy into a live strategy, discrepancies that often plague strategies written in a general programming language whether it is C++ or MATLAB.
MesoLive Pricingβ
Weβve worked hard to improve the efficiency of MesoLive, making it affordable. Thanks to these optimizations, weβre introducing MesoLive at an introductory price of $25/month.
Note: MesoLive is available as an add-on to MesoSim.
Trial and Compatibilityβ
Before subscribing, please consult our documentation to ensure your strategy is fully supported. Additionally, we recommend utilizing the trial to experience the platform firsthand.
Next stepsβ
We will continue to extend MesoLive and MesoSim compatibility by adding missing features and supporting additional brokerages. In parallel, we plan to expand our Q-API with more functions to assess predictor-target relationships.