DinoOpenEngine: A C# / SQLite-Driven Framework for MetaTrader 5
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Hi everyone,
I’m sharing a project I’ve been developing to solve "EA Sprawl." When managing a portfolio across multiple instruments, the overhead of maintaining, compiling, and deploying dozens of different Expert Advisors becomes a significant bottleneck.
DinoOpenEngine is an algorithmic trading framework that moves strategy logic out of the compiled binary and into a structured, C#-driven environment.
The Core Concept
Instead of hardcoding unique logic into every EA, you define your strategies in typed C# using a fluent API. These definitions and parameters are stored in a shared SQLite database.
You use a single, standardized EA binary across your entire terminal. When attached to a chart, this "Engine" binary reads the database, pulls the specific logic assigned to that instance, and executes it.
Key Features
Standardized Deployment: One .ex5 file for everything. No more "EA_Gold_V2," "EA_EURUSD_Final," etc.
Data-Driven Logic: Change strategy parameters or logic in the database/C# layer and the changes take effect without needing to recompile or swap files in the terminal.
Advanced Risk Management: Built-in drawdown limits scoped by hour, day, week, and month (ideal for prop-firm consistency rules).
State Persistence: Critical states (trailing stops, break-even levels, virtual stops) are persisted in SQLite to survive terminal crashes or VPS reboots.
Regression Testing: Includes a test suite that runs backtests against "golden files" to ensure refactoring doesn't break your logic.
Server-Side Ready: Includes a JWT-based authentication system (currently inactive in the OS release) for those looking to integrate backend controls.
Why use this?
If you are running one or two simple bots, vanilla MQL5 is likely more efficient. However, if you are managing a diverse portfolio and are tired of the copy-paste-compile-redeploy cycle, this framework provides the architectural "plumbing" to help you scale.
GitHub Repository: https://github.com/GiacomoGhi/DinoOpenEngine
I'd love to hear your thoughts on the architecture!
In the repo README file and the related WIKI there is the detailed documentation on how everything works together. Thanks to everyone interacting with this post!